clientOptions
the timeout option should increase as your bot get into more server to include time for cache. All client events will start being triggered once the ready event is fired
fetchAllUsers are not recommended for bots in more than 2500 servers as it could cause a 429 rate limited error.
To calculate the intent value, you could use this tool online to calculate it.
Title | Required? | Description | Type |
intent | false | The intent number that the bot need | default: 32509(use 32767 for full intent access) | number |
timeout | false | The time in milisecond that the bot will timeout if connection is not successful. This will also be the time that will cut all caches and run the ready event Requirements: < 600000 ms and > 2000 ms Default: 5000 ms | number |
fetchAllUsers | false | Cache all users using your bot. You need to have SERVER MEMBERS INTENT enabled on your developer portal and have GUILD_MEMBERS intent included in the intent number or only 1 member per server will be cached. By setting this to true intent number will automatically be switched to 32767 unless you set Default: false | boolean |
intentsForce | false | Lock the intent string you or the library have provided, and no other place will be allowed to change this intent |
Last updated