DevYukine
Cluster 0 failed to start
Current code:
const Sharder = new ShardingManager(join(__dirname, 'Client.js'), { token: settings.token, client: BaseClient, clientOptions: { disableEveryone: true, commandEditing: true, commandLogging: true, regexPrefix: /^((?:Hey |Ok )?Dum(?:,|!| ))/i, console: { useColor: true, timestamps: 'MM-DD-YYYY hh:mm:ss A', utc: false }, prefixCaseInsensitive: true, noPrefixDM: true, prefix: 'dd.', pieceDefaults: { commands: { deletable: true, cooldown: 3, quotedStringSupport: true, bucket: 2 } }, readyMessage: (client) => [ ✔ ] Shard ${client.shard.id + 1} out of ${client.shard.shardCount} is ready. ${client.guilds.size.toLocaleString()} guilds & ${client.users.size.toLocaleString()} users loaded., disabledEvents: [ 'CHANNEL_PINS_UPDATE', 'USER_NOTE_UPDATE', 'RELATIONSHIP_ADD', 'RELATIONSHIP_REMOVE', 'USER_SETTINGS_UPDATE', 'VOICE_SERVER_UPDATE', 'TYPING_START', 'PRESENCE_UPDATE' ], aliasFunctions: { returnRun: true, enabled: true, prefix: 'funcs' }, dashboardHooks: { apiPrefix: '/', port: 7575 }, typing: true, production: true, providers: { default: 'mongodb'} }, development: false });
Hey 👋
This might be related to multiple things
- discord.js not emitting ready (either caused by a bug or by the discord api not sending the READY payload)
- your "Client.js" is not in the correct format (see Readme for this)
Kurasuta does retry already by itself since some version, so if that happens for the retries aswell it is very likely your "Client.js" having a wrong layout.
Having same issue. would be helpful to have more debug information outputted so we can troubleshoot bot logs in but never emits 'ready' or 'shardReady'
Better example in Readme would be helpful too
