Moderation
The GorBot Moderation & Administration systems are designed to give community owners and trusted staff a connected set of tools for managing users, roles, permissions, server behavior, moderation actions, and administrative workflows.
A healthy community usually needs more than a ban command.
Staff may need to warn a member, remove a disruptive user, review prior actions, adjust slowmode, clean problem messages, manage moderator roles, enforce role persistence, review server configuration, or correct a permissions problem before it becomes a larger issue.
GorBot is built to bring those responsibilities together instead of scattering them across unrelated bots and disconnected configuration systems.
Moderation tools should help trusted staff act quickly while still respecting ownership, permissions, auditability, and the difference between ordinary moderation and higher-level server administration.
|
Moderation
Day-to-day community protection: warnings, message cleanup, user discipline, mutes, kicks, bans, role-related enforcement, and other actions used to keep channels usable and community rules enforceable.
|
Administration
Higher-level server control: permissions, moderator configuration, roles, server settings, protected features, policy decisions, diagnostics, and other actions that can affect the wider community.
|
|
Warnings & Discipline
Moderation workflows can support warnings, strike-style tracking, notes, and escalating action so staff have more context than a single isolated punishment.
|
Message Cleanup
Cleanup and purge-style controls can help remove spam, repeated content, links, attachments, bot output, or other unwanted messages from a channel when authorized.
|
Mute, Kick & Ban
Trusted staff can use supported disciplinary actions to temporarily restrict a user, remove them from the server, or prevent them from returning.
|
|
Softban & Timed Actions
Where enabled, moderation can include temporary or reversible enforcement options that are more appropriate than a permanent ban for every situation.
|
Voice Moderation
Supported voice controls can help staff manage disruptive users in voice channels through actions such as deafen and undeafen.
|
Slowmode & Channel Control
Channel-level controls can help staff reduce spam and restore order without immediately escalating to user removal.
|
|
Moderator Roles
Server owners can define or manage the trusted roles that GorBot should recognize for supported moderation and management workflows.
|
Role Management
Authorized administrators can create, rename, recolor, delete, or otherwise manage supported Discord roles through GorBot where the bot has the required Discord permissions.
|
Server Configuration
Administrative settings let server owners control which GorBot systems are enabled, how they behave, and which roles or users are allowed to manage them.
|
|
Permissions
Permissions determine whether a feature can actually work. GorBot administration includes tools and diagnostics intended to help owners understand when Discord role hierarchy or missing permissions block an action.
|
Automation Control
Administrative users can manage supported automation behavior so server actions and workflows are intentional rather than being uncontrolled bot behavior.
|
Protected Actions
Destructive or high-impact actions can be kept behind stronger authorization so ordinary moderators do not automatically receive every owner-level capability.
|
Discord role hierarchy and permissions remain part of every moderation system.
Examples of common problems include:
- GorBot's role being below the role it is expected to manage;
- missing Manage Roles permission;
- missing Ban Members or Kick Members permission;
- missing Manage Messages permission;
- a moderator attempting an action beyond their own authority;
- a protected owner-only action being attempted by ordinary staff.
GorBot's administration direction includes permissions diagnostics so problems can be explained in practical terms instead of appearing only as a generic failure.
If the target role or user is above GorBot in Discord's role hierarchy, Discord itself may refuse the requested action even when the GorBot configuration is otherwise correct.
GorBot's web dashboard is intended to expose appropriate moderation and administration controls through structured pages.
This is useful for:
- reviewing users and stored moderation information;
- managing server settings;
- selecting roles from dropdowns instead of typing IDs;
- configuring moderation behavior;
- viewing notes and history;
- managing larger feature sets;
- performing administrative actions with clearer context.
The dashboard does not bypass Discord permissions or GorBot authorization. It is another interface into the same protected management model.
Discord remains the natural place for immediate moderation.
Supported moderation workflows can be exposed through prefix commands, slash commands, buttons, or other Discord-side interactions depending on the feature.
Typical moderation categories include:
- clean / purge;
- mute or voice restriction;
- kick;
- softban;
- ban / unban;
- warnings;
- member lookup;
- moderation logs;
- role persistence;
- diagnostics;
- slowmode;
- role and moderator management.
The exact command set may evolve between releases as GorBot's moderation suite continues to expand.
A connected moderation system can preserve more context than a simple ban list.
GorBot's moderation direction includes support for concepts such as:
- warnings;
- strike tracking;
- moderator notes;
- reasons;
- timed restrictions;
- clearing or reversing actions;
- reviewing prior moderation state.
This gives trusted staff a more consistent way to respond to repeated behavior and helps prevent moderation decisions from depending entirely on one person's memory.
GorBot's wider administration model is designed around auditability.
Where supported, moderation and management history can help identify:
- who performed an action;
- when it occurred;
- which server it affected;
- what type of action occurred;
- which interface or subsystem initiated it;
- the target of the action.
This becomes increasingly important as moderation can occur from Discord commands, the web dashboard, automation systems, or protected administrative surfaces.
Supported role persistence allows selected role assignments to be remembered and restored when appropriate.
This can be useful for:
- community identity roles;
- verified-member roles;
- access roles;
- moderation-related restrictions;
- persistent participation state.
Role persistence should be configured carefully. A role being persistent is a deliberate server policy choice, not something every Discord role should automatically inherit.
GorBot's moderation platform is being developed to support automated safeguards alongside human moderation.
These can include areas such as:
- restricted words or phrases;
- anti-spam behavior;
- anti-raid protections;
- anti-scam protections;
- automated moderation toggles;
- rule-based responses.
Automated enforcement should remain configurable by authorized server management rather than being imposed identically on every community.
Certain destructive operations should be treated differently from ordinary actions.
Examples include:
- permanent record deletion;
- destructive configuration changes;
- high-impact role removal;
- privileged server-management actions;
- protected platform-level changes.
GorBot's design separates these from routine moderation where practical so that higher-impact actions can remain restricted to the appropriate administrative surface or authority level.
For example, some permanent deletion workflows may be intentionally limited to protected administrative interfaces rather than ordinary moderator commands.
|
Members
Use normal community and roleplay features available to them.
|
Moderators
Handle day-to-day enforcement and community protection within the authority granted to them.
|
Server Owners / Managers
Configure GorBot, define trusted roles, manage protected server settings, and perform higher-level administration.
|
Platform Administration
Protected GorBot operational access such as the Admin Gateway, cluster management, updates, backups, and infrastructure controls.
|
GorBot separates several concepts that are often confused:
- authentication — who is this user?
- ownership — does this user own the record?
- moderator authority — is this user trusted to perform staff actions?
- server administration — may this user change server-wide configuration?
- platform administration — may this user control GorBot infrastructure itself?
This layered model allows the same connected system to serve ordinary users, moderators, server owners, and platform administrators without treating them as equivalent.
Gor Ultima and GorBot are part of the same larger project.
The RunUO side manages the persistent game world. GorBot extends that ecosystem into Discord, the web dashboard, roleplay profiles, NPC systems, automation, and community administration.
Moderation and administration belong primarily to the community-management side of that ecosystem, giving trusted staff tools to protect the Discord community and manage the systems surrounding the roleplay environment.
|
Why did a moderation action fail?
Check both GorBot authorization and Discord permissions. Role hierarchy is a common reason a valid action is refused.
|
Can every moderator change server settings?
No. Routine moderator authority and server-owner/manager authority are separate concepts.
|
|
Can I manage moderation from the dashboard?
Supported moderation and administration workflows can be exposed through the Web Dashboard, while immediate actions can still be performed from Discord.
|
Does the dashboard bypass Discord permissions?
No. The web interface does not give GorBot powers that Discord itself has not granted.
|
|
Are all advanced moderation features live now?
No. GorBot's moderation suite continues to expand. Availability can vary by release, server configuration, and whether a feature is still under development.
|
What is the Admin Gateway?
It is a protected platform-administration surface for GorBot infrastructure and is separate from normal server moderation.
|