Perhaps some combat?

Made my moves today and had no problems with port trading. I did notice one other thing, a few times when I typed in an adjacent sector to move to it moved me when I entered the last number before I hit the enter key. This happened a couple times. I have a registered version of TWGS that I host for a few friends of mine and this has never occurred when I play on there so I don't think it is a problem
on my end. It's not a big deal just thought you might want to know.

It's a low turn game so i don't think anyone will be running world trade , well if they do it won't be for long. Game seems to run fast, I just logged in with swath. been moving around and trading and all seems good.

Think we're only supposed to stay logged in. Unless I misunderstood JP's post.

Having said that I goofed around as much as I could with the limited turns and the only issues I came across I was unable to replicate.

Come on you bozos, log in and set your relog. You too Cruncher.

Yeah, log and sit is fine for now. I'm already chasing a few issues just related to that As soon as I'm comfortable with it, I'll reset the game with some settings conducive to some real testing. I appreciate your attention!

About the auto-completion of sector number, that only happens for small sector (< 5000 sectors) games. This game has 1000 sectors, so that's default behavior. You can change that in your personal settings (C/N) if you find it annoying.

Heh.. I saw this late last night and forgot the pword, then remembered to change the port to 23. Hehe.. I'm in there now.

JP give us a few more turns

Great that you showed but perhaps you could stay logged in since I believe that's the whole point of this exercise...not to mention he'll give us turns next bang when he's ready to move past the "everyone join game and stayed logged in" phase.

The main thing I'm testing right now is latency emulation. TWGS needs to estimate the ping time of a connection in order to balance latency. I've added a line to the @ global command to indicate how long ping time is being measured for a connection. If anyone wants to check what TWGS is measuring for ping, here's what you can do. From the same system that is running the client, use ping.exe (assuming it's windows) to twgs.classictw.com and compare the value to the ping amount reported on the @ screen. The difference should not be more than 10 ms or so at most. If it is, let me know so I can analyze your connection stats.

S: ping : 157 ms
S: ping : 156 ms
S: ping : 156 ms
S: ping : 156 ms
S: ping : 156 ms
S: ping : 157 ms
S: ping : 156 ms
S: ping : 141 ms
S: ping : 157 ms
S: ping : 140 ms
S: ----------------
S: Min: 140 Max: 157 Average: 153 -- Someone is gonna get podded!
S: High/Low Removed Average: 154
S: Min:Max Split: 17 No Lag has been Detected


------------------

Trade Wars 2002 Version 3.14
Windows NT - Win32
Using high resolution timer

Average Interval Lag:
0 ms (0%)

Max Interval Lag:
0 ms (0%)

Timestamp: 2256077444

Event Lag: 0 ms

Ping: 46

--------------------------------

Pinging twgs.classictw.com [67.19.41.138] with 32 bytes of data:

Reply from 67.19.41.138: bytes=32 time=65ms TTL=117
Reply from 67.19.41.138: bytes=32 time=49ms TTL=117
Reply from 67.19.41.138: bytes=32 time=48ms TTL=117
Reply from 67.19.41.138: bytes=32 time=48ms TTL=117

Ping statistics for 67.19.41.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 65ms, Average = 52ms

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

Trade Wars 2002 Version 3.14
Windows NT - Win32
Using high resolution timer

Average Interval Lag:
0 ms (0%)

Max Interval Lag:
0 ms (0%)

Timestamp: 2261449928

Event Lag: 0 ms

Ping: 51

Who's Playing

Gunnery Sergeant Crosby [3]
Staff Sergeant Tommy Gunn [1]
Gunnery Sergeant TesteR Extremist [2]
Civilian hitechredneck



Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

*:\*****\****>ping twgs.classictw.com

Pinging twgs.classictw.com [67.19.41.138] with 32 bytes of data:
Reply from 67.19.41.138: bytes=32 time=73ms TTL=115
Reply from 67.19.41.138: bytes=32 time=60ms TTL=115
Reply from 67.19.41.138: bytes=32 time=58ms TTL=115
Reply from 67.19.41.138: bytes=32 time=58ms TTL=115

Ping statistics for 67.19.41.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 73ms, Average = 62ms

Using Swath 1.9.8 without TWX...

Ping from twx/mombot

Type sub-space message [<ENTER> to send line. Blank line to end transmission]
S: ping : 165 ms
S: ping : 162 ms
S: ping : 160 ms
S: ping : 161 ms
S: ping : 163 ms
S: ping : 160 ms
S: ping : 161 ms
S: ping : 161 ms
S: ping : 162 ms
S: ping : 161 ms
S: ----------------
S: Min: 160 Max: 165 Average: 161 -- Someone is gonna get podded!
S: High/Low Removed Average: 161
S: Min:Max Split: 5 No Lag has been Detected
S:

Sub-space comm-link terminated

Command [TL=00:00:00]:[800] (?=Help)? :
Script terminated: scripts\MomBot\Commands\Data\ping.cts

Trade Wars 2002 Version 3.14
Windows NT - Win32
Using high resolution timer

Average Interval Lag:
0 ms (0%)

Max Interval Lag:
0 ms (0%)

Timestamp: 2262281626

Event Lag: 0 ms

Ping: 33

"I've added a line to the @ global command to indicate how long ping time is being measured for a connection. If anyone wants to check what TWGS is measuring for ping, here's what you can do. From the same system that is running the client, use ping.exe (assuming it's windows) to twgs.classictw.com and compare the value to the ping amount reported on the @ screen." -so says JP if you would only read ....

oh and it helps to actually be in the twgs.classictw.com game R when you run the tests lol

It's important to realize that the TW definition of "ping" isn't what I'm referring to here. I'm talking about the ICMP ping as measured by programs like windows ping.exe. The TW ping measurement includes internal TW delays which are now configurable in TEDIT. For one, it includes the emulated latency of 150 ms. These values look reasonable.

So we're done with this round of testing and can move on to the more fun "more turns" phase?

I'm not beta testing, but this is to give you guys an example of system ping. If you are using windows open up the dos prompt window and type the following.

C:\>ping twgs.classictw.com <<<< (This is the command line)

Pinging twgs.classictw.com [67.19.41.138] with 32 byte

Reply from 67.19.41.138: bytes=32 time=73ms TTL=115
Reply from 67.19.41.138: bytes=32 time=74ms TTL=115
Reply from 67.19.41.138: bytes=32 time=77ms TTL=115
Reply from 67.19.41.138: bytes=32 time=77ms TTL=115

Ping statistics for 67.19.41.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 77ms, Average = 75ms

C:\>