here is my ping on this server....
Type sub-space message [<ENTER> to send line. Blank line to end transmission]
S: ping : 172 ms
S: ping : 172 ms
S: ping : 172 ms
S: ping : 172 ms
S: ping : 187 ms
S: ping : 171 ms
S: ping : 171 ms
S: ping : 171 ms
S: ping : 218 ms
S: ping : 172 ms
S: ----------------
S: Min: 171 Max: 218 Average: 177 -- Someone is gonna get podded!
S: High/Low Removed Average: 173
S: Min:Max Split: 47 Minimal Intermittent Lag Detected


I can only play about 15\20 mins, then my cash script (mombot Wsst) just stops? any idea why? is this a server thing, a game setting? or something else?

Just curiuos.

If the ship xport range is too low, it will run until it eventually gets out of range between the 2 ships. This might be the problem and might not. Look at your ship export range and how far away you are from the other ship and see if that may be the problem.

It is not a game setting that causes that, unless the steal factor is high and your experience goes too low (some scripts automatically stop at a preset level). If you can simply restart the script and it runs then this isn't the issue.

Is TWX still responding (not maxing CPU)? Is it stopping in a sector you have busted in before (script issue)? Are you using TWX 2.04 or one of the recent releases? Check the active triggers when the script stops and see what it is looking for ($st) assuming the script doesn't terminate and is just frozen. Are you using Win XP for your OS?

As a wild guess, it is a script issue involving a trigger or wait command. I have a script that runs great for hours and then maxes the CPU and freezes - some kind of loop that I haven't been able to find.

               / Promethius / Enigma / Wolfen /

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

I can simply restart it. Its the same script I use on other servers with no problems. (can run it over night, and its still cashing when I weake up...) This particular game, I go up stairs for a beer, come back down, its stopped. Its not xport range, and It doesnt give me any message. Just stops.

Ya know what..... I thought I was in 2 rums (80 export) but I now notice one is a colo.... Maybe there is something to the xport range.laff Guess too many trips up for another beer. I am trying it again today.

Packet loss.

A trigger that you're waiting on isn't coming in the way it should, and something isn't being triggered.

Next time it happens hit $st and get a list of the triggers it's waiting on. This is why complex trigger-based
stuff needs a timeout built-in to auto-restart as needed.

I will try that, but I am begining to think it was just too much podding oil consumed last night!

Try Turbo SST instead