Most "the bot isn't working" reports come down to permissions, not bugs. Fluxer, like Discord, gives bots access through roles and per-channel overrides. This page walks through what the bot needs, in the order that fixes problems fastest.
Quick triage
Run !help in a public channel (one with no special permissions). No reply? It is a permissions or invite issue, not the command.
Still nothing? Temporarily grant the bot's role Administrator and try again. If it now works, a specific permission or channel override was the cause. Narrow it down below, then remove Administrator if you prefer least-privilege.
Works in one channel but not another? That is a channel/category override. See Channels & overrides below.
Role permissions the bot needs
When you invite the bot, it comes with a role (named after the bot). That role must keep at least:
Create Emojis & Stickers and Manage Emojis & Stickers: required for the emoji pack (see below). On some instances these are labelled Create Expressions / Manage Expressions.
The Administrator invite on your bot page includes all of these. If you invited with a stripped-down link, the fastest fix is to re-invite with Administrator (it only adds missing permissions, it will not remove the bot).
Tip: keeping the bot's role above the roles it needs to manage matters for role rewards and moderation. Fluxer never lets a bot act on a role higher than its own.
Channels & overrides
A bot that has a permission at the server level can still be blocked in a specific channel. This is the single most common "it only works in #gen-chat" cause.
Open the channel (or its category) → Permissions.
If the bot's role or @everyone is denied View Channel or Send Messages there, the bot goes silent in that channel even though it works elsewhere.
Add the bot's role to the channel with View Channel + Send Messages allowed, or give the bot a role that already has access.
Categories cascade: fixing the category usually fixes every channel under it, unless a child channel has its own override.
If you locked a channel to mods/staff only, the bot is not a mod. Add its role explicitly.
Emoji pack setup
Pluuty ships button/menu icons (music controls, help, Kick / Twitch / YouTube / Spotify) as custom emoji it uploads into one server you manage.
Invite the bot with Administrator so Create Emojis & Stickers and Manage Emojis & Stickers are included.
In a channel the bot can see, run !emojipack sync as the bot owner, server owner, or someone with Manage Server.
Confirm with !emojipack status.
If sync reports a permission error, the two emoji/expression permissions are missing. Re-invite with Administrator (or toggle them on the bot's role) and run !emojipack sync again.
Command prefix (and DMs)
The default prefix is !, so the command is !emojipack sync, not@!emojipack.
You can mention the bot instead of the prefix: @YourBot emojipack sync. That is a normal mention, not @!.
Change the prefix per server with !prefix or in General settings.
DMs: only a few flows use direct messages (support, some confirmations). Everyday commands run in a server channel. If DMs never arrive, allow direct messages from server members in your Fluxer privacy settings.
Changing the bot's name & avatar
This trips people up, so it is worth stating plainly:
The name, color, and avatar in the Pluuty dashboard are the label and embed identity Pluuty uses (what shows on embeds and in your bot list).
The bot's real username and profile picture, what Fluxer shows in the member list and DMs, live on the Fluxer application you created: User Settings → Applications → your app → Bot. Change them there.
After you update them in Fluxer, the new name/avatar appears within a few minutes. Restarting the bot from the dashboard is not required for this.