Moderation
The GorBot Moderation & Administration system is designed to give community owners and trusted staff a connected set of tools for protecting the server, managing members, controlling permissions, configuring roles, and handling day-to-day administrative work.
A healthy Discord community usually needs more than a few isolated punishment commands.
Staff may need to warn a member, clean disruptive messages, apply a temporary restriction, review prior actions, adjust slowmode, manage moderator roles, restore persistent roles, or correct a permissions problem before it causes confusion.
GorBot brings those responsibilities together so communities can rely less on a collection of unrelated moderation bots.
Moderators should be able to act quickly, while server owners retain control over who can manage roles, settings, permissions, and higher-impact community actions.
|
Moderation
Day-to-day community protection: warnings, cleanup, user discipline, mutes, kicks, bans, role-related enforcement, voice moderation, and other actions used to keep channels usable and rules enforceable.
|
Server Administration
Higher-level community management: moderator configuration, roles, server settings, permissions, automation controls, protected server features, and other settings that affect how GorBot operates inside the Discord server.
|
|
Warnings
Staff can use warning-based workflows to document behavior before or alongside stronger disciplinary action.
|
Message Cleanup
Cleanup and purge-style controls help remove spam, repeated content, unwanted links, bot output, attachments, or other disruptive messages when authorized.
|
Mute, Kick & Ban
Trusted staff can temporarily restrict a member, remove them from the server, or prevent them from returning when the situation requires it.
|
|
Softban & Temporary Action
Reversible or temporary enforcement can provide a middle ground when a permanent ban would be excessive.
|
Voice Moderation
Supported voice controls help moderators manage disruptive behavior in voice channels through actions such as deafen and undeafen.
|
Slowmode
Channel-level rate control can reduce spam and help restore order without immediately escalating to user removal.
|
Moderation becomes more consistent when actions have context.
GorBot's moderation model supports the idea that staff should be able to track useful information such as:
- warnings;
- strikes or repeated incidents;
- moderator notes;
- reasons for actions;
- temporary restrictions;
- prior disciplinary state;
- reversal or removal of earlier actions.
This helps staff make decisions based on the member's actual history rather than relying entirely on memory or searching through old Discord messages.
|
Moderator Roles
Server owners can define trusted roles that GorBot recognizes for supported moderation and server-management workflows.
|
Role Editing
Authorized users can manage supported role details such as names, colors, and related settings when Discord permissions allow it.
|
Role Persistence
Selected roles can be remembered and restored when appropriate, allowing important community state to survive a member leaving and later returning.
|
Discord's own permission model remains part of every GorBot moderation action.
Common causes of failed actions include:
- GorBot's highest role being below the role it is expected to manage;
- missing Manage Roles permission;
- missing Manage Messages permission;
- missing Kick Members permission;
- missing Ban Members permission;
- a moderator trying to act beyond their granted authority;
- the target member or role being protected by Discord's hierarchy.
If the target role or member is above GorBot in Discord's hierarchy, Discord itself may refuse the requested action even when the GorBot settings are otherwise correct.
The GorBot Web Dashboard can provide supported moderation and server-administration tools through structured pages.
This is useful for:
- reviewing stored moderation information;
- managing server moderation settings;
- selecting roles from readable dropdowns;
- configuring trusted moderator roles;
- reviewing notes or prior actions;
- managing role-persistence settings;
- configuring community safety features;
- handling longer administrative forms.
The web interface does not bypass Discord permissions. It is simply another way to use authorized GorBot functionality.
Discord remains the natural place for live moderation.
Supported moderation workflows can be exposed through prefix commands, slash commands, buttons, or other Discord-side interactions depending on the feature.
Common moderation categories include:
- clean / purge;
- mute;
- deafen / undeafen;
- kick;
- softban;
- ban / unban;
- warnings;
- members;
- moderation logs;
- role persistence;
- diagnostics;
- slowmode;
- role and moderator management.
The exact available command set can evolve as GorBot continues to improve.
Server-level administration can include configuration for:
- moderator roles;
- moderation behavior;
- role persistence;
- slowmode-related controls;
- supported safety settings;
- Automation;
- role interactions;
- community management features;
- other enabled GorBot systems.
These settings belong to authorized community management rather than ordinary members.
GorBot's moderation system can work alongside Automation for community safety and repetitive enforcement tasks.
Examples of supported or expanding moderation concepts can include:
- restricted word and phrase controls;
- spam reduction;
- rule-based responses;
- automated moderation toggles;
- raid-related protection;
- scam-related protection.
Automated moderation should remain configurable rather than forcing every Discord community to use the same rules.
Where supported, GorBot can preserve moderation information that helps staff understand what happened.
Useful records can include:
- who performed an action;
- when it happened;
- which member was affected;
- the type of moderation action;
- a reason or note;
- earlier warnings or disciplinary history.
This helps communities maintain consistency even when more than one moderator is responsible for handling problems.
|
Members
Use the ordinary community and roleplay features that have been made available to them.
|
Moderators
Handle day-to-day community enforcement within the authority granted by the server owner.
|
Server Owners / Managers
Configure GorBot, define trusted roles, manage server-wide settings, and control higher-level community administration.
|
GorBot separates several important concepts:
- identity — which Discord user is making the request?
- moderator authority — is this user trusted to perform moderation?
- server administration — may this user change server-wide GorBot settings?
- Discord permissions — does Discord itself allow the requested action?
This separation allows the same GorBot system to serve ordinary members, moderators, and server owners without treating them as equivalent.
Gor Ultima and GorBot are part of the same overall project and ecosystem.
The RunUO server provides the persistent game world.
GorBot extends that project into Discord, the Web Dashboard, roleplay profiles, NPC systems, automation, and community management.
Moderation and administration belong to the community side of that ecosystem, helping trusted staff maintain the Discord environment surrounding the roleplay world.
|
Why did a moderation action fail?
Check both GorBot authorization and Discord permissions. Role hierarchy is one of the most common causes of a valid action being refused.
|
Can every moderator change server settings?
No. Routine moderator authority and server-management authority can be kept separate.
|
|
Can moderation be managed from the dashboard?
Supported moderation and server-administration workflows can use the Web Dashboard, while immediate actions can still be performed directly in Discord.
|
Does the dashboard bypass Discord permissions?
No. Web actions still depend on GorBot authorization, Discord permissions, and role hierarchy.
|
|
Can roles be remembered when someone rejoins?
Selected roles can use role-persistence behavior when the server has configured that feature.
|
Are all moderation features identical on every server?
No. Available features and behavior can depend on the GorBot release, server permissions, and which options the community has enabled.
|