-
-
Notifications
You must be signed in to change notification settings - Fork 638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Atlest fix it #234
Comments
Been working fine for me. Double check your token and .env file along with the configs |
Same problem here, everything else is correct on my end just dies and tries relaunching endlessly. |
same |
same with me lol |
Delete the package-lock.json and the .npm & node_modules folder. Then do |
what he said it worked |
I meant to comment a while back, I fixed this as well. Turns out when you first make a login for the MongoDB thing for some reason the password you set doesn't actually work. If you go in and reset the password to something else it works fine, no clue why that is but it worked for me. |
・Unhandled promise rejection
Error
1 Error [ShardingReadyDied]: Shard 0's process exited before its Client became ready.
Copy
Stack error
1 Error [ShardingReadyDied]: Shard 0's process exited before its Client became ready.
2 at Shard.onDeath (/home/runner/ALL-IN-ONE-Bot-v4/node_modules/discord.js/src/sharding/Shard.js:162:16)
3 at Object.onceWrapper (node:events:642:26)
4 at Shard.emit (node:events:539:35)
5 at Shard._handleExit (/home/runner/ALL-IN-ONE-Bot-v4/node_modules/discord.js/src/sharding/Shard.js:412:10)
6 at ChildProcess.emit (node:events:527:28)
7 at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
The text was updated successfully, but these errors were encountered: