Don't define replies explicitly in code

[LeafHacker]

Instead of defining replies in the code, we could load them on launch or something. Perhaps pass in a file as an argument on launch or something?

[LeafHacker]

One option would be to load replies from impactclient.net/bot_replies.json, which could be proxied or redirected to the Resources repo by cloudflare or impactserver. We could then implement a i!reload command to reload the replies without restarting the bot.

Another option would be to use one of github's apis to get push-notifications of changes on the resources repo and pull in replies.json on every commit there, similar to how CI and heroku get push notified.

[LeafHacker]

Constants like user and channel IDs would need storing in the JSON and parting into the reply strings too.

Might be worth using a JSON alternative like yaml to allow raw-string literals for the regexes.