I am playing in a game on Y-City where the games Latency emulation is set to 100ms but ProPing.ts says my ping is several times that 400-500. (Immediately logoff and on to Microblaster.net ping is 200)

Some Pack2 and mombot scripts are just sitting waiting for things like command prompts from TWGS which have already passed, is this because of the ping difference? Normally my ping is much lower than this <200 and I wonder if this server has a poor ping + latency setting are the problem....

Anything I can do about this? Anyone else see this with new TWGS?

Ping scripts send information to the TWGS and wait for it to show back up. The wait is timed in ms. The ping rate you have should result in a laggy feeling on the game. The ping rate "shouldn't" have an effect on the script activation esp since they are coming in slow.

You might check your All Keys setting and make sure it is set to space if you haven't already.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Can you do a network ping to the Y-City server so we can compare the actual network ping to the in-game ping you're measuring? For Windows, you can use PING.EXE to get a measurement. I'd like to see two measurements taken at the same time, one from a ping program and one from your script.

ProPing avg: 482
ping : 156 ms
ping : 532 ms
ping : 468 ms
ping : 469 ms
ping : 500 ms
ping : 485 ms
ping : 500 ms
ping : 500 ms
ping : 500 ms
ping : 437 ms
(Strangely first one is always low <200 then rest are around 500ms)

Windows Ping avg: 153

Just happened again running mombot wsst on first steal cycle here is game log:
<Thievery>

Docking
[Pause]

(R)ob this port, (S)teal product or (Q)uit (?=Help) S


Which product? (1)Fuel Ore, (2)Organics or (3)Equipment (Q=Quit) ? 3


How many holds of Equipment to swipe? [255] 255
You start your droids loading the cargo and...
Command [TL=00:00:00]:[12445] (?=Help)? : X

<I> Ship details

Choose which ship to beam to (Q=Quit) 10
Security code accepted, engaging transporter control.
<I> Ship details

Choose which ship to beam to (Q=Quit)


Command [TL=00:00:00]:[3179] (?=Help)? :

DUMPED Triggers in twxproxy are waiting for success or bust message from TW which does not appear in log, so not transmitted or received?

ProPing script Avg right after 500 (nearly all were exactly 500)
Windows Ping Avg. 156

Looking at the output for robbing ports, I noticed that the "success" is being written at the start of the line, not at the end where it should be. So something has changed there. I wonder if that change is what's causing the trigger to miss? Or is this just a coincidence?

Either way, I'm going to try to figure out why that output changed and get it cleaned up. The ping issue may be a separate issue, and I'm looking into that as well.

I heard there were changes to actually abort display of the xport list verus prior calculation of all the distances of ships. Since this is so close to that and this script macros that part I believe could it be aborting display of part of the rob in addition to the xport that happens right after? Probably not helpful since I know very little about programming but it came to mind.

Also this might be pertinent, there is a 2s Rob/Steal delay set in this game.

If your running wsst or turbo sst those long delays are screwing with the scripts. While that delay is happening the script is still shooting out the information....

You know what, I bet that's it. It does look like the output was aborted. If I go in manually to steal product and I get the "loading the cargo and..." prompt, then press space during the 2 second delay, I don't see the "success" output and it drops to the command prompt without a line between the "loading cargo" line and the command line, exactly as you show in your output.

I can fix it so that space doesn't abort this output. And we can address any other problems like this as we see them.

I'm almost certain this is the cause. I'll upload a fix on twgs.classictw.com and hopefully you can test it out there.

Is this related to the abort thing? Is the trigger ever actually coming? We had a problem where the "Success!" line was being aborted.

Yeah, it's both. I'll fix it.

I made a change intended to allow the game to continue to process events during delays like the 2 second rob/steal delay. These events can include record updates or a change in the state of the player (for example, the port gets blown up). What you're seeing is a side-effect of this change, but it's not a necessary side-effect. I'll clean it up.