Help
FAQ and troubleshooting
Fixes for when Dexy doesn't answer, says you need a permission, can't track invites, can't give roles, or a counter won't update.
Start with d!diag. It checks Dexy's permissions and setup in your server and says what to fix. On the dashboard, the same check is on the server's Overview.
d!diag
d!diag
Dexy doesn't answer a command#
Work through these in order:
- Is it the right prefix? Mention Dexy with nothing else (
@Dexy) and it replies with the prefix used in this server. A prefix ending in a letter or number, likepp, needs a space before the command:pp stats. - Is the prefix turned off? With the prefix off, only mentions work:
@Dexy help. An admin turns it back on withd!settings prefix on, or with Prefix commands on the dashboard's General page. - Are commands limited to some channels? If the server set command channels, Dexy stays silent in the others, so the channel doesn't fill up with refusals. Admins and roles with the
commandsrole permission can use commands anywhere. Seed!settings channels. - Are commands limited to admins? With command access set to admins only, Dexy stays silent for everyone else. See
d!settings access. - Can Dexy see and post in the channel? Dexy needs View Channels, Send Messages, Embed Links and Read Message History there. Check the channel's and its category's permissions for Dexy's role.
d!help, d!invite, d!links, d!ping and d!privacy work in any channel, for anyone, whatever the settings.
Dexy says a module is turned off#
Each module can be switched off per server. When it is, its commands answer with a message saying so, and the command that turns it back on. An admin can run it, or switch the module on from the dashboard's Overview.
d!modules
d!modules enable stats
d!modules
d!modules enable stats
Dexy says "You need Manage Server…"#
Commands that change something need the Fluxer permission that fits the job, such as Manage Server for settings, Manage Channels for counters or Ban Members for bans. The message names the permission. Administrators, the server owner and the Dexy admin role pass these checks.
Other ways in:
- An admin can give your role part of Dexy with role permissions, like
settingsorcounters. See Permissions. - If you have Manage Server but are still refused, the server may have changed whether Manage Server counts as a Dexy admin. The message then says which roles count, or that it doesn't count at all.
"You can't use that command here" means another check refused it. The permissions matrix lists what each command needs.
Dexy is missing a permission#
d!diag marks each missing permission with what stops working without it. ❌ means Dexy can't work properly; ⚠️ means one feature is affected.
To fix it, give Dexy's role the permission in your server settings, under Roles. If one channel is the problem, check that channel's and its category's permissions too. The getting started guide lists every permission Dexy uses and why.
"Slow down, try again in …"#
Some commands have a cooldown, so they can't be repeated too fast. Stats cards and charts, for example, can be run once every 8 seconds per person, d!purge once every 10 seconds per channel, and d!lock once every 10 seconds per server. Dexy replies with how many seconds are left.
The cooldown of each command is on its page in d!help <command> and in the command reference.
Counters have limits of their own, because they create, delete and rename Fluxer channels. A server can make 5 counters and delete 5 counter channels in any minute, and each counter can be renamed or relinked 5 times a minute. d!counter setup counts as 3, as it makes 3 counters. On the dashboard, a button that has to wait shows how long.
A counter isn't updating#
- Is the Counters module on?
d!modulesshows it. - Does Dexy have Manage Channels? Counters can't be renamed without it.
- Did the counter fail?
d!counter listmarks a counter whose last update failed with ⚠️, andd!diagand the dashboard's setup check say what went wrong. - Is it just not time yet? Counters update on a schedule that depends on what they show. Times and online counts update most often, member counts every 30 minutes, message and voice stats every hour, and dates once a day.
d!counter speedchanges it.
See Counters for more.
Invites aren't being tracked#
Invite tracking needs Manage Server, so Dexy can read the server's invites. Manage Channels helps too: without it, new or deleted invites aren't noticed until the next check.
If d!diag says invite tracking is blocked by 2FA, the server requires two-factor authentication for moderator actions, which stops Dexy from reading invites. An owner can lower that requirement in the server settings.
Joins from before Dexy joined, or before it had the permission, can't be matched to an invite afterwards.
Dexy can't give or take a role#
Two things are needed:
- Dexy has Manage Roles.
- Dexy's highest role is above the role it gives or takes. Drag Dexy's role up in your server's role list.
The same goes for moderation: Dexy can't time out, kick or ban someone whose highest role isn't below Dexy's. Moderators can't act on someone whose highest role isn't below theirs either (the owner can act on anyone).
Some channels aren't in my stats#
Dexy only counts channels it can see. d!diag lists the channels it can't see; give Dexy's role View Channels there if they should count. Channels ignored on purpose with d!settings ignore aren't tracked either.
Filters, like the channel filter or leaving bots out, only change what stats show. Dexy keeps counting everything, so you can change a filter back any time.
The dashboard says it isn't open to me#
The server's stats are for its admins. Ask an admin to open them to members (Dashboard access on the Permissions page, or d!settings dashboard members), or to give your role the view role permission. To change settings you need to be a Dexy admin, or have a role permission for that area. See The dashboard.
The dashboard keeps your server list for a few minutes. If you just joined a server or got a new role, wait five minutes and reload.
Where can I get help?#
Join the support server. Mention what d!diag says, and the command you ran.