I wanted to thank you both for your fast responses, but I'm still having the same issue. I am able to connect without using SWATH, but not when I use it!?!?!?!

Start a thread in TradeWars Helpers & Scripts, add a screen shot of the error or the full error message

A screen shot of the SWATH ALT-O screen and we can go from there.

Ah ok in WinXP Start > Run > telnet twgs.21-6.com 23 <-- not really needed if 23, since that is default.

The problem he is having is an issue with the 1.9.4 or older Swath
it is due to the change in the log in triggers.

If he does not use the Swath auto log in or ini. funtions
so that he has to type in his own name and password at prompts
that should get him in with Swath.

The new 1.9.5 will not have this problem , its just not been released yet.
This could not be helped with the current version when changes are made
without considering or knowing what was being triggered on in other software.

Be aware that parsing will have to be turned off if you intend to go into a 30k universe as well.

hope this helps.

Something that might be useful at this point is knowing exactly what the triggers are for major apps like Swath. In general I don't want to break Swath, even if a new version is going to be out soon. But I also don't want to be in a position to not change anything. If I know exactly what needs to stay, I can compromise and get the changes I want without breaking anything.

The problem there-in is that it triggers on practically everything at some point.
As a helper, it tries to parse everything it can.

Well, I do really try to avoid breaking scripts and helpers. My policy is that menu items and prompts will not change, but ancillary text like this or the text that's displayed on startup about the TW copyright and authors, etc, can't be relied upon. Version, copyright date, company name and product name are all subject to change.

That said, I will see if I can fix this.

One of the reasons why the startup text like this comes up so much here is that there's
a pause between the "Enter your name" prompt and the game selection prompt. You
can't just do...

waitFor "Enter your name"
send $loginname & "*" & $gameletter

And have it actually work. So people setup various triggers. They waitfor the
game server to load, then they wait for either an ansi menu to pass, or for the
game select prompt.

In the current ver, most ppl trigger on the "Trade Wars Game Server" text to
separate the trigger phases. It's not necessary, but pack1 scripts like 1_login
have done this for years. When Jumpgate came out a few years ago we found
that the line had been changed, and most of us since have been using the phrase
"Game Server" to trigger on ever since.



That's from the relog I use. Technically, I could combine all of them into a single
block of triggers, so it's not really a big deal. There's not even a need to have the
interim problem trigger.

A lot of scripters do the same stuff. They use code they've used for years because
it works. I don't think it's going to be possible to do all the things you want and
not break some stuff. But it's really not a big deal, I'd much rather have the new
features than a pile of unused scripts.

I mean we all appreciate the work you're doing to maintain legacy support, but
I hope you don't get caught up in that. Most of us don't consider it a high priority.

For instance here's the same block, chopped down to work around the
game load text changes. That took, eh, 60 seconds?

Are you talking about the short pause after the intro screen is displayed but before an ANSI screen is displayed? This was done so that a player could see the official intro text before having it replaced by a full-screen custom login screen.

I imagine this screen is a problem in general because it uses custom ANSI screens that can have any text for the prompt and menus. There's no guarantee you'll get the "Selection (? for menu):" prompt at all. The only text that's consistent is the login prompt and these lines of text. Maybe for future compatibility I should have something in there that would serve as a trigger, that's guaranteed not to change.

Really any text phrase to trigger off of that is going to be there 100% of the time and that ansi screens don't replace if they are used will work.

Yep. And it's fine. It would be nice if keys could be buffered on that pause tho, or during
the ansi menu.



Nod. You could do either the game selection prompt after the ANSI, but that could be
a headache. Or, for super-easy no-fuss fun, just accept keys to be pressed during this
time. If people could do...



And have $gameletter send the player on to that game letter, then none of this would
be necessary.

Actually no longer than the pause is, it's not there long enough to even read the intro text. Plus just about every telnet client has scroll back these days if they want to catch the server IP or name of who it's registered.

Ok, now I understand. I never intended for there to be non-buffering of input there. I'll fix that.

Ok, I'm not sure if it's something I changed, or I'm just not getting what you're saying. Right now, on the beta, if I wait for the text "(ENTER for none)", then send "John<ENTER>A", it will accept login name "John", pause for the 3 seconds, then accept "A" and kick off that game. So it doesn't appear to be eating keys here. Can anyone verify that this behavior is fixed with the beta?