Dashboard
The GorBot Web Dashboard gives community members, server owners, and authorized staff a dedicated place to manage features that would be difficult or cumbersome to handle entirely through Discord commands.
Discord remains the main place for conversation, roleplay, live moderation, events, notifications, and community interaction.
The dashboard complements Discord by providing larger forms, persistent pages, searchable records, visual controls, profile editors, server settings, and other tools that benefit from more space than a command window can provide.
It gives GorBot a better place for detailed configuration, profile management, roleplay tools, community settings, and other workflows that would otherwise require long sequences of commands or temporary forms.
|
Create, browse, edit, and maintain persistent roleplay characters with flexible profile styles, custom fields, images, and supported presentation controls.
|
Create and maintain NPC profiles, portraits, profile styles, custom fields, cloning, sharing, and global publishing from a dedicated management view.
|
Server Settings
Authorized community managers can configure supported GorBot behavior without relying entirely on command syntax or manually entering Discord IDs.
|
|
Trusted staff can use supported web tools for community moderation, permissions, role management, and server-level administrative workflows.
|
Build and manage configurable workflows through forms that make triggers, roles, channels, actions, and publishing behavior easier to understand.
|
Community Tools
Manage supported announcements, tracked content, role interactions, roleplay tools, and other community-facing features from one web interface.
|
The member-facing dashboard is intended to focus on personal and roleplay features rather than server administration.
Depending on enabled features, a community member may use the dashboard to manage:
- their Characters & Profiles;
- NPCs they own in the NPC Database;
- personal roleplay information;
- profile images and presentation;
- supported privacy choices;
- community features made available to ordinary members.
This creates a self-service area where users can maintain their own information without needing staff to make every change for them.
Server owners and other authorized managers can access additional GorBot configuration appropriate to their Discord community.
Supported server-management areas can include:
- server-wide GorBot settings;
- roles and permission-related configuration;
- moderation settings;
- automation configuration;
- tracked Discord content;
- role-selection systems;
- welcome and community presentation features;
- supported roleplay settings;
- other server-level GorBot features.
The dashboard is permission-aware. A control existing on the website does not mean every logged-in user is allowed to use it.
GorBot uses Discord OAuth for supported dashboard sign-in.
This allows the web application to identify the Discord user and apply the ownership and authorization rules required by dashboard features.
Signing in answers one question:
Who are you?
GorBot then separately determines:
- which records you own;
- which servers you can manage;
- whether you have an authorized staff role;
- which features the server has enabled;
- what actions you are permitted to perform.
Logging in does not automatically grant moderation or server-management authority.
|
Discord
Live conversation, roleplay, commands, reactions, notifications, moderation actions, community events, and immediate interaction with GorBot.
|
Web Dashboard
Detailed forms, stored profiles, configuration pages, searches, browsing, long-form editing, role selectors, and other tasks that benefit from more screen space.
|
The Character Library is one of the dashboard's primary roleplay tools.
It allows a user to work with their stored characters through a persistent web interface instead of recreating profile information through Discord every time.
Supported character workflows include:
- creating characters;
- browsing existing characters;
- searching stored profiles;
- editing character information;
- changing profile styles;
- maintaining custom fields;
- managing supported images and presentation;
- returning to older characters when they become relevant again.
The library is designed to remain practical even for users with large character collections.
The NPC Database provides dashboard tools for persistent non-player identities.
Supported workflows include:
- creating NPCs;
- editing owned NPCs;
- changing profile styles;
- maintaining custom fields;
- managing portraits;
- cloning NPC records;
- sharing supported public profiles;
- publishing eligible NPCs to the broader global listing.
The dashboard gives these long-lived world identities a place to be maintained as roleplay develops.
The Automation dashboard is designed to make event-driven workflows easier to configure.
Instead of relying on long command syntax, supported workflows can present clear controls for:
- trigger selection;
- channels;
- roles;
- user-facing content;
- actions;
- enabled or disabled state;
- publishing behavior.
Role selectors can use actual server roles where supported, reducing the need for administrators to manually copy Discord role IDs.
GorBot supports tracked published content for selected dashboard-managed features.
When content is tracked, GorBot remembers the Discord message associated with that configuration.
Later dashboard changes can update that same message instead of always posting another copy.
This is useful for:
- persistent information panels;
- role-selection messages;
- community notices;
- automation controls;
- other long-lived dashboard-managed Discord content.
If a tracked message is no longer available, supported workflows can recreate it and establish tracking again.
For supported dashboard features, GorBot can separate configuration from publication.
This allows workflows such as:
- Save — preserve the configuration;
- Save & Publish — preserve the configuration and publish the supported Discord result;
- Unpublish — remove or disable the published presentation where supported;
- edit and republish — update an existing published configuration.
This gives server managers more control over when changes become visible to members.
Supported Moderation & Administration tools can use the dashboard when a web interface provides better context than a command.
Examples can include:
- server moderation settings;
- role configuration;
- trusted moderator settings;
- permissions-related configuration;
- reviewing stored moderation information;
- longer forms and notes;
- community safety settings.
Immediate moderation actions can still remain available inside Discord where staff are actively working.
GorBot separates authentication from authorization.
A user may be signed in successfully but still be unable to perform an action because they do not own the record, do not manage the server, or do not have the required Discord authority.
Dashboard actions can depend on factors such as:
- Discord identity;
- ownership of the character or NPC;
- server ownership;
- trusted management roles;
- enabled features;
- Discord permissions;
- Discord role hierarchy.
A web button does not give GorBot powers that Discord itself has not granted.
GorBot uses shared authoritative state for persistent platform data.
This is important because the Discord service can run across multiple managed nodes.
Information such as character profiles, NPC records, community configuration, and other supported persistent state can remain consistent across the platform rather than becoming isolated copies tied to individual machines.
The result is a dashboard that can continue presenting the same stored community information even as Discord work moves between healthy nodes.
GorBot's web services are hosted independently from individual managed Discord nodes.
This allows the dashboard and persistent web-facing information to remain separate from the health of one specific Discord machine.
The Discord side can use multiple managed nodes, shared state, failover, and load sharing while the web interface continues to provide a consistent place for users and server managers to work.
For more information about the underlying architecture, see Reliable Infrastructure.
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, roleplay profiles, NPCs, automation, moderation, and community management.
The dashboard is the web-facing part of that ecosystem, providing space for the detailed management and persistent information that does not fit naturally inside the game client or a Discord command.
|
Do I need the dashboard to use GorBot?
Not for every feature. Discord remains a primary interaction surface. The dashboard is used where a feature benefits from detailed web-based management.
|
Why use the web instead of commands?
Profiles, settings, role selectors, long forms, searches, and configuration pages are easier to manage with a persistent web interface than through a sequence of temporary Discord interactions.
|
|
Can every signed-in user see server-management tools?
No. Access depends on ownership, Discord identity, server authority, enabled features, and the permissions required by the feature.
|
Where do I manage my characters?
Use the Character Library in the GorBot dashboard.
|
|
Where do I manage NPCs?
Use the NPC Database, which provides creation, editing, cloning, portrait, sharing, and publishing tools.
|
Does the dashboard bypass Discord permissions?
No. Dashboard actions still respect GorBot authorization, ownership rules, Discord permissions, and role hierarchy.
|