MrBot

Currently online in the major RS channels as MrBot.

See http://www.rebelsquadrons.org/irc/bot.help for instructions on using the bot.

todo

• RS Trivia. Use the new scrambler codebase.
• Scrambler: !pause
• Find out what's causing the occasional fwrite() errors (note: for now almost all of the fwrites have a @ prefixed as a temporary solution, since the "log off" mode isn't specifically checked for yet)
• Make RS webpage (in /irc/ or /chat/) with details about channels, accesses, etc. Make it possible to edit stuff via website.
• seen: recursive nick checks? licah|afk has not /nick'd LicahEvlDead, so there are now two results for "licah" while licah is licah|afk (because of different hostmasks)
• logs: consider making monthly archives of logs for filesize purposes
• dictionary def: !def can use http://www.mso.anu.edu.au/~ralph/OPTED/ -- !etym can use http://www.etymonline.com/index.php?term=zephyr
• !def - take out links; for only 2 definitions, should likely provide both of those definitions.
• login: provide "invalid PIN" message if that is the case.
• !date requested. will be tricky due to timezones.
• add support to reconnect to MySQL if the service is rebooted and/or the connection doesn't exist. Makes bot more robust, and we can restart mysql service as needed.
• This isn't exactly about an improvement to the bot per se, but using Ajax I ought to be able to adapt the bot's code to make an IRC client to run off the RS site. It'll be very similar to cgi:irc, however.. so if I can get that working instead, then we can just use that.
• I kinda want to revamp ICTE a lot and start awarding idle points, like the plan was for ORW3. That would involve some bot stuff, too. We can set that up with auto-on and auto-off for MrBot... it could be a completely automated ICTE system.. some sweet stuff could happen. It'd take a fair amount of time, but not as much as you might think. let's think about it.. also, maybe icte.rs.org? since it's going to be a major site of its own. Or, maybe just rs.org/icte will still work. That's a whole project to consider.. woot
• scrambler: !re needs the same delay time as !hint.
• (re)connecting: lots of php errors generated -- need to suppress some (especially related to sockets, since we use error-handling for that)
• !op: "insufficient access" message goes to wrong person, apparently.
• error messages: state when bot doesn't manage a channel.
• further standardize error messages? -- make everything work like !op
• ICTE: select type for EaW (!signup eaw 1v1 space)
• ICTE: !servers, apparently. (probably for JO)
• ICTE: people want !jo 1v1, etc.... we can likely do that as part of "default" - "if ICTE" - get list of games.

DB ICTE bot !rules:

Use !signup <game> <players> to play (ex: !signup JA 1v1). Use !<game> <players> to see who's already signed up.
When signing up for EaW, you *must* specify LAND or SPACE. ie, !signup EAW 2v2 SPACE

DB ICTE bot !servers:

JA Antei Training Center 69.12.92.90:27960 Pass: DBROX
JA Kr'Tal Gaming Server 69.12.53.67:27676 Pass: DBROX
JO Clan Taldryan JO Server 69.12.53.83:27960 Pass: Talpwnz
JO GE JO Server 209.160.77.26:27960 Pass: Reborn
Teamspeak 208.100.26.180:8771

Scrambler logs

• do some RS lists (can pull automatically from db and format -- like ABG chars, medals, etc)
• add logs from other scrambler (morelogs.rar)
• List of unusual words -- huge. http://phrontistery.info/a.html