Commands like `;headcount` with the time arguments and `;afk` Raid Status Embeds cause rate-limiting to sending Messages

[Ragviswa]

Current Behaviour

Problems, Frustrations, General Description

Certain commands in channels can cause rate-limiting issues which affect all other commands within that channel. ;hc when adding the time arguments or ;afks with their raid status embeds can hit this limit and block the bot from sending additional messages with other commands. This can block the channel from being used until a ;restart occurs to reset the commands.

How to Reproduce

Run ;hc with the time arguments and wait for about an hour for rate-limiting to occur. Then all commands which send messages will not execute or will execute after a long delay. The method to do with ;afks is unknown exactly how to reproduce.

Wanted/Expected Behaviour

Improvements, Additions, Changes

Rewrite or refactor the relevant commands to ensure rate-limiting does not occur and the bot does not need a ;restart. Could add logging for rate-limiting in general to ensure future issues are caught more easily.

Reasoning

It is annoying for all staff for a ;restart to be required in seemingly random instances due to rate-limiting. This is the only issue limiting bot uptime from being longer.

Tasks

Things to Do

• Debugging the exact causes for rate-limiting
• Fixing the identified bugs within the relevant commands

Paths to Files

• /commands/headcount.js
• /commands/afkCheck.js