Config

ZeroBot uses a JSON Style Configuration. We chose Config::JSON because, despite its heavy dependencies, fits all of our needs. It supports arrays and hashes, which no other Config::* could do (properly). The following is a working configuration (zerobot.conf), and will start the bot properly. You should know that 1 means "yes", and 0 means "no".

{
   "IRC" : {
      "home" : "#Janus-Dev",
      "port" : "6697",
      "server" : "irc.JanusIRC.com",
      "ssl" : 1
   },
   "admins" : [
      "*!k@k"
   ],
   "client" : {
      "gecos" : "Demon Days",
      "ident" : "dz",
      "nick" : "Deltron_Zero",
      "nickserv" : "NickServPass",
      "trigger" : "*"
   },
   "owners" : [
      "miniCruzer!eyeless@*",
      "*!*@*.dhcp.insightbb.com"
   ],
   "set" : {
      "autoop_admin" : 1,
      "autoop_owner" : 1,
      "database" : "zero.db",
      "rejoin_on_kick" : 1
   }
}

• IRC - This section defines the settings to use for the IRC Server, including Port, Server Address, SSL, and its main channel. The main channel is used for the bots error logging. If it gets banned/kicked from another channel, it will notify you in here. If the port you define is using SSL, indicate 1 for yes, 0 for no.

• Admins - These are the hostmasks in which the bot will give Admin Level command access to. You can put as many hosts as you want here, separated by commas. ["nick!user@host.1", "nick!user@host.2", "nick!user@host.3" ], - and so on.

• Owners - These are the hostsmasks in which the bot will give both Admin Level and Owner Level access to. You can put as many hosts as you want here as well.

• Set - This is ZeroBot's pseudo modularization settings. autoop_ tells the bot whether to op owners/admins if the bot has ops too. Settings database and rejoin_on_kick are not yet used.