Advertisement
Guest User

Untitled

a guest
Aug 11th, 2017
107
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 15.24 KB | None | 0 0
  1. #####################
  2. # BOT CONFIGURATION #
  3. #####################
  4.  
  5. ### the log file
  6.  
  7. bot_log = ghost.log
  8.  
  9. ### the language file
  10.  
  11. bot_language = language.cfg
  12.  
  13. ### the path to your local Warcraft III directory
  14. ### this path must contain war3.exe, storm.dll, and game.dll
  15. ### this path must end in your system's path seperator (i.e. "\" on Windows or "/" on Linux)
  16. ### 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)
  17. ### 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
  18.  
  19. bot_war3path = C:\Program Files (x86)\Warcraft III\
  20.  
  21. ### the address GHost++ will bind to when hosting games (leave it blank to bind to all available addresses)
  22. ### if you don't know what this is just leave it blank
  23.  
  24. bot_bindaddress =
  25.  
  26. ### the port GHost++ will host battle.net games on (this must be different from your admingame_port)
  27.  
  28. bot_hostport = 6112
  29.  
  30. ### maximum number of games to host at once
  31.  
  32. bot_maxgames = 5
  33.  
  34. ### command trigger for ingame only (battle.net command triggers are defined later)
  35.  
  36. bot_commandtrigger = !
  37.  
  38. ### the path to the directory where you keep your map config files (must end in your system's path seperator)
  39. ### this directory can also contain common.j and blizzard.j (extracted from War3Patch.mpq)
  40. ### 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
  41.  
  42. bot_mapcfgpath = mapcfgs\
  43.  
  44. ### the path to the directory where you keep your savegame files (must end in your system's path seperator)
  45.  
  46. bot_savegamepath = savegames\
  47.  
  48. ### the path to the directory where you keep your map files (must end in your system's path seperator)
  49. ### 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
  50. ### GHost++ will search [bot_mappath + map_localpath] for the map file (map_localpath is set in each map's config file)
  51.  
  52. bot_mappath = Maps\
  53.  
  54. ### whether to save replays or not
  55.  
  56. bot_savereplays = 0
  57.  
  58. ### the path to the directory where you want GHost++ to save replays (must end in your system's path seperator)
  59.  
  60. bot_replaypath = replays\
  61.  
  62. ### the Warcraft 3 version to save replays as
  63.  
  64. replay_war3version = 24
  65.  
  66. ### the Warcraft 3 build number to save replays as (this is specific to each Warcraft 3 version)
  67. ### patch 1.23: war3version 23, buildnumber 6058
  68. ### patch 1.24: war3version 24, buildnumber 6059
  69.  
  70. replay_buildnumber = 6059
  71.  
  72. ### the bot's virtual host name as it appears in the game lobby
  73. ### colour codes are defined by the sequence "|cFF" followed by a six character hexadecimal colour in RRGGBB format (e.g. 0000FF for pure blue)
  74. ### 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
  75.  
  76. bot_virtualhostname = |cFF0080FFGhost
  77.  
  78. ### whether to hide each player's IP address from other players or not
  79.  
  80. bot_hideipaddresses = 0
  81.  
  82. ### whether to check for multiple IP address usage or not
  83.  
  84. bot_checkmultipleipusage = 1
  85.  
  86. ### whether to require spoof checks or not
  87. ### disabling spoof checks just turns off automatic spoof checks and requiring players to be spoof checked before starting the game
  88. ### spoof checks need to be enabled if you want GHost++ to detect which realm each player came from (use the !check command to see the realm)
  89. ### you can always manually spoof check by whispering the bot (and in fact is required before running admin commands)
  90.  
  91. bot_spoofchecks = 1
  92.  
  93. ### whether to display game refresh messages by default
  94. ### this can always be changed for a particular game with the !refresh command
  95.  
  96. bot_refreshmessages = 0
  97.  
  98. ### whether to automatically lock games when the owner joins
  99.  
  100. bot_autolock = 0
  101.  
  102. ### whether to automatically save games when a player disconnects
  103. ### this can always be changed for a particular game with the !autosave command
  104.  
  105. bot_autosave = 0
  106.  
  107. ### whether to allow map downloads or not
  108. ### set to 0 to disable map downloads
  109. ### set to 1 to enable map downloads
  110. ### set to 2 to enable conditional map downloads (an admin must start each map download with the !download or !dl command)
  111.  
  112. bot_allowdownloads = 1
  113.  
  114. ### whether to ping players during map downloads or not
  115. ### GHost++ will always stop pinging any players who are downloading the map
  116. ### this config value determines whether GHost++ should stop pinging *all* players when at least one player is downloading the map
  117.  
  118. bot_pingduringdownloads = 0
  119.  
  120. ### the maximum number of players allowed to download the map at the same time
  121.  
  122. bot_maxdownloaders = 3
  123.  
  124. ### the maximum combined download speed of all players downloading the map (in KB/sec)
  125.  
  126. bot_maxdownloadspeed = 100
  127.  
  128. ### use LC style pings (divide actual pings by two)
  129.  
  130. bot_lcpings = 1
  131.  
  132. ### auto kick players with ping higher than this
  133.  
  134. bot_autokickping = 400
  135.  
  136. ### the ban method
  137. ### if bot_banmethod = 1, GHost++ will automatically reject players using a banned name
  138. ### if bot_banmethod = 2, GHost++ will automatically reject players using a banned IP address
  139. ### if bot_banmethod = 3, GHost++ will automatically reject players using a banned name or IP address
  140. ### if bot_banmethod is anything else GHost++ will print a message when a banned player joins but will not automatically reject them
  141.  
  142. bot_banmethod = 1
  143.  
  144. ### the IP blacklist file
  145.  
  146. bot_ipblacklistfile = ipblacklist.txt
  147.  
  148. ### automatically close the game lobby if a reserved player (or admin) doesn't join it for this many minutes
  149. ### games which are set to automatically start when enough players join are exempt from this limit (e.g. autohosted games)
  150.  
  151. bot_lobbytimelimit = 10
  152.  
  153. ### the game latency
  154. ### this can always be changed for a particular game with the !latency command (which enforces a minimum of 50 and a maximum of 500)
  155.  
  156. bot_latency = 100
  157.  
  158. ### the maximum number of packets a player is allowed to get out of sync by before starting the lag screen
  159. ### before version 8.0 GHost++ did not have a lag screen which is the same as setting this to a very high number
  160. ### this can always be changed for a particular game with the !synclimit command (which enforces a minimum of 10 and a maximum of 10000)
  161.  
  162. bot_synclimit = 50
  163.  
  164. ### whether votekicks are allowed or not
  165.  
  166. bot_votekickallowed = 1
  167.  
  168. ### the percentage of players required to vote yes for a votekick to pass
  169. ### 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
  170. ### the formula for calculating the number of votes needed is votes_needed = ceil( ( num_players - 1 ) * bot_votekickpercentage / 100 )
  171. ### this means it will round UP the number of votes required
  172. ### 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
  173. ### 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
  174. ### 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
  175. ### 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
  176. ### 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
  177.  
  178. bot_votekickpercentage = 100
  179.  
  180. ### the default map config (the ".cfg" will be added automatically if you leave it out)
  181.  
  182. bot_defaultmap =
  183.  
  184. ### the MOTD file
  185. ### the first 8 lines of this file will be displayed when a player joins the game
  186. ### if this file doesn't exist a default MOTD will be used
  187.  
  188. bot_motdfile = motd.txt
  189.  
  190. ### the gameloaded file
  191. ### the first 8 lines of this file will be displayed when the game finished loading (after the player loading times are displayed)
  192.  
  193. bot_gameloadedfile = gameloaded.txt
  194.  
  195. ### the gameover file
  196. ### the first 8 lines of this file will be displayed when the game is over
  197. ### this only works when using a stats class - note: at the time of this writing the only stats class is for DotA maps
  198.  
  199. bot_gameoverfile = gameover.txt
  200.  
  201. ### whether to use regular expressions when loading map configs and maps or not
  202.  
  203. bot_useregexes = 0
  204.  
  205. ### the "TCP no delay" flag
  206. ### this controls whether or not your operating system should use the "no delay" algorithm on game sockets
  207. ### 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
  208. ### enabling this algorithm requires additional bandwidth because it is a less efficient way of sending data
  209. ### however, it may reduce game latencies in some cases
  210.  
  211. tcp_nodelay = 1
  212.  
  213. ############################
  214. # ADMIN GAME CONFIGURATION #
  215. ############################
  216.  
  217. ### whether to create the admin game or not (see readme.txt for more information)
  218.  
  219. admingame_create = 0
  220.  
  221. ### the port GHost++ will host the admin game on (this must be different from your bot_hostport)
  222.  
  223. admingame_port = 6113
  224.  
  225. ### the admin game password
  226.  
  227. admingame_password =
  228.  
  229. ### the default map config to use in the admin game
  230. ### if this value is blank the bot will use a hardcoded map instead
  231. ### it's recommended that you use the hardcoded map instead of specifying a different one
  232. ### this value exists because the hardcoded map is specific to Warcraft 3 versions and you may wish to use a previous or newer version
  233. ### the ".cfg" will be added automatically if you leave it out
  234.  
  235. admingame_map =
  236.  
  237. #####################
  238. # LAN CONFIGURATION #
  239. #####################
  240.  
  241. ### the Warcraft 3 version to use when broadcasting LAN games
  242.  
  243. lan_war3version = 24
  244.  
  245. ### the UDP broadcast target
  246. ### if this value is blank the bot will try to broadcast LAN games on the default interface which is chosen by your operating system
  247. ### sometimes your operating system will choose the wrong interface when more than one exists
  248. ### therefore you can use this value to force the bot to use a specific interface
  249. ### for example you may set it to "192.168.1.255" to broadcast LAN games to the 192.168.1.x subnet
  250.  
  251. udp_broadcasttarget =
  252.  
  253. ### the UDP "don't route" flag
  254.  
  255. udp_dontroute = 0
  256.  
  257. ##########################
  258. # AUTOHOST CONFIGURATION #
  259. ##########################
  260.  
  261. ### this section of the config file is for enabling autohost when the bot starts up without having to issue a command
  262. ### you can activate the autohost feature without changing anything here by using the !autohost command
  263.  
  264. autohost_maxgames = 0
  265. autohost_startplayers = 0
  266. autohost_gamename =
  267. autohost_owner =
  268.  
  269. ##########################
  270. # DATABASE CONFIGURATION #
  271. ##########################
  272.  
  273. ### database type
  274. ### use "sqlite3" for a local SQLite database
  275. ### use "mysql" for any MySQL database
  276.  
  277. db_type = sqlite3
  278.  
  279. ### sqlite3 database configuration
  280. ### this is only used if your database type is SQLite
  281.  
  282. db_sqlite3_file = ghost.dbs
  283.  
  284. ### mysql database configuration
  285. ### this is only used if your database type is MySQL
  286.  
  287. db_mysql_server = localhost
  288. db_mysql_database = ghost
  289. db_mysql_user = YOUR_USERNAME
  290. db_mysql_password = YOUR_PASSWORD
  291. db_mysql_port = 0
  292.  
  293. ############################
  294. # BATTLE.NET CONFIGURATION #
  295. ############################
  296.  
  297. ### which battle.net server to connect to
  298. ### 1.) useast.battle.net
  299. ### 2.) uswest.battle.net
  300. ### 3.) asia.battle.net
  301. ### 4.) europe.battle.net
  302. ### note that each banned player is tied to the realm it was created on and the realm is case sensitive
  303. ### 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
  304.  
  305. bnet_server = server.eurobattle.net
  306.  
  307. ### the server alias
  308. ### this name will be used to identify the battle.net server in the GHost++ console
  309. ### 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
  310.  
  311. bnet_serveralias = eurobattle
  312.  
  313. ### your Warcraft III: Reign of Chaos CD key
  314. ### 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
  315.  
  316. bnet_cdkeyroc = FFFFFFFFFFFFFFFFFFFFFFFFFF
  317.  
  318. ### your Warcraft III: The Frozen Throne CD key
  319. ### 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
  320.  
  321. bnet_cdkeytft = FFFFFFFFFFFFFFFFFFFFFFFFFF
  322.  
  323. ### your battle.net username
  324. ### 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
  325.  
  326. bnet_username = ghostmielsen
  327.  
  328. ### your battle.net password
  329.  
  330. bnet_password = bonny1986
  331.  
  332. ### the first channel to join upon entering battle.net
  333.  
  334. bnet_firstchannel = W3-Bots
  335.  
  336. ### the root admin on this battle.net server only
  337.  
  338. bnet_rootadmin = mielsen
  339.  
  340. ### command trigger for this battle.net server only
  341.  
  342. bnet_commandtrigger = !
  343.  
  344. ### whether to automatically add your friends list to each game's reserved list
  345.  
  346. bnet_holdfriends = 1
  347.  
  348. ### whether to automatically add your clan members list to each game's reserved list
  349.  
  350. bnet_holdclan = 1
  351.  
  352. ### whether to allow anonymous users (non admins) to use public commands such as !stats and !statsdota on this battle.net connection
  353. ### if you are having trouble with spammers causing your bot to flood the server you should disable this
  354.  
  355. bnet_publiccommands = 1
  356.  
  357. ### BNLS server information for Warden handling (see readme.txt for more information)
  358. ### 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
  359.  
  360. bnet_bnlsserver = localhost
  361. bnet_bnlsport = 9367
  362. bnet_bnlswardencookie = 1
  363.  
  364. ### you will need to edit this section of the config file if you're connecting to a PVPGN server
  365. ### your PVPGN server operator will tell you what to put here
  366.  
  367. bnet_custom_war3version = 24
  368. bnet_custom_exeversion = 243 4 24 1
  369. bnet_custom_exeversionhash = 197 67 68 222
  370. bnet_custom_passwordhashtype = pvpgn
  371.  
  372. ###
  373. ### example configuration for connecting to a second official battle.net server
  374. ###
  375.  
  376. # bnet2_server = uswest.battle.net
  377. # bnet2_serveralias = USWest
  378. # bnet2_cdkeyroc = FFFFFFFFFFFFFFFFFFFFFFFFFF
  379. # bnet2_cdkeytft = FFFFFFFFFFFFFFFFFFFFFFFFFF
  380. # bnet2_username =
  381. # bnet2_password =
  382. # bnet2_firstchannel = The Void
  383. # bnet2_rootadmin =
  384. # bnet2_commandtrigger = !
  385. # bnet2_holdfriends = 1
  386. # bnet2_holdclan = 1
  387. # bnet2_publiccommands = 1
  388. # bnet2_bnlsserver = localhost
  389. # bnet2_bnlsport = 9367
  390. # bnet2_bnlswardencookie = 2
  391.  
  392. ###
  393. ### example configuration for connecting to a third PVPGN battle.net server
  394. ###
  395.  
  396. # bnet3_server = server.eurobattle.net
  397. # bnet3_serveralias = EuroBattle
  398. # bnet3_cdkeyroc = FFFFFFFFFFFFFFFFFFFFFFFFFF
  399. # bnet3_cdkeytft = FFFFFFFFFFFFFFFFFFFFFFFFFF
  400. # bnet3_username =
  401. # bnet3_password =
  402. # bnet3_firstchannel = The Void
  403. # bnet3_rootadmin =
  404. # bnet3_commandtrigger = !
  405. # bnet3_holdfriends = 1
  406. # bnet3_holdclan = 1
  407. # bnet3_publiccommands = 1
  408. # bnet3_custom_war3version = 24
  409. # bnet3_custom_exeversion = 184 0 22 1
  410. # bnet3_custom_exeversionhash = 219 152 153 144
  411. # bnet3_custom_passwordhashtype = pvpgn
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement