Troubleshooting
Troubleshooting
Use this checklist when a module saves correctly but the bot does not behave as expected in Discord.
Overview
Ludicrous Bot stores this module as structured server configuration. The Discord bot worker should read the saved guild settings, watch the relevant Discord events, and apply the behavior described by each field.
Before You Start
Test changes in a staff channel first, especially when roles, punishments, or message deletion are involved.
Required Discord Permissions
- Manage Server for dashboard access
- Administrator temporarily for diagnosis, then reduce permissions
Setup Steps
- Check whether Ludicrous Bot is still in the server.
- Confirm selected channel and role IDs still exist.
- Move Ludicrous Bot's role above managed roles.
- Review API route responses and bot worker logs.
- Re-save the affected module after fixing Discord permissions.
Dashboard Instructions
- Open the server dashboard.
- Select this module in the sidebar.
- Review warnings and empty states.
- Save once the preview matches your desired behavior.
Example Use Cases
- A reaction role menu saves but cannot assign a role because the bot role is below the target role.
- Welcome messages stop after the selected channel is deleted.
Troubleshooting
- If a selector is empty, verify `DISCORD_BOT_TOKEN` is set and the bot is in the guild.
- If a server is missing, confirm your user account has Manage Server or Administrator.
- If saves are rejected, wait for the route rate limit window to reset.
FAQ
Should I give the bot Administrator forever?
No. It is useful for diagnosis, but production servers should grant only the permissions required by enabled modules.