# maximum number of games to host at once # players can always vote to drop a player who is lagging after waiting 45 seconds regardless of this value # due to the way GProxy++ works, increasing this value increases bandwidth requirements and CPU requirements on the players' computers # if you set this to 10 or more GHost++ will only wait for up to 10 minutes # if you set this to 0 or 1 GHost++ will wait for up to 1 minute # the maximum number of minutes to wait for a GProxy++ client to reconnect to the game # the port GHost++ will listen for GProxy++ reliable reconnects on if bot_latency is 100 use a value of 50 for bot_synclimit # a reasonable value is 5000 divided by bot_latency, e.g. # you should ensure that bot_synclimit is set to a reasonable value if you choose to allow GProxy++ reliable reconnects # whether to allow GProxy++ reliable reconnects or not # the port GHost++ will host games on (this must be different from your admingame_port) # if you don't know what this is just leave it blank # the address GHost++ will bind to when hosting games (leave it blank to bind to all available addresses) # set this to 1 to act as Warcraft III: The Frozen Throne (you WILL need to enter a TFT cd key to login to ) # set this to 0 to act as Warcraft III: Reign of Chaos (you WILL NOT need to enter a TFT cd key to login to ) # whether to act as Warcraft III: The Frozen Throne or not # common.j and blizzard.j are only required for automatically calculating map_crc, you do not need them if your map config files already contain map_crcīot_war3path = R:\\Warcraft 3 Frozen Throne # if this path contains War3Patch.mpq the bot will attempt to extract "Scripts\common.j" and "Scripts\blizzard.j" on startup and write them to bot_mapcfgpath (which is defined later in this file)
# this path must contain war3.exe, storm.dll, and game.dll # the path to your local Warcraft III directory # note: if the log is locked you will not be able to edit/move/delete it while GHost++ is running # set this to 2 to lock the log while GHost++ is running (may be faster, particularly on Windows) # set this to 1 to leave the log unlocked while GHost++ is running (may be slower, particularly on Windows)
0 kommentar(er)
