Ok, that is good to know. We are still on the v1 server and have not had much time to examine the v2 server and options. Once we get all the work done on the current project, then we will have to look at it.

I still do not see how you will be able to restrict telnet to telnet and flash to flash logins. Unless the TWGS had a "built-in" web server portion and contained its own games that only the flash interface can access. That would help to keep the two apart.

It won't matter anyway. Most of the current helpers won't work without some major revisions, but anything that accepts key input from the user can be scripted.

Yeah, that's the point. Anyone using the flash client will be forced to play manually (for now). The purpose of the flash client is so players can access the game from mobile devices without needing a telnet app.

I would like to allow flash client players to access all games, but restrict at least one game to flash client users only. Because we know a manual player cannot survive against a telnet player with scripts and helpers.

That's where you are missing the point. Flash clients will be able to use scripts. Maybe somewhat crude methods at first, but it's still very easily done.

Do you have a mobile device that you access games with? If so, what do you use? Hardware and software?

I have a 7" HTC I'm borrowing from my son, and I cannot see myself actually playing a game with this. The MS keyboard doc (I think they call it surface) for 10" tablets looks doable with a standard keyboard.

I think what's trying to be accomplished here is #1 an interface for mobile devices, and #2 a way for people to quickly access the game without going through the "learning curve" of installing a telnet client, etc...

(On the beta server there were over 200 login's within a month after JP asked people to give the flash client a try. That link was on facebook.)

That is what I said in an earlier post.



There is just no reason to make a flash login an actual helper- it is not practical. If it is being used in the method to quickly access a game, then there is no need to have to have TWGS be able to distinguish between telnet players and flash players.

Again, you are missing the point. You are suggesting that the only way to have access is through a mobile device using a flash client when you can access it with the new browsers. See link below.

http://securitywatch.pcmag.com/none/284 ... ash-client

Anything that I can access with a browser, I can script by sending the key commands directly to the browser window.

You are missing the point, flash clients will open up a whole new updated opportunity for flash client helpers.

The times, they are a changing... JP is trying to expand this game from telnet only to allow users to access the game with modern apps and browsers.

Until flash client users "have" the tools to compete against telnet players, I'd like a way to give them their own "space" to play and learn.

Flash connections still use a socket connection and port. So if he (John) is wanting to expand to allow modern apps/browsers via something like flashterm, he will not be able to distinguish between flash client/telnet client connections. We have Java login, Flash login for our TWGS and they still use socket connection and port. If you specify port 23 for telnet and 500 for flash client, how will the TWGS distinguish between the two since the socket connection is the same when being passed to the TWGS? How will I prevent telnet clients from connecting to flash connection on port 500?

I am trying to understand the logic to having two separate logins- one for flash and one for telnet. We already can connect via telnet client, helper, Java login, Flash login now. What is the advantage of segregating them?

Well really what I would like to do is make it so that people could access my server's game via a flash or java based client like the one jp has so that

1. It would be more of a convenience than learning how to use a telnet client and

2. The ANSII graphics would display properly.

Right now I'm using Putty for external access and while it supports color, it doesn't support the graphics.

The Flash/Java client looks like it'd be a nicer route to go, especially for people new to this sort of thing.

I thought I would be easier process, if TWGS has the capability to distinguish between the two different methods to connect. Segregate the telnet players away from the flash client players until they have their own helper.

So, if this isn't possible, I can use the settings available in v2 to create a 500 turn time limit game that will be playable for flash client players and too boring for telnet players.

I've played with both the Java and the Flash clients, and while it was fun at first, all the manual typing was simply too much. Having come from the '90's it didn't take me long to get Zoc and start writing my own macros.

I'm sure once this takes off there will be plenty of "helpers" springing up that use the flash client, but until the players have some sort of scripts to use to play the game, it won't be very fun.

I think this is a brilliant move for JP, there are many more Flash developers than there are people who can code TWX Proxy.

Either this forum thread has taken a life of its own or I'm totally lost... 0_0

You're not lost, welcome to the evolution of EIS Open Forum threads

So, how are you doing there Sam? Do you have any more questions about running your own server?

I use Zoc as a straight telnet client. In the settings I choose to emulate asci BBS and changed the color of my background to black, text to yellow.. etc, so everything looks right. I've not used putty, so I don't know what the settings are for that one to display correctly. I'm sure there's a way, but you're correct, setting up a telnet client and learning to use scripts comes with a steep learning curve.

Probably the easiest "out-of-the-box" telnet clients for TW is Swath. It's free to use for 30 days before you decide if you want to buy it or not. It's a very good helper with lots of built in scripts. You can also create your own macro's on the fly and store them to be reused later.

Not exactly true. Putty does not display the graphics correctly by default. In the configuration under window/translation change the character set to "CP437". Code Page 437 (sometimes referred to extended ascii, although there is no such standard) is the set of line drawing characters used in ANSI drawings. Also, make sure you are using a font like courier new that uses the same spacing for all characters. I was using putty in combination with TWX until I broke down and bought swath.

JP has written his own flash terminal for the next release. He has also added a web server to TWGS that hosts a web page with the Flash terminal on it (on port 80 by default). This flash terminal still connects to TWGS by telnet, so JP would have to add some sort of secure authentication so that TWGS would know you were connecting through the flash client, and then you could restrict games to this client only.