Feature Request: Support the ability to suppress or remove a user's (long) slowmode cooldown via the API.

[QuantumToasted]

Our large server has several channels with excessively long slowmode (1 or 6 hours), each with their own posting guidelines. Some of these guidelines involve content vetting that goes beyond what Discord's native AutoMod provides. To name a few:

• Validating a mix of message length, line breaks, attachment count, and link wrapping to see if a message takes up too much space (ad/promotion channel)
• Validating a combination of tags in a forum channel to make sure that a user has selected a region and gamemode ("looking to play"/"looking for group" channel)
• Validating that a forum post meets minimum length requirements for the title and description separately (general purpose help forum)

These three examples require reactionary intervention by a bot, which deletes the post/message and notifies the user about the problem with their message. This effectively means that the message was never "posted" as far as our server is concerned, but the user is still subjected to the slowmode of that channel. We have no way to circumvent or lift this cooldown on our end — if memory serves, even granting them a role with MANAGE_MESSAGES (which bypasses slowmode) does not lift existing slowmode cooldowns.

It would be a great help to servers utilizing channels with longer slowmodes, in the absence of the proper AutoMod functionality to block the messages in the first place, to be able to manually remove an existing slowmode cooldown for a particular channel. If AutoMod could be tweaked to accomplish the things we need instead, that would be fine as well, but the goal is that users should (be able to) not be punished with long message cooldowns for messages that were deleted reactively by a bot in channels with very long slowmode settings.

[Amgelo563]

As a workaround you could make the bot a middleman, so the user sends the message and combination of tags/title/etc through a modal and select menus, it validates, and only lets them send it if it passes. Can use a webhook if you want to preserve pfp and username. Another alternative could be to offer a way to pre-validate if your bot will let them pass or not, before the user tries to create the post.

[SirCastik]

I have a similar issue on one of the servers I develop on, and as a workaround - the server admins made a "Slowmode Permit" role which overrides slow mode via permissions, and every time the bot has to reject a message from a user, it gives the user this role (so they could continue sending messages) until the user sends a message that is accepted by the bot and kept on the channel. Then, the bot removes the role from the user, and the user can't send more messages.