United Documentation

Clear setup guides for United's protection, moderation, ticket, and server tools.

Quick Start

1. Invite United with the website invite button.
2. Open the dashboard through ,dashboard or the website.
3. Set one Bot Logs channel in Setup → Logs so activity has a clear home.
4. Use Protection Setup to enable and validate the core protection tools.

Anti-Nuke and Anti-Raid

Use the dashboard Protection Setup button for the fastest safe baseline. It checks permissions, creates or finds Bot Logs, and enables the selected protections. Anti-Nuke attributes destructive server changes through Discord audit logs; Anti-Raid watches suspicious joins, bots, accounts, and mass-join patterns.

Recommended first setup

1. Set Bot Logs in Setup → Logs.
2. Open Protection Setup and enable Anti-Nuke, Anti-Spam, Anti-Raid, and account-age checks.
3. Open Permission Health and repair missing permissions or role-position warnings.
4. Use ,antinuke config to review the final configuration.

Anti-Spam and Scam Trap

Anti-Spam now keeps message floods, repeated content, mass mentions, emoji spam, caps spam, and invite-link limits in one control surface. Scam Trap remains a separate immediate-action decoy channel.

Start with ,scamtrap #channel, then set the outcome with ,scamtrap action timeout, kick, or ban. Use ,scamtrap timeout 5m for the timeout length and /scamtrap config to customize the channel warning, member DM, and Bot Logs message.

Tickets

Each ticket type has its own category and role notifications. Edit Ticket Types in the dashboard, choose the exact roles for that type, then edit or refresh the public panel. Ticket activity uses Bot Logs by default; transcripts can use the optional Ticket Logs channel in Setup → Logs.

Ticket workflow

1. Create or confirm the category for each ticket type.
2. Choose the roles allowed to see and receive a ping for that specific type.
3. Save the type, edit the public panel, then refresh the panel only when its message needs updating.
4. Claim, close, or export tickets from Discord or Ticket Center.

Use ,tickets list to see open tickets, ,tickets claim to claim one, ,tickets transcript to export one, and ,tickettimeout 10m when a ticket needs a response window.

Roles and Verification

Autoroles are assigned on join. When verification is enabled, United removes configured unverified roles when the member receives the verified role. Server owners and Discord administrators retain their normal Discord permission-based access.

Sticky Roles keep selected roles through a leave and rejoin. Use ,stickyroles add @StaffBlacklist for a role such as Staff Blacklist. When an appeal is accepted, use ,stickyroles pardon @member @StaffBlacklist to remove that person's current role and their saved rejoin record without changing the rule for anyone else.

Use ,autorole add @Role for automatic roles and the dashboard for verification, role health, reaction roles, and role recovery.

Bot Logs

Setup → Logs has one default Bot Logs channel for all activity. You can optionally split any active United log type, including tickets, moderation actions, voice activity, and every protection module. Existing server channels are reused rather than duplicated.

Use ,logs #channel to choose the all-in-one default. Dedicated commands are optional overrides, not required extra setup.

Command Syntax

United accepts prefix commands with ,. Command names are not case-sensitive, so ,HeLp and ,help behave the same way.

Formatting durations

Use a number immediately followed by a unit whenever a command asks for a duration.

Channels, members, and roles

Use Discord mentions whenever possible. Type # and choose a channel, @ and choose a member, or @ and choose a role. This prevents copy-and-paste mistakes with IDs and names.

Permissions and Role Position

United follows the permissions set in Discord. Server owners and Discord administrators can configure server settings. Moderation actions also require United to have the matching Discord permission and a role above the target member's highest role.

Languages

Set a server language with commands such as ,english, ,dutch, or ,slovak. Use language-specific command references such as ,helpdutch when available.

Set Up a New Server

Use this order for a clean setup. It keeps your server organized and avoids creating duplicate ticket panels, roles, or log channels.

1. Invite the bot. Give United the permissions it requests, then move the United role above any roles it must timeout, kick, ban, mute, jail, or remove.
2. Choose your log channel. In Dashboard → Setup → Logs, choose an existing channel or let United create #bot-logs. This is the default home for moderation, security, tickets, and configuration activity.
3. Check Permission Health. Resolve red checks for Manage Messages, Moderate Members, Kick Members, Ban Members, Manage Roles, Manage Channels, and View Audit Log before enabling protection.
4. Configure protection. Open Protection Setup in the dashboard. It validates the log channel and can enable Anti-Nuke, Anti-Spam, Anti-Raid, and account-age checks together.
5. Configure the member journey. Set Welcome, Autorole, and Verification. If you use an unverified role, set it as the verification role to remove after verification.
6. Add tickets only when ready. Configure the ticket types and panel before publishing one. Existing configured panels are reused during repair; United should not create a second panel or category when a valid one already exists.

Anti-Nuke in Detail

Anti-Nuke watches destructive server actions through Discord audit logs. It can identify repeated channel changes, role changes, bans, kicks, webhook creation, dangerous permission escalation, and unauthorized bot additions. When its threshold is reached, it records the actor, action, result, and incident timeline in Bot Logs and the dashboard.

Before enabling it

1. Confirm United has View Audit Log, Manage Roles, Manage Channels, Kick Members, and Ban Members as appropriate for your chosen response.
2. Move the United role above roles it needs to strip or manage. Discord will not let any bot act on roles at or above its own role.
3. Set a Bot Logs channel. Use ,antinukelogs #channel only if this server needs a separate Anti-Nuke log destination.
4. Enable it with ,antinuke on or use the Anti-Nuke dashboard tab.

Thresholds and actions

Thresholds define how many actions in a time window create an Anti-Nuke event. Keep lower thresholds for destructive changes and use a slightly higher threshold where legitimate staff activity is common.

Available responses are strip_permissions, kick, and ban. Start with stripping permissions while tuning thresholds. The dashboard Incident view includes recovery controls when a destructive change is detected.

Whitelisting

Use ,antinuke_whitelist @member only for a person or bot that must perform actions above the normal threshold. Use ,antinuke_unwhitelist @member to remove it. Whitelisted users are excluded from enforcement; do not use the whitelist as a general staff list.

Anti-Raid and Account-Age Protection

Anti-Raid detects many joins in a short period, can lock writable channels, and records the response. Account-age checks, default-avatar signals, and alt detection use the same universal trusted-member and trusted-role list as the rest of United protection.

Recommended baseline

Universal protection whitelist

Use ,antinuke_whitelist @member for one trusted account or ,antinuke_whitelistrole @role for a tightly controlled staff role. The same exemption applies across Anti-Nuke, Anti-Spam, Anti-Raid, account-age checks, Link Limit, Link Filter, and Scam Trap.

Anti-Spam, Invite Links, and Scam Trap

Anti-Spam and invite-link escalation share one dashboard workspace and one Discord command family. Their scanners remain separate internally so an ordinary flood cannot corrupt an invite countdown. Scam Trap remains an immediate-action decoy channel.

Message spam

Run ,antispam for the overview, ,antispam on to enable it, ,antispam action timeout to choose the response, and ,antispam config message_threshold 5 to tune it. Ignored channels and roles use ,antispam ignore.

Invite links

Run ,antispam links 3 to allow three invite links per five minutes, ,antispam linkaction kick to choose the final response, and ,antispam linktimeout 5m when the response is timeout. ,antispam linkignore manages invite-specific exceptions.

Scam Trap

1. Create or select a channel that normal members should not type in.
2. Run ,scamtrap #channel.
3. Set the action: ,scamtrap action delete, timeout, kick, or ban.
4. For a timeout, set its duration: ,scamtrap timeout 5m.
5. Use ,scamrefresh to refresh the warning panel immediately.

Create a Ticket Panel

A ticket panel is the public dropdown message members use to open tickets. Build ticket types before publishing the panel. Each type stores its own category, staff roles, and optional form questions.

Dashboard setup

1. Open the server in the dashboard and choose Tickets.
2. Select Edit Ticket Types. Add a name, optional emoji, and the category where tickets of that type should be created.
3. Press Roles next to a type and check only the roles that should see and be pinged for that type. Discord administrators can still access tickets through their administrator permission.
4. Press Questions to save up to five required questions. Members complete this form before their ticket opens. Leave it blank to use United's default reason form.
5. Select Edit Panel to set the panel title, description, main image, and thumbnail. Choose the existing channel where the panel belongs.
6. Use Refresh Panel after saving panel text or types. This updates the existing panel message rather than making a duplicate channel.

Discord command setup

,ticketquestions lets an administrator choose a type and edit its form in Discord. ,panel setup shows the setup guide. ,panel creates or reuses a detected existing panel. ,panel_delete deletes panel messages and their saved records only when you intentionally want to replace them.

Ticket Controls, Transcripts, and Timeouts

Once a ticket opens, the member who opened it, roles assigned to that ticket type, Discord administrators, and the permanent owner can access it. Selected roles are not global ticket staff; a role chosen for Staff Reports does not automatically see Support tickets.

Close, reopen, and delete

Every new ticket receives a compact action menu. The ticket creator may close or delete their own ticket. Ticket staff can reopen, save transcripts, and manage the ticket. The Access button and the ,add/,remove commands require Discord Manage Channels, administrator, server owner, or the permanent owner. ,delete saves the transcript first, then removes the channel.

Transcript channel and auto-close

Set the transcript destination with ,ticketlogs #channel or Dashboard → Setup → Logs → Ticket Transcript Channel. If no separate ticket log exists, ticket activity stays in Bot Logs. Set inactive auto-close with ,tickettimeout 24h, ,tickettimeout 3d, or set it to off to disable it. Auto-close will not proceed unless a transcript can be saved.

Welcome Messages

Welcome messages are independent from verification. They announce a new member in the selected channel, while verification controls access and roles. Set up welcome after you know where new members should be sent.

Recommended flow

1. Choose the channel: ,welcome channel #welcome.
2. Run ,welcome setup to choose a starter template, or ,welcome config to open the interactive editor.
3. Use placeholders in the message: {user_mention}, {user_name}, {server_name}, and {member_count}.
4. Optionally set a large image with ,welcome image https://... and a thumbnail with ,welcome thumbnail server, user, or an image URL.
5. Run ,welcome test to preview it for yourself. When it looks right, run ,welcome toggle to enable it.

Use ,welcome examples to view placeholder examples. Use ,welcome save name and ,welcome load name to keep reusable designs. Do not type a raw username if you need a real clickable mention; use {user_mention}.

Goodbye Messages

Goodbye messages announce when a member leaves, is kicked, or is banned. Welcome and goodbye configurations are independent and can use different channels and designs.

Recommended flow

1. Run ,goodbye setup #goodbye to create a starter configuration in an existing channel, or omit the channel to let United find or create one.
2. Open ,goodbye config or Dashboard → Goodbye to edit the title, message, color, image, thumbnail, and link buttons.
3. Use {user_mention}, {user_name}, {user_id}, {server_name}, and {member_count}.
4. Run ,goodbye test before enabling it for real departures.
5. Use ,goodbye toggle whenever the automatic message should be paused.

The departing member is no longer in the server, so {user_mention} is useful for identification but does not notify them. Sticky roles are saved before United sends the goodbye message.

Autorole and Verification

Autorole and verification are designed to work together. Without verification, configured autoroles are given when someone joins. With verification enabled, members can receive an unverified or limited-access role first, then receive the verified role after completing the panel. United removes the configured unverified role when verification succeeds.

Ticket Types and Staff Access

Ticket types are the choices inside the public dropdown. A good type has a clear name, its own category, and only the roles that are responsible for that kind of request. For example, a Staff Report should not ping or reveal itself to every Support role.

Create the first types

,tcfg quick creates a small common starter set. ,tcfg preset lets you choose a larger starter set. ,tcfg add opens the guided menu to add one type. Run ,tcfg list to see the types currently saved for the server.

Who can see a ticket

Ticket Troubleshooting

When a ticket is closed or deleted, United archives the transcript before removing access or deleting the channel. It logs the transcript and ticket action to the configured destination. If a transcript cannot be saved, close and delete intentionally stop rather than silently losing the conversation.

Welcome and Verification Troubleshooting

Use Dashboard → Welcome for visual editing and testing. Use Discord commands when you are already in the server and need a fast change. The two paths save the same server configuration.

Protection Troubleshooting

Always read the Bot Logs entry first. It records the actor, the detected action, the result, and any Discord permission failure. That is more reliable than guessing from a missing moderation result.

Trusted Protection Roles

Use a trusted role when a whole staff team should bypass United's automatic protection checks. Run ,antinuke_whitelistrole @role to add it and ,antinuke_unwhitelistrole @role to remove it. This applies to Anti-Nuke, Anti-Spam, Anti-Raid, Link Limit, Link Filter, and Scam Trap. Use ,antinuke_whitelist @member when only one person or bot needs the bypass.

Timeout a Member in One Ticket

United has two different ticket timeout modes. A command with only a duration sets the server-wide inactive ticket auto-close setting. A command with a member mention temporarily stops that member from sending messages in the current ticket only. It does not apply a server-wide Discord timeout.

Temporarily Block New Ticket Creation

Use the short ,tblock command when someone should not be able to open any new tickets for a while. It does not close their current ticket, timeout them from Discord, or change any of their roles.