The modlog API should not auto-detect events caused by the bot.
This would allow the simplification of interacting with the modlog API.
This would make interacting with the modlog API easier, but required for certain actions.
This would not remove auto-detecting bans made by moderators through the discord interface rather than the bot
A practical case and rationale
While working on #2866, I noticed there is no clean way to create a case type for multiple audit log entries. In wanting to allow role mutes to be supplemented with permission overwrites as needed, I would need a case type which supported multiple audit log actions.
Rather than change the modlog API to support this, removing the action type all together and just not detecting actions the bot took allows cleaner ease of use.
This does mean that someone can't do a ban with a reason and have an audit log entry automatically generated, they would need to create a case.
Mitigating the impact of downsides
If we provide a few pre-registered case types which cover generic use already registered and support their use, the downside becomes one extra import and one extra line per mod action.
This would remove a key from the dicts used in case registration.
This would be a change in expected behavior if cogs are not updated for this.
The text was updated successfully, but these errors were encountered:
Just for clarity, the parsing in mod with get_audit_log_info + the event listener there for automatic case generation without a (discord) audit log entry is why this key is currently being used in core red. any modification around this should address that.