-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add cooldowns to commands #27
Comments
Just another idea of how this can be structured in a command cooldown { bucketType ->
when {
bucketType.CHANNEL -> {
15 Seconds
}
bucketType.USER -> {
30 Seconds
}
bucketType.MEMBER -> {
if (event.author.id == 332947254602235914) {
30 Seconds
} else {
1 Minute
}
}
}
} |
While I do think that cooldowns are a very valuable thing in a framework like this, I'm not currently in a position where I know how to implement them - I'm going to need help with this one |
The pull request that would have solved this (#191) hasn't been touched in five months, so I've been left with little choice other than to close it. Perhaps in the future, someone else could have a look at getting this implemented. |
Summary
Add a way of specifying cooldowns for commands.
Preferred Behaviour
The interface for the cooldowns could look something like this:
The text was updated successfully, but these errors were encountered: