This page lists the most common problems with Dispatch.IO on Fluxer, their cause and the fix. Start with the first section: most issues come from the prefix, the permissions or where the bot's role sits.
Basic checks
- Is the bot online? The website's status page shows its state.
- The right prefix? Mention the bot (
@Dispatch.IO): its introduction shows the community's prefix. - Can the bot see the channel? Its role needs View channel, Send messages, Embed links and Add reactions.
- Is its role high enough? Drag the Dispatch.IO role above the roles it gives and the members it moderates.
- Is the module on and set up? A module without a channel posts nothing.
Commands
| Problem | Likely cause | Fix |
|---|---|---|
| The bot doesn't answer at all | Wrong prefix, channel invisible to the bot, or bot offline | Mention the bot, check its permissions in the channel and the status page. |
| "You need the … permission" | Your role lacks the command's Fluxer permission | See Permissions and roles. |
| "I'm missing the … permission" | The bot's role lacks the permission | Add it to the bot's role. |
| "Usage: …" | Missing or mistyped argument | Follow the syntax shown or !help <command>. |
| The reply disappears | It is a temporary reply (5 seconds) | Read it quickly, or check your direct messages for personal information. |
| Your command stays in the channel | The bot lacks Manage messages | Give it the permission in the channel. |
| Another bot answers too | It uses the same prefix | Change Dispatch.IO's prefix: !prefix ?. |
Reactions and forms
| Problem | Likely cause | Fix |
|---|---|---|
| A reaction does nothing | The message no longer waits for a reaction (confirmation expired after 30 s, list after 5 min), or you're not allowed | Run the command again; check your permissions. |
| Your reaction is removed right away | Normal for a one-off button, or it isn't your command | Nothing to do: the action happened, or only the author can answer. |
| No form link | Direct messages closed | Open your DMs to the community's members, then try again. |
| "Link expired" on the form | Over 15 minutes, already used, or the bot restarted | Run the command again or click the reaction again. |
| "This form isn't for you" | You're signed in on the website with another Fluxer account | Sign out and sign back in with the account that got the link. |
Modules
| Problem | Likely cause | Fix |
|---|---|---|
| No welcome message | No arrival channel, or missing permissions (Attach files) | See Welcome and goodbye. |
| A role isn't given | Role above the bot's role, dangerous role, or Manage roles missing | Move the bot's role up; check its permissions. |
| No level or flame announcement | Module off or no channel | See Levels and XP and Flames. |
| No log | Log channel not picked, log off or filtered | See Logs. |
| The ticket panel has no reaction | System paused, or category deleted | Turn the system back on or pick a category on the website. |
| The temporary voice channel isn't created | Manage channels or Move members missing, or the plan's limit | See Temporary channels. |
| The music doesn't start | Not in voice, Connect or Speak missing in the voice channel, unsupported link (Spotify, Deezer, Apple Music), or a radio is already playing | See Music and radio. |
| A website change has no effect | The bot was offline when you saved | Save again once the bot is online. |
Still stuck?
Report the problem with !report bug <description> (attach a screenshot), or join Dispatch.IO's support community on Fluxer: its link is in the bot's introduction and in !help.