amnt docs
Creators

Discord Roles, Giveaways, Scheduling and Backup

Self-assign role panels, a verify gate, giveaways, scheduled posts, and server backup/restore - all webhook-only, no bot uptime required.

Button roles - /roles panel / /roles config

Self-assign roles by clicking a button - no reactions, no gateway needed.

/roles panel               post a new panel in this channel
/roles config [panel_id]   edit staff - err, member - roles, text, exclusivity

/roles config opens a dashboard with a native role picker (up to 20 roles per panel), a text/color editor, an Exclusive toggle (picking one role removes any other from this same panel - good for "pick your region" or "pick your pronouns"), and a repost button.

Clicking a role button toggles it: click once to add, click again to remove.

Verify gate - /verify panel / /verify config

A locked-down server where new members see only a #verify channel until they click a button that grants one role.

/verify panel               post a new verify panel in this channel
/verify config [panel_id]   pick the role it grants

Stops raid bots that never interact, without requiring a verified phone number the way safety level "Lockdown" does - pair it with a stricter safety level for defense in depth, or use it alone for a lighter touch.

Giveaways - /giveaway

/giveaway start prize:"Nitro" duration:2h winners:1
/giveaway end [giveaway_id]      end early (default: the latest active one here)
/giveaway reroll [giveaway_id]   pick new winner(s), excluding previous winners

duration is relative: 30m, 2h, 1d. Members click Enter to join, click again to leave. Giveaways end automatically on schedule (a cron checks every 5 minutes) - /giveaway end is only for ending one early.

Scheduled posts - /schedule

/schedule post message:"..." when:2h
/schedule post message:"..." when:"2026-09-01 09:00"
/schedule list
/schedule cancel post_id:<id>

when accepts a relative duration (2h, 1d) or an absolute date/time. Posts go out on a 5-minute cron sweep - not to-the-second precision, but close enough for an announcement.

Server backup and restore - /backup

/backup export                    snapshot this server's roles + channels
/backup list                       see your backups
/backup restore backup_id:<id>    restore INTO this server

Restore is additive - it never deletes anything, and reuses an existing role or channel with the same name rather than duplicating it. Run /backup export in server A, then invite the bot to a brand new server B and run /backup restore there with the same id to recreate the structure.

⚠️ One approximation, stated plainly: Discord roles carry an arbitrary permission bitfield. A backup classifies each role into the same three tiers /build-server itself uses - admin, moderator, or member - not a byte-for-byte copy of an unusual custom permission set. Good for "get my structure back after a nuke"; not a forensic backup of exotic per-role permissions.

What none of these need

Every feature on this page is button/command-driven, so none of it needs the bot to run a persistent connection (a "gateway") - the same architecture choice behind the Server Builder and Ticket Panels. The only things this architecture genuinely cannot do: a welcome DM on join, or auto-assigning a role the instant someone joins without them clicking anything - native onboarding (built into the Server Builder) covers the real need behind both.

On this page