Before the incident with the data loss at the hosting company, CF was hosted on the east coast I think. Now its hosted somewhere in texas, and if my traceroute is correct near the mexican border. This increase european reponse times from 130-150 into the 180-200 region. May not sound like alot, but we already had tight timings at 130-150 in regards to getting abilities "in before the round". With a response time of 180-200 it would mean we always and at all times play 1 tick behind the US players.

So assuming the logic at the server end is something like this:

pulse_start -> send_data/receive_data -> pulse_end .. PROCESS ..

and that your roundtrip to the CF server is 200ms, a pulse
(time between pulse_start/pulse_end) would have to take 200ms or
less in order for you to have a chance to miss it.

200 ms pulse time means that there are 5 pulses a second which is
clearly not the case with CF. I do not know the exact duration
but empirically i'd estimate it at 400ms, possibly more.


So, 200ms roundtrip to the server should not affect your command
inputs and you shouldn't be disadvantaged (in combat).

EDIT:

Forgot to mention that the above does not include human reaction
times so if we assume that your reaction time is 300ms (sort of optimistic and implies that you never type but use predefined macros)
then with a pulse time of 400ms you can miss commands..

When i was playing from Europe, my roundtrip to CF was, at times,
500+ milliseconds. I had to stack commands and have the battle
strategy mostly predetermined in order not to miss rounds.

It was formerly hosted in Texas. Houston, I think. Now it's in the Phoenix/Tempe area.

Notice the first jump when it moves across the atlantic ocean, then second when it moves from DC to Atlanta, then third jump when it moves to Phoenix.

Target Name: carrionfields.net
IP: 66.85.154.235
Date/Time: 21.02.2012 10:35:55 to 21.02.2012 10:52:48

Hop Sent Err PL% Min Max Avg Host Name /
1 1000 0 0,0 0 0 0 unknown <192.168.1.1>
2 1000 0 0,0 3 31 7 <10.197.64.1>
3 1000 0 0,0 4 132 12 <62.92.86.109>
4 1000 0 0,0 4 63 9 ti0048d320-ge1-1-0-10.ti.telenor.net <146.172.84.201>
5 1000 0 0,0 4 75 14 ti0001c310-xe7-1-2.ti.telenor.net <146.172.98.1>
6 1000 0 0,0 4 64 10 ti0001b300-ae1-0.ti.telenor.net <146.172.105.10>
7 1000 0 0,0 4 218 17 te3-7.ccr01.osl01.atlas.cogentco.com <130.117.14.21>
8 1000 0 0,0 23 46 27 te0-1-0-5.ccr21.ham01.atlas.cogentco.com <130.117.2.177>
9 1000 0 0,0 36 64 39 te0-1-0-3.mpd21.ams03.atlas.cogentco.com <130.117.50.53>
10 1000 0 0,0 45 71 49 te0-0-0-2.ccr21.lpl01.atlas.cogentco.com <154.54.37.70>
11 1000 0 0,0 117 151 121 te0-2-0-3.ccr21.bos01.atlas.cogentco.com <154.54.31.189>
12 1000 0 0,0 113 137 117 te0-5-0-3.mpd21.jfk02.atlas.cogentco.com <154.54.44.17>
13 1000 0 0,0 120 147 123 te0-1-0-4.mpd21.dca01.atlas.cogentco.com <154.54.2.66>
14 1000 0 0,0 145 168 148 te0-0-0-6.mpd21.atl01.atlas.cogentco.com <154.54.28.198>
15 1000 0 0,0 145 172 148 te0-1-0-2.mpd21.iah01.atlas.cogentco.com <154.54.5.202>
16 1000 0 0,0 150 533 192 te4-3.ccr01.sat01.atlas.cogentco.com <154.54.46.6>
17 1000 0 0,0 175 588 212 te7-1.ccr01.phx02.atlas.cogentco.com <154.54.6.249>
18 1000 0 0,0 174 198 178 vl3512.na41.b023003-0.phx02.atlas.cogentco.com <38.20.49.214>
19 1000 0 0,0 184 207 188 <38.104.116.74>
20 998 821 82,3 185 361 193 bb2.cwie.10.2.phx0.cwie.net <64.38.200.5>
21 997 997 100,0 0 0 0 <->
22 997 997 100,0 0 0 0 <->
23 1000 0 0,0 185 213 188 <66.85.154.234>
24 1000 0 0,0 179 204 183 riverwind.thirdhosting.com <66.85.154.235>