You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an easy way to handle cooldowns for custom command handler implementations, or any other usecase requiring them.
Why is this needed?
It could be handy to enforce ratelimits, or just to create custom logic within Discord bots.
Ideal implementation
Cooldown buckets that can operate on a variety of types, (perharps passing a lambda to tell it how to extract the hash so it works on any type?) and logic that can either wait for the cooldown to expire then continue or raise errors (or other similar behaviour)
Checklist
I have searched the issue tracker and have made sure it's not a duplicate. If it is a follow up of another issue, I have specified it.
The text was updated successfully, but these errors were encountered:
Summary
Add an easy way to handle cooldowns for custom command handler implementations, or any other usecase requiring them.
Why is this needed?
It could be handy to enforce ratelimits, or just to create custom logic within Discord bots.
Ideal implementation
Cooldown buckets that can operate on a variety of types, (perharps passing a lambda to tell it how to extract the hash so it works on any type?) and logic that can either wait for the cooldown to expire then continue or raise errors (or other similar behaviour)
Checklist
The text was updated successfully, but these errors were encountered: