Every plugin page in the dashboard is built the same way: a header with the plugin's icon tile, its name, a status chip (Enabled / Disabled), a Docs button that opens the matching handbook page in a new tab, and the Enable / Disable button; then tabs, then sections of fields. Learn the page once and you can operate all of them.
The Enable / Disable button in the page header is stored separately from the settings below it. It answers one question: should this plugin run on this server?
The button saves immediately — there is no separate save step for the switch itself. The small icon
tile next to the plugin in the sidebar reflects the current state: filled when enabled, grey when
disabled. The same tiles appear in the Quick actions palette (Ctrl/⌘ + K), which jumps to
any page or plugin by name.
For premium plugins there are two facts, and Cloudy deliberately keeps them apart:
| Fact | Stored where | Meaning |
|---|---|---|
enabled | Your plugin settings | "The admin wants this on" |
| license active | Your premium license | "This server is entitled to it" |
The plugin runs only when both are true. Cloudy never writes the license state into the toggle, which has one very practical consequence:
Until then, the page renders as a locked preview: you can look at every setting, but a popup points you to the Premium page, a lock bar reading Preview only — premium required stays at the bottom once you dismiss it, and saving is blocked. Premium plugins carry a small crown badge in the sidebar.
Every plugin uses one of three shapes. Recognising which one you are on tells you how it behaves.
One set of settings per server. You edit fields, the save bar appears, you save.
Welcome & Goodbye, Leveling, Birthdays, Polls, Economy, Animals, Temp Voice, Reminders.
A list of items you create, edit and delete individually — panels, rules, subscriptions, commands, counters, schedules. Each item has its own editor; there is no page-wide save bar, saving happens per item.
Tickets, Verification, Honeypot, Reaction Roles, Giveaways, Custom Games, Counter Channels, Scheduled Messages, Embed Messages, Automations, Custom Commands, Twitch, Kick, YouTube, TikTok.
Several sub-features under one plugin, split into tabs. Each tab saves independently.
Moderation (logging, AutoMod, protection, cases, channel locks, feedback, sticky messages, commands).
Plugins that ship slash commands have a Commands section (a tab of its own on the Moderation page) listing every command, what it does, and which Discord permission a member needs to use it. All commands are registered globally once; disabling a plugin does not remove them from Discord, it makes them answer that the plugin is disabled.
Some plugins deliberately have no commands at all — reaction roles, embed messages and automations are configured entirely from the dashboard, and the bot maintains the Discord side on its own.
Each plugin owns its own tables. This matters in two places: