Automations
The GorBot Automation System is designed to reduce repetitive work by allowing supported Discord events to trigger predefined community actions.
Instead of requiring a moderator or server owner to manually repeat the same process every time something happens, an automation can watch for a supported event and respond according to the workflow configured for the server.
Automations can support administrative work, community engagement, role management, announcements, roleplay systems, and other recurring server behavior.
GorBot's automation model is intended to let authorized server managers decide what should happen, when it should happen, and which parts of the community the workflow is allowed to affect.
|
Trigger
The event that begins the workflow. A trigger represents something GorBot can detect, such as activity in a channel, a role change, a reaction, a voice event, or an interaction with an automation control.
|
Action
The configured response. Depending on the supported workflow, GorBot can use that event to perform a community action, send information, adjust a role-related state, or continue another automated process.
|
GorBot's automation foundation has been designed around multiple Discord event categories. Supported or developing workflow triggers include events such as:
|
Message Activity
Workflows can react to supported message events such as messages being created, edited, or removed.
|
Reactions & Interactions
Reaction activity and supported automation-button interactions can provide direct user-driven triggers for a workflow.
|
Role Changes
Supported workflows can respond when members gain or lose roles, allowing role state to participate in broader community automation.
|
|
Voice Events
Voice-channel activity can be used as a workflow signal where supported, allowing a community to react to members joining or changing voice state.
|
Community Events
GorBot can continue expanding automation around other server events as additional systems become part of the connected platform.
|
Roleplay Events
Because GorBot also contains roleplay systems, future and specialized workflows can connect community automation with roleplay-oriented features where appropriate.
|
|
Member Onboarding
Guide new members toward channels, information, roles, or other server resources as part of a repeatable arrival workflow.
|
Role Workflows
Respond to role-related events or supported user interactions so access, notifications, or community state can be managed more consistently.
|
Announcements
Use supported events to produce repeatable messages or notifications without requiring staff to manually post the same information every time.
|
|
Moderation Assistance
Automation can support Moderation & Administration by helping respond to predictable conditions, while protected enforcement remains subject to the server's configured permissions and policies.
|
Roleplay Support
Roleplay communities can use automation to support event notices, participation workflows, scene-related activity, roles, reminders, and other recurring roleplay administration.
|
Community Engagement
Automated responses can make server activity feel more connected by reacting consistently to supported community actions and events.
|
The GorBot Web Dashboard provides the natural management surface for automation.
Instead of requiring server owners to remember long command syntax, a dashboard editor can present the workflow as a set of visible choices.
Depending on the workflow, configuration can include:
- automation name or purpose;
- trigger type;
- target channels;
- roles;
- user-facing content;
- workflow actions;
- enabled or disabled state;
- publishing state;
- other conditions supported by that automation type.
Role-selection controls are intended to use clear Discord role selectors where practical so administrators do not need to manually copy role IDs for normal setup.
GorBot's dashboard direction separates editing from live publication where appropriate.
This supports workflows such as:
- Save — preserve configuration without necessarily making a new live publication;
- Save & Publish — save the configuration and push the supported live result;
- Unpublish — remove or disable a published presentation where that workflow supports publication;
- edit and republish — update an existing live workflow without rebuilding it from the beginning.
This model is especially useful for automations that create or maintain a visible Discord message, button, role selection, or other published community interaction.
GorBot includes a tracked-content foundation that allows supported published Discord content to remember the message it belongs to.
When tracked content is edited later, GorBot can update the existing Discord message instead of automatically creating another copy.
This is useful for long-lived community content such as:
- role-selection messages;
- information panels;
- persistent announcements;
- automation controls;
- other dashboard-managed Discord messages.
If a tracked message no longer exists, supported workflows can recreate and re-track it instead of leaving the configuration permanently broken.
Role interaction systems are a natural example of GorBot automation.
A server can present members with supported buttons, reactions, or dropdown-style choices and use those interactions to manage Discord roles according to server configuration.
This can support:
- notification roles;
- interest groups;
- roleplay roles;
- access categories;
- opt-in community groups;
- event participation;
- self-service server organization.
These workflows still depend on Discord permissions and role hierarchy. GorBot cannot assign or remove a role that Discord itself prevents the bot from managing.
Some automations can be designed around direct member interaction.
An automation button can act as a deliberate trigger: a member clicks the control, GorBot receives the event, verifies the relevant workflow, and performs the configured response.
This gives communities a way to create guided self-service interactions without requiring members to learn command syntax.
Interactive workflows can be especially useful for:
- role selection;
- sign-ups;
- acknowledgements;
- guided community actions;
- roleplay participation;
- simple workflow choices.
|
Events
Roleplay-event systems can use automation concepts for notices, participation, reminders, recurring events, and other organizational work surrounding a live roleplay event.
|
Scenes
Scene-management features can benefit from automated joins, leaves, notices, archival steps, or other recurring scene administration as those systems continue to evolve.
|
Roleplay Identity
Automation can eventually work alongside Characters & Profiles and NPCs where a workflow needs to react to roleplay-oriented community state.
|
Automation can support Moderation & Administration, particularly for predictable or repetitive server conditions.
However, moderation automation should remain controlled by authorized server management.
Areas of continuing GorBot development include concepts such as:
- restricted word and phrase enforcement;
- anti-spam behavior;
- automated moderation toggles;
- anti-raid systems;
- anti-scam systems;
- rule-based moderation responses.
Every automation still operates inside Discord's permission model and GorBot's authorization rules.
For example:
- a role automation cannot manage a role above GorBot in the Discord hierarchy;
- a workflow cannot perform a Discord action for which the bot lacks permission;
- administrative automation controls should remain restricted to authorized server management;
- protected actions should not become unrestricted simply because they can be triggered automatically.
Automation changes how an action starts. It does not remove the security rules around the action itself.
Before publishing an automation, consider:
- who can trigger it;
- how often it can run;
- which channels it affects;
- which roles it can change;
- whether the action is reversible;
- whether the result could create spam;
- whether the workflow has enough permission checks;
- whether a destructive action should remain manual instead.
High-impact and destructive workflows should receive stronger protection than ordinary community conveniences.
GorBot's larger administration direction includes global audit concepts that can distinguish where important actions originated.
Automation is one of those possible sources.
A useful audit trail can help identify:
- the server;
- the action;
- the affected object or user;
- when it occurred;
- whether it came from the dashboard, Discord, an automation, or another supported subsystem.
The exact audit surface continues to evolve, but automation is being treated as part of the same accountable administrative environment rather than as an invisible side system.
Gor Ultima and GorBot are part of the same overall project and ecosystem.
The RunUO side provides the persistent game world. GorBot extends that project into Discord, the web dashboard, roleplay profiles, NPCs, moderation, community management, and automation.
Most Discord automation belongs to the GorBot community layer.
Where future game-side integration is appropriate, carefully designed workflows may also participate in the broader ecosystem without treating the RunUO server itself as a GorBot Discord node.
|
What is an automation?
A rule that watches for a supported trigger and performs a configured response when that trigger occurs.
|
Where do I configure automations?
Supported workflows are managed through the Web Dashboard, where the trigger, actions, roles, channels, and other settings can be presented as a structured editor.
|
|
Can an automation assign roles?
Supported role workflows can manage roles, but GorBot must still have the required Discord permissions and role hierarchy position.
|
Can I edit something before publishing it?
Where the workflow supports publication, GorBot's dashboard direction includes separate save and publish behavior so configuration can be prepared before it becomes live.
|
|
Will editing tracked content create another Discord message?
Tracked-content workflows are designed to update the existing published message when possible instead of creating unnecessary duplicates.
|
Are all planned automation types available now?
No. The automation platform continues to expand. Availability depends on the current GorBot release, the workflow type, and the features enabled for the server.
|