When reaction roles are set as exclusive, a user can only have 1
reaction role from that message. Others are removed automatically when
picking a role if needed.
The !clean response is intended to be deleted after a delay when
cleaning the current channel i.e. not specifying a different channel
to clean. This behaviour was reversed, so the response got deleted when
cleaning a different channel and stayed when cleaning the current
channel.
Post date will always be more or less the time the log message is posted.
The logMessage variable in the alert action contains the full,
formatted log message that would be posted in a log channel as the
AUTOMOD_ACTION log type.
This loose pre-check checks the config schema by treating every object
as partial. This means that if a property exists, it's guaranteed to be
the correct type (e.g. object). However, there's no guarantee that all
or any properties exist.
This allows preprocessStaticConfig implementations to be much less
defensive and thus reduce boilerplate.
