United Features

United combines the systems a Discord server normally spreads across several bots. The goal is not to collect the longest feature list. It is to make protection, moderation, tickets, member access, and recovery behave like one understandable system.

Protection that explains its decisions

Anti-Nuke watches destructive Discord changes such as repeated channel or role deletion, suspicious bans and kicks, dangerous permission changes, webhook activity, and unauthorized bot additions. United checks Discord audit logs to identify the actor, verifies its own role hierarchy, then applies the server's configured response. The resulting Bot Logs entry records what was detected, who Discord attributed it to, what United attempted, and whether Discord accepted the action.

Anti-Raid handles the member-join side of server security. It can watch mass joins, very new accounts, bots, missing profile pictures, and account-age requirements. Anti-Spam handles repeated messages, fast floods, duplicate content, excessive mentions, and configured @everyone or @here bursts. Link Limit focuses on repeated Discord invite links, while Scam Trap provides a clearly marked decoy channel where any message can trigger the selected response.

Moderation with one consistent record

United supports bans, kicks, timeouts, warnings, purge operations, mute and jail workflows, role stripping, unjail and role restoration, slow mode, and member lookup. Commands accept a Discord mention or a plain user ID where a member target is expected. Native Discord actions are also logged by checking the audit log, so a timeout applied through Discord's member menu can produce the same style of record as a timeout command.

Moderation logs are deduplicated before delivery. A command response in the channel is not supposed to become a second or third moderation log. The event record identifies the target, moderator, reason, duration when relevant, and action source.

A ticket desk, not just private channels

Each ticket type stores its own destination category, staff roles, optional questions, and public panel label. That means a Staff Report can be visible only to senior staff while General Support reaches the support team. Discord administrators retain their native administrator access, but unrelated staff roles are not added merely because they can work another ticket type.

Tickets include persistent controls for claim, unclaim, close, reopen, transcript, rename, member and role access, member-specific ticket timeouts, and temporary blocks on opening new tickets. Closing or deleting a ticket attempts to save its transcript before removing access or deleting the channel. Ticket panels and open-ticket controls are restored after a normal bot restart.

Logs that start simple and split only when useful

Every server starts with one Bot Logs destination. Moderation, protection, member, channel, role, configuration, and ticket activity can all use that channel. Owners who need separation can route individual event groups such as bans and kicks, Anti-Nuke, Anti-Spam, voice joins and leaves, or ticket transcripts to dedicated channels. An override is optional; removing it returns that event to Bot Logs.

Server-owner control without bot-owner exposure

The server-owner dashboard uses Discord OAuth. A signed-in owner sees servers they own or servers where they were explicitly granted dashboard access. Controls then follow the person's Discord permissions. The private bot-owner dashboard contains operational tools, project health, all-server risk summaries, and bot-wide settings that ordinary server owners never receive.

Dashboard changes can be written to a private action history and, when enabled, posted in the server's configured Bot Logs channel. This lets owners answer who changed a protection setting, which server was affected, and what the old and new values were.

Repair that checks before it creates

United's repair tools compare saved IDs with the live Discord server and search for valid existing resources. Renaming a channel should not make it invalid because its Discord ID remains the same. A ticket panel should be refreshed when its wording changes and rebuilt only when the saved panel is genuinely missing. Incident restoration recreates missing structure or repairs altered permissions without deleting unrelated channels added after the snapshot.