Errors & fixes
Use CTRL+F if on desktop, or Find in Page feature if on mobile to look for your issue.
You may NOT use Visual Studio Code to run npm commands. Run npm commands in the Command Prompt or any other Terminal.
Node/NPM-related
Could not locate binding files
Make sure to try starting your bot between every command, just in case the last command you ran solved the issue.
Open the command prompt (cmd) or terminal if on Linux/BSD or anything else and run:
Related: Glitch. Search the web.
Node can't find Python
Related: node-gyp. StackOverflow. Search the web.
BetterSQLite3 or quick.db can't be installed
Try only one of the following and take the time to read the errors, if any. If it doesn't work, try the next one.
Remove the
better-sqlite3
andquick.db
folders from within thenode_modules
folder then runnpm install
.Run
npm i better-sqlite3
.Run
npm rebuild
.Remove the entire
node_modules
folder then runnpm install
.
Related: Troubleshooting BS3, quick.db #200, better-sqlite3 #397, StackOverflow, NodeGYP, #12, #14, #18.
Bot-related problems
A new ticket is created on every single DM
Glitch users are not affected by this issue.
For users who host their bot on GitHub and Heroku, this error isn't recoverable because the json.sqlite
file is in the cache. The cache gets cleared on every bot restart.
Replit users seem to be affected by this issue as well.
Bot doesn't delete or create channels
Give your bot the permission to manage channels.
Related: #4.
Other
Can't read property of null
Related: #9, #13, #15, #18, Search the web.
User-related
Privileged intents provided not enabled
Related: discord.js #5123, #40.
Invalid token
Make sure of the following:
The token you use is the Bot token, not the Application token.
The token is in the config.json file.
Try to do the following:
Regenerate the Bot token.
Find the bot.js file and replace
client.login(config.token)
withclient.login("token")
.
MessageEmbed isn't a constructor
Update your discord.js version.
Related: #7.
Still can't find your issue?
Last updated