About United

United is an independently developed Discord bot for server protection, moderation, support tickets, logging, and owner control. It is maintained by Reno and offered free with help from the community.

Why United exists

United began from a practical problem: running a Discord server often means combining separate bots for moderation, anti-nuke protection, tickets, welcome messages, roles, transcripts, and dashboards. Those systems can disagree about permissions, duplicate logs, create overlapping channels, or make an owner search several interfaces during an incident.

The project is built around one shared configuration per server and one understandable record of what happened. A ticket role selected in the dashboard should be the role used by the ticket channel. A renamed log channel should remain valid because its Discord ID did not change. A moderation command and the resulting Discord event should produce one normalized record rather than three nearly identical embeds.

Who maintains the project

United is designed, developed, and operated by Reno, known on Discord as theonlyrenoez. There is not a large company behind the service. That independence allows user reports to turn directly into code changes, but it also means documentation must be honest about support capacity and technical limits.

How changes are handled

United uses a startup preflight before launch. The preflight compiles Python source, checks required dependencies and configuration, validates the PostgreSQL connection and prepared runtime queries, confirms protection schemas, and runs the automated test suite. Dashboard changes also receive browser layout checks at desktop and mobile sizes. Secret-free source archives are created for rollback, while runtime database backups are handled separately.

High-risk systems are designed to be idempotent. Running setup or repair again should reuse valid Discord resources. Event pipelines order security checks before ordinary feature handling, and persistent job records are used where a restart could otherwise forget long-running work.

What United is designed to do

• Give server owners a clear starting configuration without forcing dozens of channels.
• Make protection outcomes attributable and reviewable.
• Keep ticket access specific to the people responsible for each request type.
• Follow Discord permissions instead of creating a second hidden permission system.
• Store operational settings so normal restarts do not break controls or timers.
• Provide enough public documentation that owners understand a setting before enabling it.

What United cannot promise

No Discord bot can guarantee that every raid, compromised account, malicious administrator, API outage, or Discord permission conflict will be detected or reversed. United depends on Discord gateway events, audit logs, API availability, granted permissions, role hierarchy, and the configuration chosen by each server. Security features reduce risk; they do not replace trusted staff, careful permissions, and server backups.

Community direction

Server owners and members can send product ideas with ,suggest, ,suggestion, or the server-owner dashboard. Suggestions are saved to a private owner inbox and delivered to the developer. Bug reports are most useful when they include the server, command or dashboard tab, expected behavior, actual result, and relevant United log entry.