Rate limit

[PsychoJS]

Hey when you start dmall at large servers(+1000 guild members), after reaching to 1000 users, it will be disconnected and token has been reset...

any solution?

[alexlyee]

Thank you for being the first to properly document this on the issues form! I was made aware of this recently. Could you or anyone provide an error code after the bot reaches that user limit? That would help immensely. Have a great day!

[PsychoJS]

@alexlyee i think this thread explain everything... Session Start Rate Limit

[alexlyee]

Thanks for this, I'll look into it soon.

[shinebacksoftware]

How is the resolution to this looking?

[SentinelJs]

it doesnt have answer to fix this problem. cause discord is catch and banned bot

[alexlyee]

@KafJS if you’re trying to say that I don’t have a “solution” to this issue, then yes,, I suppose that is why the issue is open, and it is labeled with “help wanted”. However, as time as passed with this issue, it is becoming increasingly clear to me that this likely is caused by people misusing the delay on the bot, as my latest version of the code on my computer at home is being tested on servers with over 8000 members.

[legendhimself]

@alexlyee If I were you, I would have added a database, probably a local db where the bot can store all the ids of the members who have successfully been dmed and then after like 800-1200 dm. Have the bot do nothing (promise paused) ie stop sending dms and store the date object in db to resume the promise for dming the rest of the users, and for the ids in the db, you can use it to filter out the member array. Make it a long process with multiple breaks so that discord api cannot see the peak in rate limits caused by the bot. Which would prevent bots from getting Quarantined or even banned from Discord.