Notes

• Consider PRIORITY
• Priority probably only comes into play when you want to "overwrite" an existing hook, and then only really makes sense in the "send" event. But really, the only case where you would want to overwrite a send event, is if you wanted to overwrite the default send event, and implement your own. I need to think some more about this.
• Hooking send events
• The more module convenience the better, things like event.isadmin and the like might be really handy, or that can be left for module writer I suppose. I think it's nice though We will do this through utilities.
• Periodic DB committing
• Some sort of centralized BBM provided way of managing timers for modules
• In Servers settings, change structure to dict where servername is the key and corresponding serveropts are the value to ensure unique (and existent) server names at configuration level
• Finalize how we're doing logging
• botinst wrapper for context aware things like bot.say (auto messages to event.channel)? Maybe this falls under too much preprocessing too
• Cache aliases (ultra low priority)