I am working on a no-experience port upgrade script on my local game server. It seems to be running fine so far in testing, but the TWX "Script Terminated" message is ending up on screen in SWATH way before it finishes the last of the upgrade cycles on the screen in SWATH, like after 7 cycles with 6 cycles to go when upgrading ore. Like I said, it finishes all the cycles and seems to be working fine --- I am just finding this unnerving. I am not getting any "script errors" from TWX.

Like I said just unnerving when you go to upgrade all 3 categories on the port and TWX is sending the script terminated message right after fuel and organics are upgraded and it still has all 17 cycles to upgrade the equipment 50 units. But it still does all 17 upgrade cycles for equipment and quits from the port upgrade routine in the game back to the command prompt.

Is this fairly common behavior? Is it like just because TWX is much faster than SWATH, so the screen output in SWATH is having to catch up? Is it something I should be worried about with other scripts? Should I put some WAITON's in the script, to keep it from outrunning SWATH or another Telnet program?

Thanks

I am working on a no-experience port upgrade script on my local game server. It seems to be running fine so far in testing, but the TWX "Script Terminated" message is ending up on screen in SWATH way before it finishes the last of the upgrade cycles on the screen in SWATH, like after 7 cycles with 6 cycles to go when upgrading ore. Like I said, it finishes all the cycles and seems to be working fine --- I am just finding this unnerving. I am not getting any "script errors" from TWX.

Like I said just unnerving when you go to upgrade all 3 categories on the port and TWX is sending the script terminated message right after fuel and organics are upgraded and it still has all 17 cycles to upgrade the equipment 50 units. But it still does all 17 upgrade cycles for equipment and quits from the port upgrade routine in the game back to the command prompt.

Is this fairly common behavior? Is it like just because TWX is much faster than SWATH, so the screen output in SWATH is having to catch up? Is it something I should be worried about with other scripts? Should I put some WAITON's in the script, to keep it from outrunning SWATH or another Telnet program?

Thanks

If you're testing I'd recommend forgoing SWATH altogether and just using TWX + a telnet client such as ZOC.

The random errors introduced by SWATH's presence are pretty common and frankly unavoidable, no matter how well you've tuned the settings between the two. Easier to just leave SWATH out of it so you know the errors are in fact with your script, not with SWATH.

Like Vid said, this is normal. For instance, if your script only has a send command:

send "clvq"

The script will exit immediately after the send command, and before the response is actually received from the server.

adding "waiton" or "textrigger" commands as vid suggested will prevent the script from exiting prematurely.

Sometimes you will see "zn" added to the end of a macro. The script did that so it could wait on the "Instructions?" prompt to know when the macro finished.