FormsPrivate applications with a reaction-powered editor.

Form Menu

Form Menu puts every form setting on a paginated reaction menu, so you can build and edit a form without memorising a command for each field.

Opening the menu

Form Menu opens automatically after a form is created, or whenever you run f!forms setup or f!forms edit <form>. If the community has more than one form, f!forms setup opens a paginated picker first.

Fluxer
f!forms create StaffApp
f!forms setup
f!forms setup StaffApp
f!forms edit StaffApp

One editor, fewer commands

The existing field commands still work, but the menu is the fastest way to change several settings in a row.

Moving around

Use the arrows to move between pages. The footer shows your current page and section. Question lists are split into pages of five, and those question pages are part of the same arrow navigation.

ReactionAction
⏪Jump to the first page.
⬅️Previous page.
➡️Next page.
⏩Jump to the last page.
❌Close the menu from a normal page.

When a question is open, the same arrows browse individual questions instead of moving between sections. React ↩️ to return to the question list.

What each page edits

PageSettings
BasicsName, description, panel color, panel image, and panel emoji.
QuestionsAdd, edit, reorder, and delete questions. Questions are shown five per page.
AccessPanel channel, review channel, reviewer roles, and roles required to submit.
BehaviorCooldown, multiple submissions, accepted-submission limit, reviewer pings, applicant DMs, and anonymous review.
MessagesIntro, confirmation, accept, and decline message templates.
PublishPreview the panel, open or close the form, and publish the reaction panel.

Editing Basics

React 1️⃣ through 5️⃣ to edit the matching value:

  • 1 Name - the form and panel title.
  • 2 Description - shown on the published panel.
  • 3 Panel color - a six-digit hex color such as #A52F05.
  • 4 Panel image - an http(s) image URL.
  • 5 Panel emoji - the reaction members use to start the form.

When a setting needs free text, the menu replaces the reactions with a prompt. Reply in the same channel; type cancel to leave the setting unchanged. Optional values also accept clear.

Building questions

On the Questions page, react with a number to open a question or with ➕ to add one. Choosing a type opens a prompt for the question text; choice questions use the same pipe-separated format as the command fallback:

Choice format
Prompt | Option 1 | Option 2

At least two choices are required, and up to ten are supported. New questions start as required; use the required toggle in the question detail view to mark one optional.

ControlAction
1️⃣Edit the prompt.
2️⃣Change the type between short text, paragraph, and multiple choice.
3️⃣Toggle required on or off.
4️⃣Edit the choices on a multiple-choice question.
5️⃣Move the question up one position.
6️⃣Move the question down one position.
🗑️Delete the question after confirming with ✅.
↩️Return to the question list.
⏪ ⬅️ ➡️ ⏩Browse individual questions.
If you change a multiple-choice question to another type, its choices are cleared. If you switch another question to multiple choice, the menu asks for the choices before saving the change.

Access and Behavior

The Access page sets the panel channel, review channel, reviewer roles, and roles required to start the form. For channels, send a mention or channel ID; for roles, send role mentions or IDs. Use clear to remove a channel or clear all roles from that field.

The Behavior page toggles multiple submissions, reviewer pings, applicant decision DMs, and anonymous review. It also edits the cooldown and the per-member accepted-submission limit. Cooldowns accept values such as 24h and 7d; enter 0 or unlimited for no accepted-submission limit.

Message templates

The Messages page edits the intro, submission-confirmation, acceptance, and decline messages. Templates support {form}, {user}, and {reason}. Type reset to restore the default text.

Publishing from the menu

The Publish page lets you preview the panel, open or close the form, and publish the panel without leaving the editor. Preview the panel first; the footer tells you whether the form is a draft, open, or closed.

Opening a form requires at least one question, a panel channel, and a review channel. Publishing the panel also requires the form to be open.