The class is filled with methods and interface methods. These need to be split up in a neat and organized manner.

The bot should be deployable with Docker.

As the bot is currently written, it does not cache most, if any, of the information it receives from the Gateway WebSocket connection. An in-memory database (or possibly a stand-alone database) should be implemented to remedy this problem. This would allow for easy retrieval of information such as current information about user's in a guild without requiring as many HTTP requests.

Bot needs to be able to, at a minimum, take a message from a channel, determine if it's a valid command, process the command, and output back to Discord if needed.

One of the test cases in EventManagerTest is currently failing due to an unknown reason (9a8b5a7). It was previously passing but has decidedly begun to fail after implementing the use of futures to block before verifying method interactions.

A database (possibly in-memory or separate) needs to be implemented for the storage of per-session information about Discord. Such information may include guild and user data.

The ability to issue commands to the bot via a mention is a desired feature.

Example:
@bot ping

Automated testing on each commit should be implement. Along with this, all new features should include tests with a reasonable coverage (ideally 100%)