/ghost configurator/ghost configurator/bin/Debug/default.cfg

http://ghostcb.googlecode.com/ · Unknown · 489 lines · 330 code · 159 blank · 0 comment · 0 complexity · 3fe88e0d862610b53a6362e54f249f1d MD5 · raw file

  1. #####################
  2. # BOT CONFIGURATION #
  3. #####################
  4. ### the log file
  5. bot_log = ghost.log
  6. ### the log method
  7. ### set this to 1 to leave the log unlocked while GHost++ is running (may be slower, particularly on Windows)
  8. ### set this to 2 to lock the log while GHost++ is running (may be faster, particularly on Windows)
  9. ### note: if the log is locked you will not be able to edit/move/delete it while GHost++ is running
  10. bot_logmethod = 1
  11. ### the language file
  12. bot_language = language.cfg
  13. ### the path to your local Warcraft III directory
  14. ### this path must contain war3.exe, storm.dll, and game.dll
  15. ### 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)
  16. ### 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
  17. bot_war3path = C:\Program Files\Warcraft III
  18. ### whether to act as Warcraft III: The Frozen Throne or not
  19. ### 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 battle.net)
  20. ### set this to 1 to act as Warcraft III: The Frozen Throne (you WILL need to enter a TFT cd key to login to battle.net)
  21. bot_tft = 1
  22. ### the address GHost++ will bind to when hosting games (leave it blank to bind to all available addresses)
  23. ### if you don't know what this is just leave it blank
  24. bot_bindaddress =
  25. ### the port GHost++ will host games on (this must be different from your admingame_port)
  26. bot_hostport = 6112
  27. ### whether to allow GProxy++ reliable reconnects or not
  28. ### you should ensure that bot_synclimit is set to a reasonable value if you choose to allow GProxy++ reliable reconnects
  29. ### a reasonable value is 5000 divided by bot_latency, e.g. if bot_latency is 100 use a value of 50 for bot_synclimit
  30. bot_reconnect = 0
  31. ### the port GHost++ will listen for GProxy++ reliable reconnects on
  32. bot_reconnectport = 6114
  33. ### the maximum number of minutes to wait for a GProxy++ client to reconnect to the game
  34. ### if you set this to 0 or 1 GHost++ will wait for up to 1 minute
  35. ### if you set this to 10 or more GHost++ will only wait for up to 10 minutes
  36. ### due to the way GProxy++ works, increasing this value increases bandwidth requirements and CPU requirements on the players' computers
  37. ### players can always vote to drop a player who is lagging after waiting 45 seconds regardless of this value
  38. bot_reconnectwaittime = 3
  39. ### maximum number of games to host at once
  40. bot_maxgames = 5
  41. ### command trigger for ingame only (battle.net command triggers are defined later)
  42. bot_commandtrigger = !
  43. ### the path to the directory where you keep your map config files
  44. ### this directory can also contain common.j and blizzard.j (extracted from War3Patch.mpq)
  45. ### 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
  46. bot_mapcfgpath = mapcfgs
  47. ### the path to the directory where you keep your savegame files
  48. bot_savegamepath = savegames
  49. ### the path to the directory where you keep your map files
  50. ### GHost++ doesn't require map files but if it has access to them it can send them to players and automatically calculate most map config values
  51. ### GHost++ will search [bot_mappath + map_localpath] for the map file (map_localpath is set in each map's config file)
  52. bot_mappath = maps
  53. ### whether to save replays or not
  54. bot_savereplays = 0
  55. ### the path to the directory where you want GHost++ to save replays
  56. bot_replaypath = replays
  57. ### the Warcraft 3 version to save replays as
  58. replay_war3version = 24
  59. ### the Warcraft 3 build number to save replays as (this is specific to each Warcraft 3 version)
  60. ### patch 1.23: war3version 23, buildnumber 6058
  61. ### patch 1.24: war3version 24, buildnumber 6059
  62. ### patch 1.24b: war3version 24, buildnumber 6059
  63. replay_buildnumber = 6059
  64. ### the bot's virtual host name as it appears in the game lobby
  65. ### colour codes are defined by the sequence "|cFF" followed by a six character hexadecimal colour in RRGGBB format (e.g. 0000FF for pure blue)
  66. ### the virtual host name cannot be longer than 15 characters including the colour code, if you try to go over this limit GHost++ will use the default virtual host name
  67. bot_virtualhostname = |cFF4080C0GHost
  68. ### whether to hide each player's IP address from other players or not
  69. bot_hideipaddresses = 0
  70. ### whether to check for multiple IP address usage or not
  71. bot_checkmultipleipusage = 1
  72. ### whether to do automatic spoof checks or not
  73. ### you can always manually spoof check by whispering the bot (and in fact this is required before running admin commands)
  74. ### set to 0 to disable automatic spoof checks
  75. ### set to 1 to enable automatic spoof checks on all players
  76. ### set to 2 to enable automatic spoof checks on potential admins only
  77. bot_spoofchecks = 2
  78. ### whether to require spoof checks or not
  79. ### this controls whether the bot will require players to spoof check before starting the game
  80. ### it does NOT control whether the bot will require players to spoof check before running admin commands - spoof checks are ALWAYS required for admin status
  81. ### if you require spoof checks, players will be kicked from the lobby if they haven't spoof checked within 20 seconds of joining (autohosted games only)
  82. bot_requirespoofchecks = 0
  83. ### whether to consider admins and root admins as reserved players or not
  84. ### reserved players are allowed to join full games because another player will be kicked to allow them to join
  85. bot_reserveadmins = 1
  86. ### whether to display game refresh messages by default
  87. ### this can always be changed for a particular game with the !refresh command
  88. bot_refreshmessages = 0
  89. ### whether to automatically lock games when the owner joins
  90. bot_autolock = 0
  91. ### whether to automatically save games when a player disconnects
  92. ### this can always be changed for a particular game with the !autosave command
  93. bot_autosave = 0
  94. ### whether to allow map downloads or not
  95. ### set to 0 to disable map downloads
  96. ### set to 1 to enable map downloads
  97. ### set to 2 to enable conditional map downloads (an admin must start each map download with the !download or !dl command)
  98. bot_allowdownloads = 1
  99. ### whether to ping players during map downloads or not
  100. ### GHost++ will always stop pinging any players who are downloading the map
  101. ### this config value determines whether GHost++ should stop pinging *all* players when at least one player is downloading the map
  102. bot_pingduringdownloads = 0
  103. ### the maximum number of players allowed to download the map at the same time
  104. bot_maxdownloaders = 3
  105. ### the maximum combined download speed of all players downloading the map (in KB/sec)
  106. bot_maxdownloadspeed = 100
  107. ### use LC style pings (divide actual pings by two)
  108. bot_lcpings = 1
  109. ### auto kick players with ping higher than this
  110. bot_autokickping = 400
  111. ### the ban method
  112. ### if bot_banmethod = 1, GHost++ will automatically reject players using a banned name
  113. ### if bot_banmethod = 2, GHost++ will automatically reject players using a banned IP address
  114. ### if bot_banmethod = 3, GHost++ will automatically reject players using a banned name or IP address
  115. ### if bot_banmethod is anything else GHost++ will print a message when a banned player joins but will not automatically reject them
  116. bot_banmethod = 1
  117. ### the IP blacklist file
  118. bot_ipblacklistfile = ipblacklist.txt
  119. ### automatically close the game lobby if a reserved player (or admin) doesn't join it for this many minutes
  120. ### games which are set to automatically start when enough players join are exempt from this limit (e.g. autohosted games)
  121. bot_lobbytimelimit = 10
  122. ### the game latency
  123. ### this can always be changed for a particular game with the !latency command (which enforces a minimum of 20 and a maximum of 500)
  124. bot_latency = 100
  125. ### the maximum number of packets a player is allowed to get out of sync by before starting the lag screen
  126. ### before version 8.0 GHost++ did not have a lag screen which is the same as setting this to a very high number
  127. ### this can always be changed for a particular game with the !synclimit command (which enforces a minimum of 10 and a maximum of 10000)
  128. bot_synclimit = 50
  129. ### whether votekicks are allowed or not
  130. bot_votekickallowed = 1
  131. ### the percentage of players required to vote yes for a votekick to pass
  132. ### the player starting the votekick is assumed to have voted yes and the player the votekick is started against is assumed to have voted no
  133. ### the formula for calculating the number of votes needed is votes_needed = ceil( ( num_players - 1 ) * bot_votekickpercentage / 100 )
  134. ### this means it will round UP the number of votes required
  135. ### if you set it to 100 it will require 2/3, 3/4, 4/5, 5/6, 6/7, 7/8, 8/9, 9/10, 10/11, and 11/12 votes to pass
  136. ### if you set it to 90 it will require 2/3, 3/4, 4/5, 5/6, 6/7, 7/8, 8/9, 9/10, 9/11, and 10/12 votes to pass
  137. ### if you set it to 80 it will require 2/3, 3/4, 4/5, 4/6, 5/7, 6/8, 7/9, 8/10, 8/11, and 9/12 votes to pass
  138. ### if you set it to 70 it will require 2/3, 3/4, 3/5, 4/6, 5/7, 5/8, 6/9, 7/10, 7/11, and 8/12 votes to pass
  139. ### if you set it to 60 it will require 2/3, 2/4, 3/5, 3/6, 4/7, 5/8, 5/9, 6/10, 6/11, and 7/12 votes to pass
  140. bot_votekickpercentage = 100
  141. ### the default map config (the ".cfg" will be added automatically if you leave it out)
  142. bot_defaultmap = wormwar
  143. ### the MOTD file
  144. ### the first 8 lines of this file will be displayed when a player joins the game
  145. ### if this file doesn't exist a default MOTD will be used
  146. bot_motdfile = motd.txt
  147. ### the gameloaded file
  148. ### the first 8 lines of this file will be displayed when the game finished loading (after the player loading times are displayed)
  149. bot_gameloadedfile = gameloaded.txt
  150. ### the gameover file
  151. ### the first 8 lines of this file will be displayed when the game is over
  152. ### this only works when using a stats class - note: at the time of this writing the only stats class is for DotA maps
  153. bot_gameoverfile = gameover.txt
  154. ### whether to send "local admin messages" or not
  155. ### these messages are battle.net chat messages, whispers, and emotes which the bot receives and passes on to the "local admin"
  156. ### the local admin is the game owner if they are playing from a LAN or the same computer as the bot
  157. ### this is useful when you are using the admin game to play with one set of CD keys and you want messages sent to the bot to be relayed to you
  158. ### you can enable or disable this for a particular game with the !messages command
  159. bot_localadminmessages = 1
  160. ### the "TCP no delay" flag
  161. ### this controls whether or not your operating system should use the "no delay" algorithm on game sockets
  162. ### the algorithm is designed to reduce latency by sending data in small packets as soon as possible rather than waiting to send a single larger packet
  163. ### enabling this algorithm requires additional bandwidth because it is a less efficient way of sending data
  164. ### however, it may reduce game latencies in some cases
  165. tcp_nodelay = 0
  166. ### the matchmaking method
  167. ### this controls how the bot matches players when they join the game when using !autohostmm
  168. ### set it to 0 to disable matchmaking (first come first served, even if their scores are very different)
  169. ### set it to 1 to use the "furthest score" method (the player with the furthest score from the average is kicked to make room for another player)
  170. ### set it to 2 to use the "lowest score" method (the player with the lowest score is kicked to make room for another player)
  171. bot_matchmakingmethod = 1
  172. ############################
  173. # ADMIN GAME CONFIGURATION #
  174. ############################
  175. ### whether to create the admin game or not (see readme.txt for more information)
  176. admingame_create = 0
  177. ### the port GHost++ will host the admin game on (this must be different from your bot_hostport)
  178. admingame_port = 6113
  179. ### the admin game password
  180. admingame_password =
  181. ### the default map config to use in the admin game
  182. ### if this value is blank the bot will use a hardcoded map instead
  183. ### it's recommended that you use the hardcoded map instead of specifying a different one
  184. ### this value exists because the hardcoded map is specific to Warcraft 3 versions and you may wish to use a previous or newer version
  185. ### the ".cfg" will be added automatically if you leave it out
  186. admingame_map =
  187. #####################
  188. # LAN CONFIGURATION #
  189. #####################
  190. ### the Warcraft 3 version to use when broadcasting LAN games
  191. lan_war3version = 24
  192. ### the UDP broadcast target
  193. ### if this value is blank the bot will try to broadcast LAN games on the default interface which is chosen by your operating system
  194. ### sometimes your operating system will choose the wrong interface when more than one exists
  195. ### therefore you can use this value to force the bot to use a specific interface
  196. ### for example you may set it to "192.168.1.255" to broadcast LAN games to the 192.168.1.x subnet
  197. udp_broadcasttarget =
  198. ### the UDP "don't route" flag
  199. udp_dontroute = 0
  200. ##########################
  201. # AUTOHOST CONFIGURATION #
  202. ##########################
  203. ### this section of the config file is for enabling autohost when the bot starts up without having to issue a command
  204. ### you can activate the autohost feature without changing anything here by using the !autohost command
  205. autohost_maxgames = 0
  206. autohost_startplayers = 0
  207. autohost_gamename =
  208. autohost_owner =
  209. ##########################
  210. # DATABASE CONFIGURATION #
  211. ##########################
  212. ### database type
  213. ### use "sqlite3" for a local SQLite database
  214. ### use "mysql" for any MySQL database
  215. db_type = sqlite3
  216. ### sqlite3 database configuration
  217. ### this is only used if your database type is SQLite
  218. db_sqlite3_file = ghost.dbs
  219. ### mysql database configuration
  220. ### this is only used if your database type is MySQL
  221. db_mysql_server = localhost
  222. db_mysql_database = ghost
  223. db_mysql_user = YOUR_USERNAME
  224. db_mysql_password = YOUR_PASSWORD
  225. db_mysql_port = 0
  226. ### the bot ID is included each time the bot adds data to the MySQL database
  227. ### it is used to identify where each row of data came from when you configure multiple bots to connect to the same MySQL database
  228. ### GHost++ does not use the bot ID number itself, it's just to help you keep track of the data in your database
  229. db_mysql_botid = 1
  230. ############################
  231. # BATTLE.NET CONFIGURATION #
  232. ############################
  233. ### which battle.net server to connect to
  234. ### 1.) useast.battle.net
  235. ### 2.) uswest.battle.net
  236. ### 3.) asia.battle.net
  237. ### 4.) europe.battle.net
  238. ### note that each banned player is tied to the realm it was created on and the realm is case sensitive
  239. ### so if you change your realm from useast.battle.net to USEAST.BATTLE.NET it'll still connect but anyone previously banned will not be counted as banned until you change it back
  240. bnet_server = useast.battle.net
  241. ### the server alias
  242. ### this name will be used to identify the battle.net server in the GHost++ console
  243. ### if you leave it blank it will use a short name such as "USEast" for official battle.net servers or it will use the actual server address
  244. bnet_serveralias = USEast
  245. ### your Warcraft III: Reign of Chaos CD key
  246. ### you cannot use the same CD key here that you yourself use to login to battle.net if you plan to login at the same time as your bot
  247. bnet_cdkeyroc = FFFFFFFFFFFFFFFFFFFFFFFFFF
  248. ### your Warcraft III: The Frozen Throne CD key
  249. ### you cannot use the same CD key here that you yourself use to login to battle.net if you plan to login at the same time as your bot
  250. bnet_cdkeytft = FFFFFFFFFFFFFFFFFFFFFFFFFF
  251. ### the locale specifies the area of the world you are from
  252. ### battle.net uses this to group players together, showing them games hosted by players and bots mostly from their own area
  253. ### it's important to set this to the correct value to increase the effectiveness of the game refresher
  254. ### if you are using Windows you can set this to "system" to use the locale of your system
  255. ### otherwise you can use the list at the following URL to get the correct value for your area:
  256. ### http://msdn.microsoft.com/en-us/library/0h88fahh%28VS.85%29.aspx
  257. ### put the "decimal value" here, e.g. 1033 is the default for "English - United States"
  258. ### note: you cannot use a value of "system" on Linux, doing so will use a default value of 1033 instead
  259. bnet_locale = system
  260. ### your battle.net username
  261. ### you cannot use the same username here that you yourself use to login to battle.net if you plan to login at the same time as your bot
  262. bnet_username =
  263. ### your battle.net password
  264. bnet_password =
  265. ### the first channel to join upon entering battle.net
  266. bnet_firstchannel = The Void
  267. ### the root admins on this battle.net server only
  268. ### seperate each name with a space, e.g. bnet_rootadmin = Varlock Kilranin Instinct121
  269. bnet_rootadmin =
  270. ### command trigger for this battle.net server only
  271. bnet_commandtrigger = !
  272. ### whether to automatically add your friends list to each game's reserved list
  273. bnet_holdfriends = 1
  274. ### whether to automatically add your clan members list to each game's reserved list
  275. bnet_holdclan = 1
  276. ### whether to allow anonymous users (non admins) to use public commands such as !stats and !statsdota on this battle.net connection
  277. ### if you are having trouble with spammers causing your bot to flood the server you should disable this
  278. bnet_publiccommands = 1
  279. ### BNLS server information for Warden handling (see readme.txt for more information)
  280. ### you will need to use a valid BNLS server here if you are connecting to an official battle.net realm or you will be disconnected every two minutes
  281. bnet_bnlsserver = localhost
  282. bnet_bnlsport = 9367
  283. bnet_bnlswardencookie = 1
  284. ### you will need to edit this section of the config file if you're connecting to a PVPGN server
  285. ### your PVPGN server operator will tell you what to put here
  286. bnet_custom_war3version = 24
  287. bnet_custom_exeversion =
  288. bnet_custom_exeversionhash =
  289. bnet_custom_passwordhashtype =
  290. bnet_custom_pvpgnrealmname = PvPGN Realm
  291. ###
  292. ### example configuration for connecting to a second official battle.net server
  293. ###
  294. # bnet2_server = uswest.battle.net
  295. # bnet2_serveralias = USWest
  296. # bnet2_cdkeyroc = FFFFFFFFFFFFFFFFFFFFFFFFFF
  297. # bnet2_cdkeytft = FFFFFFFFFFFFFFFFFFFFFFFFFF
  298. # bnet2_locale = system
  299. # bnet2_username =
  300. # bnet2_password =
  301. # bnet2_firstchannel = The Void
  302. # bnet2_rootadmin =
  303. # bnet2_commandtrigger = !
  304. # bnet2_holdfriends = 1
  305. # bnet2_holdclan = 1
  306. # bnet2_publiccommands = 1
  307. # bnet2_bnlsserver = localhost
  308. # bnet2_bnlsport = 9367
  309. # bnet2_bnlswardencookie = 2
  310. ###
  311. ### example configuration for connecting to a third PVPGN battle.net server
  312. ###
  313. # bnet3_server = server.eurobattle.net
  314. # bnet3_serveralias = EuroBattle
  315. # bnet3_cdkeyroc = FFFFFFFFFFFFFFFFFFFFFFFFFF
  316. # bnet3_cdkeytft = FFFFFFFFFFFFFFFFFFFFFFFFFF
  317. # bnet3_locale = system
  318. # bnet3_username =
  319. # bnet3_password =
  320. # bnet3_firstchannel = The Void
  321. # bnet3_rootadmin =
  322. # bnet3_commandtrigger = !
  323. # bnet3_holdfriends = 1
  324. # bnet3_holdclan = 1
  325. # bnet3_publiccommands = 1
  326. # bnet3_custom_war3version = 24
  327. # bnet3_custom_exeversion = 184 0 22 1
  328. # bnet3_custom_exeversionhash = 219 152 153 144
  329. # bnet3_custom_passwordhashtype = pvpgn
  330. # bnet3_custom_pvpgnrealmname = PvPGN Realm