Adding and Removing reactions hits guild ratelimits

[DarylJG94]

The way the module currently works with adding the reactions directly after reachother and the instant removal of reactions causes the bot to hit discords ratelimits incredibly quick, as a little hack workaround I have made the following changes:

setTimeout(async()=>{ await curPage.react(emojiList[0]); },1000);

setTimeout(async()=>{ await curPage.react(emojiList[1]); },3000);

instead of the forloop, and the removal of reactions:

setTimeout(async ()=> { reaction.users.remove(msg.author); },2000)

[xMyThoLoGyx]

Where would you make those changes? Sorry :/ is it in the node module or in your code?

[DarylJG94]

My apologies for the short delay, it is indeed hitting rate limits when posting the initial reactions. I will provide a pull request shortly

[DarylJG94]

See Pullrequest #24

[psibean]

My apologies for the short delay, it is indeed hitting rate limits when posting the initial reactions. I will provide a pull request shortly

How many reactions did you have? Was this across multiple servers at a time? The global rate limit is 50 requests per second and there's no mention of an individual limit on the create reaction endpoint - so I'm struggling to see how you're getting 50 reacts just on the INITIAL reactions.

Are you able to provide a minimal repository and the use case that replicates this?

Edit: if this is actually an issue, I'm not sure a hard coded timeout is the way to fix it. The exceptions (if any) should be exposed to the user for handling. Any timeouts should be configurable, and I'd like to have such changes incorporated into my PR which significantly restructures this module.