This is a major refactor; the bot has now been updated to easily support multi-server monitoring.

More work is required around configuring and enabling / disabling actions on a per-server basis, but this will form part of the Twitch integration work I will be doing next.

This is pretty much ready to go into master if you're happy. Let me know if you need me to explain any of the architectural decisions I've made here.

There's no reason this couldn't go into 1.0.0, though I've tagged this as part of 1.1.0.

This addresses the following issues:

25 - There is now a new "GenericActionHandler" that is resolved only when no bang-command is found. At present it doesn't do much, but this can be used to monitor incoming none-command messages for any server.

11 - Pretty much complete, though I've not bothered with a message bus.

2 - Many more unit tests. Bot.js is now much, much simpler, but there are no tests for it - I've got some minor tweaks to make to how it loads the servers on startup, at which point I'll write tests for it.

lewster32 / corporallancot

Feature/11 - Multi server support #31

25 - There is now a new "GenericActionHandler" that is resolved only when no bang-command is found. At present it doesn't do much, but this can be used to monitor incoming none-command messages for any server.

11 - Pretty much complete, though I've not bothered with a message bus.

2 - Many more unit tests. Bot.js is now much, much simpler, but there are no tests for it - I've got some minor tweaks to make to how it loads the servers on startup, at which point I'll write tests for it.