ChrisJL

> I don't understand the warnings fix here. `setup` is a coroutine function rather than a coroutine itself, so there should be no warnings from it just being imported, only...

I think having control over the config directly is quite useful. So maybe instead we could have an additional optional param for difficulty. This param would set the "default" config...

> Maybe...we can have both? That's sort of what I was suggesting, with an additional optional param for difficulty. However, rather than only allowing one or the other, I proposed...

The previous behaviour has now been migrated over to `voice_mute`. `voice_ban` currently has stub commands, so who ever picks up this ticket show implement those as described above.

We have an option on how to deal with concurrent requests, either we can queue them, or we can deny them and require the user to request them again. Is...

Ah, I did not realise I was still assigned to this one, it's up for grabs for anyone to work on

> According to a vote we held with the mods, the alert should always ping if the unfurl fails, but otherwise ping only if the destination is blacklisted. Cool, that...

> I've been requested for review, but I do not think all my previous comments have been addressed. You're right, this isn't quite ready for review just yet. It's on...

Seems like a good idea. I'd like to hear a proposed implementation from whoever wants to take this on before approving it though. Mostly since this isn't a trivial change,...

> What about the tag "rule " Those aren't tags, they're a command in and of themselves. Also, the rules are already listed in our website (it's what the rules...