Rapptz cd0de57d13 [commands] Implement a command cooldown system. ...

The way the command cooldown works is using a windowed way of doing it.
That is, if we have a cooldown of 2 commands every 30 seconds then if we
do a single command, we have 30 seconds to do the second command or else
we will get rate limited. This more or less matches the common
expectations on how cooldowns should be.

These cooldowns can be bucketed up to a single dimension of depth for
a per-user, per-guild, or per-channel basis. Of course, a global bucket
is also provided. These cannot be mixed, e.g. no per-channel per-user
cooldowns.

When a command cooldown is triggered, the error handlers will receive a
an exception of type CommandOnCooldown with proper information regarding
the cooldown such as retry_after and the bucket information itself.

2016-07-22 18:05:38 -04:00

..

__init__.py

[commands] Implement a command cooldown system.

2016-07-22 18:05:38 -04:00

bot.py

[commands] Make Bot.check decorator an actual decorator.

2016-07-08 04:29:11 -04:00

context.py

[commands] Add Context.cog property.

2016-06-16 05:42:28 -04:00

converter.py

[commands] Fix error in converters in a private message context.

2016-07-02 23:39:29 -04:00

cooldowns.py

[commands] Implement a command cooldown system.

2016-07-22 18:05:38 -04:00

core.py

[commands] Implement a command cooldown system.

2016-07-22 18:05:38 -04:00

errors.py

[commands] Implement a command cooldown system.

2016-07-22 18:05:38 -04:00

formatter.py

[commands] Refactor pagination into its own class.

2016-07-05 21:44:14 -04:00

view.py

Initial implementation of commands extension module.

2016-01-04 22:22:52 -05:00