View unanswered posts | View active topics It is currently Fri Mar 29, 2024 12:01 am



Reply to topic  [ 6 posts ] 
 Anyone else seen this odd behavior between SWATH & TWX? 
Author Message
Ensign

Joined: Wed Nov 06, 2002 3:00 am
Posts: 268
Unread post Anyone else seen this odd behavior between SWATH & TWX?
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. :shock:

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


Wed Sep 23, 2015 9:48 am
Profile
Commander

Joined: Sun Feb 25, 2001 3:00 am
Posts: 1837
Location: Guam USA
Unread post Re: Anyone else seen this odd behavior between SWATH & TWX?
SteveH_66 wrote:
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. :shock:

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

What you experiencing is a run away effect .. due to pacing.
If you are like me , you might want that script terminated message when everything was done for real.
I tend to like the ding sound when done as well .. just so I know to launch next script quickly.

But the short answer is its normal.
to make that message appear at the end of your loop
just add a line like this :

Send "/*"
WaitOn "hip"
WaitOn "] (?=Help)?"

and all will be as it should.

Vid

_________________
TWGS V2 Vids World on Guam Port 2002
Telnet://vkworld.ddns.net:2002
Discord @ DiverDave#8374
Vid's World Discord

Founding Member -=[Team Kraaken]=- Ka Pla

Image
Winners of Gridwars 2010
MBN Fall Tournament 2011 winners Team Kraaken
Undisputed Champions of 2019 HHT Just for showing up!

The Oldist , Longist Running , Orginal Registered Owner of a TWGS server :
Vids World On Guam


Wed Sep 23, 2015 10:03 am
Profile WWW
Chief Warrant Officer

Joined: Sat Jul 14, 2012 6:32 pm
Posts: 104
Unread post Re: Anyone else seen this odd behavior between SWATH & TWX?
SteveH_66 wrote:
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. :shock:

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.

_________________
"TW: A proud tradition of...change is the only constant."

-Val


Wed Sep 23, 2015 9:32 pm
Profile
Ensign

Joined: Wed Nov 06, 2002 3:00 am
Posts: 268
Unread post Re: Anyone else seen this odd behavior between SWATH & TWX?
Thanks for the reassurance Vid, like I said kind of unnerving to see your script get out ahead of the Telnet client and quit halfway before it's done :shock:

CBYNot wrote:

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.


Thanks for the tip CBYNot, with my scripting skills (or lack thereof? :lol: ), I don't need outside factors introducing problems into my scripting, then having to figure out was it me (most of the time probably) or the Helper. :mrgreen:


Thu Sep 24, 2015 9:01 am
Profile
Ambassador
User avatar

Joined: Wed Apr 20, 2011 1:19 pm
Posts: 2559
Location: Oklahoma City, OK 73170 US
Unread post Re: Anyone else seen this odd behavior between SWATH & TWX?
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.

_________________
Regards,
Micro

Website: http://www.microblaster.net
TWGS2.20b/TW3.34: telnet://twgs.microblaster.net:2002

ICQ is Dead Jim! Join us on Discord:
https://discord.gg/zvEbArscMN


Thu Sep 24, 2015 2:13 pm
Profile ICQ YIM WWW
Ensign

Joined: Wed Nov 06, 2002 3:00 am
Posts: 268
Unread post Re: Anyone else seen this odd behavior between SWATH & TWX?
Micro wrote:
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.


Thanks for that information Micro. I was just unnerved to see it finishing up that fast. Somehow I messed that one up and had to rewrite the whole script, I did a couple of versions. One of them has some waiton's in it that kind of slows it down, the faster one has less of them and it goes pretty quick. I'm sure it could be optimized to run even faster, could probably even be written in a totally different way than what I did. Mine is just an amateur creation. I think I'll post them to another post, so anyone that wants to use them can download them if they want. Or you pro's could even download them for a few chuckles. :lol:


Thu Sep 24, 2015 3:19 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 6 posts ] 

Who is online

Users browsing this forum: No registered users and 23 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by STSoftware.