Bot troubleshooting

Work down this list.

1. Run @FluxerList ping. Mentions work with any prefix, so this rules out a changed prefix.
2. Check the channel. If an admin ran !settings channel #something, commands only work there. Admins can lift it with !settings channel none.
3. Check the bot’s permissions in that channel. It needs Send Messages, Embed Links, and Read Message History.
4. If !ping works but a game or claim doesn’t, an admin may have turned it off. See Set up the bot.
5. If the bot doesn’t answer anywhere, it may be down. Check the status page.

Check the status page first. If the bot or the site is listed as having an incident, staff are already on it and it will start answering again once it’s resolved. If everything shows as operational, work through the steps above, then ask in the support server with the exact message you saw.

The bot can’t reply in that channel. Grant it Send Messages, Embed Links, and Read Message History there. The message tells you which channel it means.

This server isn’t listed on FluxerList yet, so bump, vote, and stats have nothing to act on. List it with !list or on fluxerlist.com.

Anything involving tokens needs a FluxerList account. Sign in at fluxerlist.com with Fluxer once, and the bot recognises you from then on.

A server can be bumped once every 12 hours. The message says how long is left and shows a live countdown. Turn on bump reminders to get pinged when it’s ready.

It’s usually missing permissions in that channel. Run !setup check in a channel where it can post: it lists what the bot has and what’s missing (View Channel, Send Messages, Embed Links, and Read Message History are required). If the bot can’t post where you ran a command, it DMs you the reply along with what to fix (unless you turned that off with !usersettings permdm off). Muting the bot or blocking it from a channel isn’t the fix for a shared prefix, use !prefix <new> instead.

The new prefix applies immediately. If you forget it, mention the bot with @FluxerList prefix and it tells you what it is. Prefixes can be up to 5 characters.

Another bot in your server probably shares the prefix. The cleanest fix is a prefix of your own with !prefix <new>, so commands stop triggering both bots. To keep it, switch the nudge off with !dym off. You don’t need to mute the bot: mentions like @FluxerList ping always work.

See Notifications. The usual causes are a missing channel, missing permissions there, or a deleted webhook.

That server is already pending or live on FluxerList, or your account has reached the number of servers it can list. Check your dashboard.

FLAT needs the bot in your server and tracking turned on. Check with !flat. Scores update hourly, so give it a little time after the bot joins. See FLAT activity score.