Application Command Cooldowns

[i0bs]

I feel like cooldowns are a very big aspect of developing commands for bots on this platform now.

The ability to add our own cooldowns for how many X given seconds a command can be used per user (with given permission overrides as of the v2 system) would be an extremely beneficial way for server owners to avoid spam of slash commands as-is, as well as bot developers avoiding unnecessarily high HTTP requests.

[Mysterious-Dev]

Good idea. This can be very useful.

[timka-123]

This is very fine! Plus one step for change prefix commands to slash

[iamcxdev]

Best idea

[Like475]

It's amazing idea!

[DerKrisp]

Very good idea!

[Deauthorized]

Bump

[lol219]

@shaydewael Cc

[i0bs]

Reading back on my original request, I think what I'm ideally asking for is a way for developers to define their own custom rate limits through the API. That's essentially what the "cooldown" acts as, and it could also be amazing if we could point a cooldown to an existing rate limit or sub rate limit, e.g. message reactions.

For things like buttons, developers might wish to purposefully make it slower to spam without having to use reactions, which I believe most agree are a more abusive and exhaustive way of hitting API rate limits.

[devsnek]

This is a good idea, but it presents some interesting technical challenges on our end. So, not saying no to this but I can't give any promises or ETAs.

[muhitrhn]

It will be a really very good feature to have as then we will be able to stop people from spamming the buttons.