Creating Appeal Forms
Since version 8.4 "Halcyon", Appeals share the same drag-and-drop Visual Form Builder as Applications, with a few extra appeal-specific settings. The legacy template selector (Ban / Mute / Warning / General templates) was removed — every appeal form is built from scratch with the visual builder.
Opening the Builder
- Open Appeals in the sidebar
- Click New Form to start a blank form, or Edit on an existing card
- The builder opens with four tabs: Build, Logic, Settings, Preview
The Build, Logic and Preview tabs work identically to Applications → Creating Forms. Refer to that page for field types, page logic and the canvas layout. This page covers what is specific to appeals.
Appeal Settings
The Settings tab includes the standard form options (status, notifications, cooldown, resubmissions, max per user) plus these appeal-specific sections:
Appeal Type
| Field | Choices | Why it matters |
|---|---|---|
| Type | Ban Appeal · Mute Appeal · Warning Appeal · General Appeal | Drives the badge shown on the user's My Appeals page and which moderation action the auto-action targets |
| Platform | Roblox · Discord | Where the original punishment was issued. Used by auto-action to decide whether to call Discord or the Adonis plugin. |
Appeal Actions
| Toggle | What it does |
|---|---|
| Auto-action on approval | When a staff member approves the appeal, automatically unban or unmute the user on the configured platform. Off means approval is just a record — staff still has to revert the punishment manually. |
| Require original punishment | Force the appellant to link to the original ban / mute / warning ID before submitting. Helps reviewers cross-check, and is required for auto-action to know what to reverse. |
Visibility
The Public toggle decides whether the form appears on your server's public landing page. Private forms are still reachable through their direct URL — useful if you only want to share the link in DMs or punishment messages.
Form Limits
You can have up to 10 active appeal forms per server (twice the limit of applications, because most servers run separate forms per punishment type and platform). Pause or archive old forms to free a slot.
Recommended Setups
Separate forms per punishment type
Most servers create four forms — Ban, Mute, Warning, General — each with a focused set of questions and the matching Type selected. This keeps the badge accurate, lets staff filter submissions by type, and means auto-action only ever touches the right kind of punishment.
One form per platform
If you moderate Discord and Roblox separately, splitting forms by platform lets you wire up auto-action per side without one form trying to do both.
General appeal as a fallback
Keep one General Appeal form public for edge cases your other forms don't cover. Set "Require original punishment" off so users can submit even when they don't know the exact ID.
Field Suggestions
Use the visual builder's Static text field for the disclaimer / rules block instead of a Yes/No question. Then ask:
- Roblox username / Discord ID (Short text, required) — even if "Require original punishment" is on, having it as a field gives reviewers context.
- What happened? (Long text, required)
- Why do you believe the action should be reversed? (Long text, required)
- What will you do differently? (Long text, required)
For Warning Appeals, replace the last two with Why was the warning unjustified? and an optional Evidence link (URL field).
Best Practices
- Match the form Type to its purpose — appeal type drives both the user-facing badge and the auto-action logic.
- Keep appeal forms shorter than application forms. Three to five well-chosen questions outperforms a ten-question wall of text.
- Turn Auto-action on approval off if your team likes to do the unban manually as a final sanity check.
- Use Cooldown hours generously (24h+) on Ban Appeals to discourage spam.
- Make sure your moderation log channel is configured before enabling auto-action — every reversal is logged there.