Discord Server Builder

What it is

/build-server interviews a server owner about their community, shows them exactly what will be built, and only then creates it: categories, channels, roles, a written welcome message and rules, verification settings, AutoMod rules, a generated server icon, native onboarding, and a support-ticket panel.

Nothing is created until the owner approves the preview. Every build can be undone within 7 days.

Running it

Requires Administrator on the server. In any text channel:

/build-server

1. Pick a mode - Fresh server, Update server, or Rebuild (rebuild deletes existing channels first and needs a second confirmation - it cannot be undone automatically past 7 days).

The rest of this section is the Fresh server flow.

2. Answer 5 questions in a form: topic, server name, audience, anything it must have, anything to avoid.
3. Pick 4 details: size, vibe, safety level, and any extras (tickets, onboarding, voice channels, events, announcements-only, a VIP tier).
4. Review the preview - the exact category tree, roles, rules text, AutoMod rules and (if picked) onboarding/tickets setup. Nothing exists on Discord yet.
   • ✅ Build it - creates everything.
   • ✏️ Change something - describe what should be different (up to 5 revisions), get a new preview.
   • ✖️ Cancel - nothing is created.
5. The build runs - this can take a minute for a large server. A report lists what was made and anything skipped, with an ↩️ Undo this build button.

What every server gets

Regardless of what you pick, every build includes:

Roles

Every server gets the same base ladder, top to bottom:

Founder › Admin › Mod › Bot › OG › Member

Picking the ⭐ VIP / paid tier extra adds VIP above OG. The builder also adds up to 3 roles specific to your community (e.g. "Speedrunner", "Artist"), which sit just above Member and are cosmetic only.

Roles are re-ordered after creation so the hierarchy is right - Discord creates new roles at the bottom, so without that step the ladder comes out upside down.

Safety levels

Lockdown stops raids effectively, but it also stops real members without a verified phone. Pick it only if the server has had a raid problem.

What gets protected automatically

Once built, none of this needs the bot to stay online - it all runs on Discord's own infrastructure:

• AutoMod: profanity/slurs filter, spam detection, mention-spam limits, invite-link blocking, plus a short list of terms specific to the community's topic. Violations post to a staff-only mod-log channel.
• Verification & content filter: set from the chosen safety level.
• Onboarding (if picked): a native "what brings you here" flow that assigns roles on signup - no bot uptime required. Discord requires at least 5 channels members can post in before it accepts an onboarding config; if your layout has fewer, the preview says so and onboarding is skipped while everything else still builds.
• Server icon: generated from the community's description and set automatically.

Not included: a custom server banner. Discord requires Boost Level 2 for a banner (Level 1 for an invite splash image) - a brand-new server has neither. The icon is set on every build; the banner isn't offered until the server actually qualifies.

Tickets

If picked, a full ticket panel is created - the same system /ticket panel uses on its own. See Discord Ticket Panels for the full configuration options (staff roles, opening questions, cleanup). Run /ticket config any time after the build to customise it.

Updating an existing server

If your server already exists and has members, the interview is the wrong tool - it assumes an empty server. Run /build-server and pick 🔧 Update server instead.

1. It reads your server

A read-only scan. Nothing is changed. You get back three things:

What's here now - category, channel and role counts, member count, verification level, media filter, AutoMod rule count, whether Community mode and a server icon are set, and how many tickets are already on record.

What needs fixing, ranked so the dangerous items can't hide behind the cosmetic ones:

The log ladder

Both a fresh build and an update can create four separate log channels, each with a different audience - a single #mod-log cannot express this, which is why they are four:

On an update it adds only the rungs you don't already have. If your admin role is called something else ("Owner", "Head Staff"), the real role is used - so the channel is never hidden from everyone including your own staff.

Name polish

The one item that renames anything, which is why it is its own tick, off by default, and shows every change before it runs.

It keeps your words and adds the house style: welcome → 👋│welcome, General Chat → 💬│general-chat, bot-log → 🤖│bot-log. An emoji you already chose is kept, not replaced.

A rename changes the label and nothing else - same channel, same id, same messages, same pins, same permissions, same category. /server undo puts the old names back for 7 days.

What you can add - everything the bot offers, each with its real state here:

Each is marked with its state:

• ➕ not here yet - it would be created
• 🔗 you already have a channel for it - the panel attaches to that one, no new channel
• ✅ already set up in this server. Not offered again, so you can't end up with two panels
• 🎁 included with the bot, nothing to set up

If the bot is missing permissions, that is reported here instead of failing halfway through a build later.

2. You tick what to fix and what to add

Two separate dropdowns - one for fixes, one for adds. Nothing is pre-ticked. Each option says exactly what it will do. If you tick Weak protection settings, a third dropdown appears for how strict (Relaxed, Standard, Strict, Lockdown - the same levels as above).

Some picks need another one to work, and the plan screen says so rather than silently skipping:

3. You approve the exact plan

A plain list of every change, a list of anything worth knowing first, then ✅ Do it, ↩️ Back, or ✖️ Cancel. Nothing has been created at this point.

Adding tickets to a server that already has them

This is the case worth being precise about.

• You already use our tickets. The feature shows as ✅ installed with the channel it lives in, and isn't offered again. Change it with /ticket config.
• You have open tickets from our system. They keep working exactly as they are. The count is shown on the scan and repeated as a warning on the plan screen. A new panel does not touch existing tickets, transcripts, or channels.
• You use another bot's tickets. Ours posts its panel and manages only the tickets opened from that panel. Tickets from the other bot keep working in their own channels.

What this mode will never do

Specifically:

• New channels match your naming style. If your channels are 🎮│gaming, new ones get an emoji prefix too. If they are general-chat, new ones are plain. Anything the model names that already exists is dropped rather than reused.
• Existing channels never have their permissions changed. New channels like rules, announcements and verify are created read-only; a rules channel you already had gets the rules posted into it and keeps its current permissions.
• Verification and the media filter are only ever raised, never lowered, and only when you tick that box.
• Your server is never renamed, and the icon is only replaced if you tick the icon box.
• /server undo only removes what this build created. Every existing channel or role the plan reused is recorded as pre-existing and skipped by undo.

Managing a built server

/server audit    - checks that what the builder made is still in place
/server resume   - continues a build that got interrupted
/server undo     - removes everything the LAST build created (7 day window)
/server add      - "add a channel for tournament signups" - adds one category
/server tune     - change the safety level after the fact

/server audit checks existence (roles, channels, AutoMod rules still there, bot permissions still granted) - it does not detect an owner manually loosening a setting the builder made.

Building and managing from the web

amnt.io/discord has the same builder as a web form - no Discord field-count limits, and a live preview as you type.

1. Click Add to Discord. Pick an existing server, or create a new one right there in Discord's own flow - the bot never creates a server for you (Discord doesn't allow that for a bot already in many servers), but you never have to leave the page to make one.
2. You're redirected back to a build form for that server.
3. Run /link in that server once, so amnt.io knows which Discord account is yours - the same command the Discord bot itself uses.
4. Fill in the form, review the preview, approve it. Same engine, same preview, same undo window as /build-server.

Afterward, amnt.io/discord/servers lists every server you've built - an audit summary and a 7-day undo button for each, without needing to be in Discord at all.

⚠️ Every action re-checks that your linked Discord account actually has Manage Server on that guild - a link in your browser's address bar proves nothing on its own.

What the bot needs

The bot's role needs Administrator, or all of: Manage Roles, Manage Channels, Manage Server. /build-server checks this up front and refuses with the exact missing permission rather than silently skipping steps.

Limits worth knowing

• AI actions are capped at 30 a month per person (100 once you /link an amnt.io account). A build, each revision, an "Update server" plan and /server add are one action each. The cap follows you, not the server, so installing the bot in more servers does not give you more. See the bot's limits.
• A rebuild snapshots channel/category names before deleting them, but does not restore anything automatically - only a fresh build follows it.
• Onboarding needs the server's Community features enabled first, which itself needs a rules channel and a few public channels - the preview flags this before you approve if the layout doesn't qualify.
• Discord allows at most one AutoMod rule of each type (spam, mention spam, keyword-preset) per server - the builder combines everything of one type into a single rule rather than one per concern.