Turning things on and off
FlaviBot ships everything at once, and almost nothing is active until you turn it on. Two levels of control exist: modules (levels, starboard, tickets, welcome, ...) and individual commands.
Reading the status dots
Every module in the sidebar carries a dot:
| Dot | Meaning |
|---|---|
| Green | the module is on and healthy |
| Grey, with a dimmed label | the module exists but is off |
| Amber, with a number | that many of its configurations are in error |
| Red, with a Disabled badge | the FlaviBot team has disabled this module globally |
A red dot is not something you did. Hovering it shows the reason the team gave when they switched the module off, for example an incident on a third-party service. It comes back on its own.
The amber count is the useful one day to day: it means a config you saved cannot run, usually a missing permission or a deleted channel. The module's own page shows which one.
Pages that are not modules (Configuration, Access Logs, Cases) have no dot. Jobs shows a pulsing dot with a count instead, while a batch job of yours is running.
Turning a module on
Modules come in three shapes.
One switch, one dialog. Levels, Birthday, Economy, Boost, Server Tag, Invite Tracker, Server Logs and Persistent Roles turn on from the sidebar: clicking one while it is off opens a short confirmation, and confirming enables it and takes you to its page to finish configuring. That confirmation applies immediately, with no save bar step.
On by being configured. Welcome and Goodbye, and DJ Mode, have no bare enable switch: they come alive once you fill them in and save.
Many configurations. Starboard, Ticketing, Counting, Sticky Messages, Temp Voice and the notification feeds (YouTube, Twitch, Kick, Reddit) hold several entries, each with its own switch: several starboards, several ticket panels, several watched channels. The module reads as on as soon as one of its entries is set up and active.
Tools such as Custom Commands, Embed Messages and Forms work the same way: there is no global switch, they light up once you create your first entry.
Turning a module off
Single-switch module pages (Levels, Birthday, Economy, Boost, Server Tag, Invite Tracker, Server Logs, Persistent Roles, Welcome, DJ Mode) have their own Enabled switch: turn it off, then press Save Changes in the bar at the bottom. Multi-configuration modules have no module-level switch — you turn off each entry with its own switch, and that applies immediately. Configuration is kept, so turning it back on later restores what you had.
Disabling a single command
Configuration → Commands Settings lists every command with a search box
and a switch each. A disabled command still appears in Discord's / list (that
list is global to the bot), but running it answers, privately, that the command
has been disabled by the server administrators, with a link to this page.
Next to the switch, Configure access opens the per-command rules:
| Mode | Effect |
|---|---|
| No restriction | anyone, anywhere (default) |
| Whitelist | only the channels, roles or users you list |
| Blacklist | everyone except the ones you list |
Channels, roles and users are three independent lists, up to 50 entries each. The same dialog exists per category (Bot, Administration, Moderation, Music, Utility, Economy) when you want to gate a whole family at once.
Which rule wins
The order matters and it is deliberate:
- If a rule exists for this command, it decides, and the server-wide presets are ignored.
- Otherwise, if a rule exists for its category, that decides.
- Otherwise the server-wide presets from the previous page apply.
Saving a per-command rule with every mode set to No restriction is therefore meaningful: it says "this command opts out of the global preset". Reset to default removes the override and puts the command back under the global rules.
