MonikaBot

Fork

Add longHelp and help for when args == 0

Merge with master. Also rework how error messages are reported from
commands.

The new idea is that successful messages are sent directly from
commands. Error messages or help messages are handled by raising a
ResponseError. Major errors that need the attention of the main admin
are handled by raising a AdminResponseError. Then, then
CommandDispatcher handles these appropriately.

Fix regression in !ascii where it wasn't finding fonts, and rebuild docs

Merge fix from trunk

Fig regression with !bigmoji not returning animated emojis properly

Merge with trunk

Add feet to !convert

Don't pass the entire message when processing message rules

Add !rot13

Catch exceptions during reminder loop, and handle users who Monika can't DM.

Improve !imagemod demotivate

Don't need futures here

Bump version, fix deepfrying

Add mutex to WrappedImage

Merge branch

Add resources

Refactor the main !imagemod command, and add drake and expanding mind memes

Allow a WrappedImage to be created from a file

Add Config::ResDirectory module

Move duplicated functionality into WrappedImage, and implement
"!imagemod demotivate"

Add !imagemod command

Use 1024 size avatars for !bigavatar, reduce cache sizes, rebuild
docs, and.... bump version to 1.0.0!

Fix reactions not showing up with !poll

Run the correct program

Bump rebision, rebuild documentation

Reload default message/periodic rules only if it's the main admin
calling the command.

Improve !decide logic, fix bug with Utils.splitDelimited

Disable "rejoin" messages for now, mark them just as "join" messages.

getUserInfo() returns a known user, but not if they're known for a
specific guild. knownUser?() does not check for a guild. So until
this functionality is implemented, we don't really if a user REjoins a
specific guild, or if it's a situation where they're in a guild that
Monika is in, then join another one she's in for the first time.

So for now, the user never "rejoins", they always "join", at least as
far as the embed message is concerned.

This should be properly fixed with the eventual rewrite of user
history.

Call the correct method

Bump revision, update documentation, rebuild api docs