Plugins & toggles

Every plugin page in the dashboard is built the same way: a header with the plugin's name and its master switch, then tabs, then sections of fields. Learn the page once and you can operate all twenty.

The master switch

The toggle in the page header is stored separately from the settings below it. It answers one question: should this plugin run on this server?

Off — the plugin registers nothing, listens to nothing and writes nothing. Its configuration stays in the database untouched.
On — the plugin runs. Slash commands appear in Discord within a minute or two (Discord controls that timing, not Cloudy).

Toggling saves immediately — there is no separate save step for the switch itself. The little dot next to the plugin in the sidebar reflects the current state.

Turning a plugin off is the correct way to pause it. There is no reason to delete your panels or clear your fields first — an off plugin costs nothing.

Enabled vs. effectively enabled

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:

When a license lapses, your toggles stay exactly as they were. The moment premium comes back, every plugin you had running is running again — you do not have to re-enable twenty plugins by hand.

Until then, the page renders in preview mode: you can look at every setting, but the save bar is locked and the sidebar shows the premium star.

The four page templates

Every plugin uses one of four shapes. Recognising which one you are on tells you how it behaves.

Singleton form

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.

CRUD list

A list of items you create, edit and delete individually — panels, rules, subscriptions, commands. Each item has its own editor; there is no page-wide save bar, saving happens per item.

Tickets, Verification, Reaction Roles, Giveaways, Custom Games, Embed Messages, Automations, Custom Commands, Twitch, Kick, YouTube.

Compound

Several sub-features under one plugin, split into tabs. Each tab saves independently.

Moderation (logging, AutoMod, channel locks, sticky messages, feedback, commands).

Toggle & info

Nothing to configure beyond the master switch; the page explains what the plugin does and lists its commands.

The Commands tab

Plugins that ship slash commands have a Commands tab listing every command, what it does, and which Discord permission a member needs to use it. Commands are registered when the plugin is enabled and removed when it 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.

Where plugins store data

Each plugin owns its own tables. This matters in two places:

Disabling a plugin keeps everything.
Resetting the server (on Server defaults) deletes member data — levels, balances, animals, birthdays, warnings, reminders, points — and removes every panel from Discord. That one is not reversible.

First setup

A 20-minute path from an empty configuration to a server that greets, moderates and rewards its members.

Saving & syncing

What the save bar counts, which fields actually get sent, how long the bot takes to notice, and what happens when a save fails.