Presets

A preset is a rule, or a whole group with its panel, packaged so it can be installed on any server.

Installing

Pick one in the marketplace, choose the target server, and fill in the blanks: roles, channels, emojis, durations. The preview shows what it will do, with your picks appearing in place as you fill them.

Everything is validated before anything is created. If a preset needs three rules and you have room for two, nothing is installed at all: you are never left with half a setup.

A preset that installs a group takes you straight to the group editor, where you publish the panel and adjust anything you like. Installed rules are yours: editing them never affects the original.

Sharing

Any rule you own can be shared from its editor, and any group from the group page. FlaviBot rewrites your server's specifics into blanks: roles, channels, categories, emojis. What it cannot rewrite, it refuses:

• Specific members: an id means nothing on another server, so a rule targeting one is refused rather than shipped broken
• A panel button wired outside its group: its target would not travel
• Scheduled and webhook rules: a schedule and a secret URL are not shareable objects

Your @everyone role becomes a variable that resolves on the installing server, so a "make this channel private" preset stays private.

Submissions are reviewed before they appear publicly. Presets that can kick, ban or time out members must be curated before they can be published. That rule is enforced by the database itself, not just by the review page.

What travels with a preset

The trigger and its settings, the filters, every action and its conditions, the batching window, and for a group: every rule plus the panel, with the buttons re-wired to the freshly created rules on arrival.

Versions and updates

A preset can be improved after it has been shared. Every published revision gets a number, and the exact content of each one is kept, so nothing an author changes later rewrites what you compared against.

On the preset page, Version history lists the revisions with the author's note, and lets you compare any two of them.

If a preset you installed has been updated, the autoresponder page shows it above your rules. Review changes opens the same comparison, phrased in what it means for your server, before you decide:

• a step that was added, removed, reconfigured or moved
• a setting you will now be asked for, or one that is gone
• a trigger, a filter, a cooldown or a batching window that changed
• a badge when the new version can kick, ban or time out and the one you installed could not

Taking the update replaces that rule's configuration with the new version. Your answers are reused, and so are the rule's name and whether you had paused it, but any edit you made to the rule itself is overwritten. That is why the comparison comes first: it is the whole decision.

When a group's preset gained rules, they are added to your group. Rules it dropped are left alone, because a rule you may have grown attached to is not FlaviBot's to delete.