Basic stuff: how much people lag before lagbox, how strict bans are, require spoofchecks (make sure that person is that name), %of people for votekick, default map, the motd (bot tells people this when they join-i'd leave this default and make/change the file with this name myself), the log method (I've got logmethod 1, but it's up to you). Also you've got your command trigger (in game), the latency, how many games it'll run at once, if the bot allows downloads, how many people can download the map at once, bot's name while in a lobby, etc etc etc. Lots of stuff which mostly matters but can be skimmed (some is required)

Ohh boy, big one. You've gotta get this right for the bot to get on BNet. You can connect to 10 servers (though I think 4 is the max anyone would use for one bot), and you'll probably have almost the exact same info for all of the servers you want to be on. First is the server itself, which one the bot looks to for a server. (All I know is the big 4 BNet ones: useast.battle.net, uswest.battle.net, asia.battle.net, and europe.battle.net). Next up is what you want it to be nicknamed-basically the short version of the server name (I've got USWest for uswest.battle.net amd USEast for useast.battle.net, it just made sense...). The next two are absolutely (ABSOLUTELY) crucial that you get right if you want to be on BNet. A RoC CDKey, and if you want to play games on TFT, then a TFT CDKey. (If you only have 1 set, see Admin Games). Locale is one I don't totally get, but since I'm on Win7, I can just set this to "system" and it's nice and easy and I can leave it alone. After that, you have to put in the username and password for your bot's account. It CANNOT make these accounts, but once made it'll be fine. The next box is the first channel your bot will join upon logging on to BNet-I suggest a place you know will be empty or your clan's channel (believe me, The Void DOES NOT count for an 'empty' channel). This next command trigger is the trigger used by the bot in channels (and I think whispers) for that BNet server, you should probably just put this as the same one as the other trigger to make it easy. Next is a "BattleNet Login Server" (I think). Anyway, it's for Warden stuff (Blizzards anti-hack bs, it'll disconnet the bot every 2 minutes without this). I use some guy's and I've not seen anything bad happen from it: "instinct121.no-ip.org". For the "wardencookie" mine's set to "1", and I've no idea what it is, and the thing has no description of it. Whatever, next is our "custom_war3version". This will probably change once in a while when WC3 has a patch. As of this writing it's 26, and if you look at WC3s version number (at the "main menu") it's in the corner-after the first dot and before the second-that's what you want (I think that's the number to put here anyway...). The next 3 boxes I've got blank and the PvPGN one is the default one (it's for private WC3 servers I think). Most of the stuff after wc3version is ignored by me, but you might want to look at "holdfriends", "holdclan", and "publiccommands". Basically, if the bot has any friends (eheh) or is in a clan, it'll hold a spot for any of them. Public commands means that there are some commands that can be used by anyone, and this lets them.

For those with only 1 set of CDKeys, this is where you need to look. Admin Game is basically a game created in the LAN for WC3 (specifically: you) to join and control the bot, as if you were on BNet. You HAVE to set a password (I fail to see the point in this....) and when you join you say "(trigger)password (password)". So if your trigger is "." (like me) and your password is, say, "DarkChaosisAwesome" (sorry DC, not my PW lol) then when you join the admin game before you can do anything, you must say ".password DarkChaosisAwesome". This is case-sensitive, and depending on your version of GHost, it might kick you for 5 minutes. (I love custom build for this, because you get multiple tries.) The map part you should leave blank, it's the map you're in to control the bot from, and means absolutely nothing unless that version of WC3 can't use that map [example: you cant use maps that died in the great map killing patch and haven't been updated], so just leave it blank and it'll be fine. The port doesn't matter to me, but you should probably no let it overlap with other ports (WC3's hostport, the other 2 ports on bot). The next section of stuff in this tab is UDP & TCP, and can make a load of difference. First is "broadcasttarget", which basically means when the bot has a game in the lobby, it'll post it in this LAN place. If you're controlling the bot in the same place you're playing WC3 on, then you can set this to 127.0.0.1, and it'll always work (if you're on another computer, it can get tricky). "nodelay" I think basically takes up a little more of your net connection to make it so other players don't feel that little bit of lag of not being host. (Try joining a player's game. When you do something in the game, usually there's a moment before it actually happens. This setting nullifies that, I think). I don't know what "don'troute" is, but I don't use it...feel free if you want to. After that stuff is if you want the bot to autohost games automatically: set how many people needed to join, the game name, the owner of the game (technically doesn't apply unless you join every single one, but you're probably rootadmin, so it still shouldn't apply), and how many it'll allow at once. (I think this uses the default map for autohosting, but I don't know-I've never used this). After that is replayversion (for if someone disconnects and the bot is set to auto-save so the other people can join again), build number (the last numbers in the wc3 version in the corner on "main menu"), and the WC3 version to use for LAN (set to the same as the other WC3 version on BNet-I don't know what happens otherwise and it should be the latest version unless you want a specific version of WC3)

PS: If you're doing admin game, you need to double-check your spoofcheck stuff back on the Bot tab. Since you're in LAN, it can't /whois you, so you won't show up as online.