server
username
password
channel
PVPGN
war3version
with
port
exeversion
exeversionhash
passwordhashtype
to a PVPGN server)
If GProxy++ doesn't receive a W3GS action for 60 seconds it will "use up" one of
the available empty actions to keep the Warcraft III client interested.
If it doesn't have any more empty actions available it will give up and allow Wa
rcraft III to disconnect.
This is because generating another empty action for the Warcraft III client woul
d result in a desync upon reconnection.
After reconnecting GProxy++ knows how many empty actions it had to use while the
connection was broken and only sends the remaining number to the Warcraft III c
lient.
GHost++ itself will only bring up the lag screen for a disconnected GProxy++ cli
ent when the client falls behind by bot_synclimit messages.
This means it's important for bot_synclimit to be set to a "reasonable value" wh
en allowing GProxy++ reconnections.
Otherwise the game will not be paused while waiting and when GProxy++ reconnects
the game will play in fast forward for the player until catching up.
During the catchup period the player will not be able to control their units.
Note that very occasionally the game temporarily enters a state where empty acti
ons cannot be generated.
If the connection is broken while in this state GProxy++ will be limited to 65 s
econds to reconnect regardless of the server's configuration.
In most games this will only happen a couple of times for a fraction of a second
each time, but note that the lower the server's bot_latency the less chance of
this happening.