[Enhancement]: Rate limit in Eigen commands like absolute and fridge

[youngcoder45]

Current behavior

The commands like ?absolute and ?fridge can be spammed to cause raids

Desired improvement

To prevent raids a cooldown or rate limit must be applied on these commands.

Impact

the server Mods will be impacted and Possible raids will be stopped.

Additional context

None

Checklist

• I searched existing issues before opening this.

[Saksham-official]

I’d like to work on this enhancement and add a rate limit specifically for these commands (and similar “fun” commands if you want). My approach would be:

• Locate the handlers for ?absolute and ?fridge in the command files and check if there is any existing cooldown or rate-limit utility in the codebase.
• Implement a per-user (and optionally per-channel) cooldown, for example a short delay like 5–10 seconds between uses, with the value configurable from a central config so it can be tuned later.
• When the command is triggered, check the last invocation timestamp; if it is within the cooldown window, reply with a short message indicating the user is on cooldown instead of executing the command.
• Add or update any relevant documentation/config comments so future contributors know how to extend this to other commands.

Before I open a PR, could you please confirm:

• What cooldown duration you prefer (and whether it should be per user, per channel, or both)?
• Should this apply only to ?absolute and ?fridge, or all similar image/meme style commands that might be abused during raids?
• Once you confirm these details, I’ll go ahead and implement it and open a PR referencing this issue.

Please assign this issue to me if it is available.
/assign @Saksham-official

[youngcoder45]

I’d like to work on this enhancement and add a rate limit specifically for these commands (and similar “fun” commands if you want). My approach would be:

• Locate the handlers for ?absolute and ?fridge in the command files and check if there is any existing cooldown or rate-limit utility in the codebase.
• Implement a per-user (and optionally per-channel) cooldown, for example a short delay like 5–10 seconds between uses, with the value configurable from a central config so it can be tuned later.
• When the command is triggered, check the last invocation timestamp; if it is within the cooldown window, reply with a short message indicating the user is on cooldown instead of executing the command.
• Add or update any relevant documentation/config comments so future contributors know how to extend this to other commands.

Before I open a PR, could you please confirm:

• What cooldown duration you prefer (and whether it should be per user, per channel, or both)?
• Should this apply only to ?absolute and ?fridge, or all similar image/meme style commands that might be abused during raids?
• Once you confirm these details, I’ll go ahead and implement it and open a PR referencing this issue.

Please assign this issue to me if it is available.
/assign @Saksham-official

No need to be assigned u can work on it without it. Just mark ur PR that it closes this issue.

[youngcoder45]

I appreciate u are eager to contribute