I've tried refactoring some of the original code that I wrote initially in haste, but a lot of it's still very questionable and in need of rewriting/refactoring.
> Rename `config.example.js` to `config.js`, open it and fill in the relevant values. The comments should explain what they are for. If something is unclear open an issue and I'll attempt to make it more clear.
> At this point you'll probably notice you need to add 3 new categories. I'm planning on automating a part of the setup process, but for now this is how it be. Make those, add their IDs to the array.
> I'd recommend getting PM2 or whatever you prefer for process management.
> Start up the bot and if you did everything right it should boot up and just work. If something goes wrong submit an issue, alternatively if you know how to fix it, issue a pull request.
Both of these can be used with `!r` and `!cr` respectively and both of them support the `anon` keyword to send an anonymous reply. The anon keyword has to be the first argument.
`!modmail <user> <content>` or `!mm <user> <content>` - Sends a modmail to a user, also supports the anon keyword. `!mm anon @navy.gif#1998 Some content that is sent anonymously`
`!markread [user|channel]` - Marks the thread read and moves the channel to the read category indicating that the mail doesn't warrant a response. Messages you've replied to are automatically marked read.
`!id [channel]` - Get the target user ID for the modmail thread. Can be used without the channel argument in a modmail channel, outside of a modmail channel will return the user ID for the channel's target if available.
- ~~Display more specific information instead of just "User is in banland" (should reflect whether user is actually banned or otherwise in the appeals server.~~
