Discord Bot Not Responding? Setup & Command Troubleshooting
Troubleshoot Discord bot login, slash-command registration, missing permissions, channel access and runtime errors for ZCraft Studios Discord tools.
Discord Bot Not Responding? Setup & Command Troubleshooting
A Discord bot can appear online but still fail to show slash commands, read messages or perform actions. Check the bot's runtime, application settings, invite scopes and channel permissions separately so you can identify the missing piece.
Identify the symptom
| Symptom | Check first |
|---|---|
| Bot is offline | Hosting process, runtime errors, environment variables and token |
| Bot is online but slash commands are missing | Application command registration and invite scopes |
| Commands appear but fail | Bot permissions, command checks and runtime logs |
| Bot cannot see a channel | Channel visibility and permission overrides |
| Bot cannot create a Forum post or thread | Create-thread and send-message permissions in that channel |
| Bot stops after a restart | Hosting configuration, persistent files and startup command |
1. Check that the bot process is running
Open the hosting console or process logs. Confirm the application starts without dependency errors and remains running. If it exits, read the first error rather than repeatedly restarting it.
Check the product's required runtime version, install dependencies from the included project instructions and verify that the configured start command points to the correct entry file.
2. Verify the bot token safely
Confirm the environment file or hosting secret contains the current bot token and that the application reads the correct variable name. Do not paste the token into Discord, support tickets, screenshots or online debugging tools.
If the token was exposed, reset it in the Discord Developer Portal and update the hosting secret before restarting the bot.
3. Check invite scopes and slash-command registration
When inviting an application that uses slash commands, make sure the invite includes both the bot and applications.commands scopes where required.
Then verify that the application completed command registration successfully. Check the runtime logs for registration errors, confirm you are testing in the intended server and follow the product's instructions for guild-specific or global commands. Do not assume a command failed to register solely because it does not appear immediately.
4. Check intents and Developer Portal settings
Some bot features require privileged Gateway Intents or other application settings to be enabled in the Discord Developer Portal. Enable only the intents the product actually requires, then restart the bot if its instructions call for it.
A missing intent can prevent the bot from receiving the events needed for a feature, even when the bot is online.
5. Check server and channel permissions
The bot needs permission in the server and in the specific channel where it is expected to act. Review role permissions and channel overrides.
For a Forum-based workflow, check that the bot can view the channel, create posts or threads, send messages in threads, and manage tags or threads if the feature requires those actions.
6. Check the bot's own logs
Look for permission errors, missing environment variables, failed API requests, command registration errors and database connection failures. Record the timestamp and the action that triggered the error.
Do not share full environment files, tokens, OAuth secrets, database URLs or private user information when requesting support.
Evidence Bot-specific checks
If you are troubleshooting Evidence Bot, follow the Evidence Bot setup guide and operations guide. Confirm the configured Forum channel and required permissions before testing case creation and follow-up workflows.
Evidence Bot manages Discord case and evidence workflows. It does not execute Minecraft bans, mutes or other server punishments.
Still not working?
Contact ZCraft Studios support with the product and release version, hosting/runtime version, the action that failed and the relevant error lines. Never include bot tokens, passwords or database credentials.