Guided configuration

Cakemix does not treat a plugin’s storage schema as its user interface. Built-in plugins provide task-specific workspaces; third-party plugins receive a generated setup flow from their public setting metadata.

Setup flow

1. Open Server → Control room and choose the work you want to configure.
2. Review the plugin status and Discord permission warnings.
3. Choose a recommended preset when one is available.
4. Complete essential fields. Dependent fields appear only when relevant.
5. Review the exact proposed effects.
6. Save once. Popii validates the complete request, rejects unknown fields, checks the configuration version, persists atomically, and creates an audit event.

Advanced settings remain available, but they are not mixed into the initial task. No privileged setting autosaves.

AutoMod

Open /app/servers/:guildId/admin/automation/automod. Start with Off, Standard, or Strict, then review rule families for spam, mentions, invites, links, blocked words, capitals, emoji, AI analysis, and anti-raid behavior. Each rule presents a short human-readable summary before its detailed thresholds.

The policy simulator evaluates sample message content through pure rule logic. It does not send a Discord message or take moderation action.

Settings and recovery

Configuration lives inside each plugin workspace at /app/servers/:guildId/admin/plugins/:pluginId. Task-oriented section routes contain at most eight closely related controls, and each section saves independently without submitting hidden or unrelated values. Every save uses optimistic concurrency. If another manager saves first, refresh, review their version, and reapply the intended changes. The former general settings URL redirects to the relevant workspace.

Create a restore point under Server → Recovery before a large change. Restoration creates another automatic backup and leaves the current configuration intact if any step fails.