I run a script for our TradeWars Academy game where a fedsweeper script runs. The OCSBot is logged in via admin, switches to TW mode, logs into the game, runs the OCSBot script. Then it logs out, goes to tedit mode, and runs a fedsweeper function. Once done, it returns to TW mode and re-enters the game, etc.

My issue is once in a while the script when going to tedit mode hangs at the Password? prompt. I have the script set to enter the tedit password, but every once in a while that is EXACTLY where it hangs. I'm trying to understand why that is. I can restart the script and then it is fine. I run the TWGS on one machine, and the OCSBot is on a different machine. I was thinking it's a network issue with a dropped packet, but was curious if any of the TWX/script gurus might know why.

I have ran into strange issues with T-Edit scripting that "shouldn't" happen. I would check the triggers that are active at that point to start with. It may be looking for something that isn't there. I've had to use waitfor a lot in T-Edit where I don't have to use it in normal game scripting - "shouldn't" be a difference I would think.

That is probably the exact problem ..
Use waitfor

That is the only way I've gotten the password issue resolved.
refer to my 14_login.ts script for sysops

I go to and from admin to in game and back many times without issues anymore.

I also have encountered this issue sometimes with Sysbot. I have a workaround in mind, just not gotten a chance to code it yet... put a delaytrigger in when the script starts an iteration, make it maybe twice as long as the script normally takes to run, and have it reset at each iteration. If the trigger hits, the script is hung, so I drop the connection and restart the script. This happens even when the TWX is running on the same box as the TWGS.

We had a similar instance too with that, but it has been fine on my end now. I believe you gave Daala a hand with the issue.

Appreciate the help guys.

i've had this problem too and i think i know why it happens. the problem is that behind the scenes twgs.exe is actually handing off responsibility for the user input to tw2002.exe (or tedit.exe?) and if you time it just right when you send your password, it falls between the cracks and neither process catches it. using the waitfor ensures that you're fully in tw2002.exe before you send the password.