Dashboard
The GorBot Web Dashboard gives users and server administrators a dedicated place to manage features that would be difficult, repetitive, or cumbersome to handle entirely through Discord commands.
Discord remains the place where communities gather, roleplay, communicate, moderate, and interact with GorBot. The dashboard complements that experience by moving complex configuration, profile management, detailed forms, administrative tools, and long-form controls into a web interface designed for those tasks.
It exists so users and administrators do not have to force every complex workflow into slash commands, prefix commands, buttons, and temporary Discord forms.
|
User Profiles
Members can work with supported personal and roleplay information through forms that are easier to read and maintain than command-only interfaces.
|
Character Management
The Character Library provides a centralized way to create, browse, edit, and maintain persistent roleplay characters.
|
NPC Management
The NPC Database provides a dedicated interface for creating, editing, cloning, sharing, publishing, and maintaining persistent NPC identities.
|
|
Server Configuration
Server owners and authorized managers can configure supported GorBot features from organized web pages instead of relying only on command syntax.
|
Moderation & Administration
Authorized staff can access supported moderation, role, permissions, configuration, and administrative workflows from a clearer management surface.
|
Automation & Community Tools
Complex automation, announcements, tracked content, roleplay systems, and other community features can be configured more comfortably through dedicated web controls.
|
The user side of the dashboard is intended to keep personal and roleplay tools accessible without exposing administrative controls that do not belong to ordinary members.
Depending on enabled features and permissions, a user-facing dashboard may provide access to:
- Characters & Profiles;
- NPCs owned or managed by the user;
- roleplay-related tools;
- personal profile information;
- supported notifications or account-facing controls;
- public profile and presentation settings;
- community features that have been enabled for normal members.
The goal is to give users useful self-service tools while keeping server administration separate.
Authorized server owners and trusted managers can access additional configuration areas that are not shown to ordinary users.
These controls are intended for tasks such as:
- server-wide GorBot configuration;
- role and permission management;
- moderation settings;
- automation setup;
- tracked content;
- community features;
- server identity and presentation;
- supported roleplay systems;
- diagnostic and management functions where appropriate.
GorBot's dashboard is designed around permissions. A page being available somewhere in the platform does not mean every logged-in user can access or use it.
The Admin Gateway is separate from the ordinary user dashboard.
It provides protected operational management for the GorBot platform and managed node fleet. This includes areas such as:
- cluster overview and health;
- node management;
- shared data state;
- updates and releases;
- backups and rollback;
- diagnostics;
- provisioning;
- website and platform management;
- operational documentation and Primer topics.
These tools are intended for authorized platform administration and are not part of the normal member experience.
|
Discord
Best suited for live conversation, roleplay, commands, moderation actions, notifications, events, reactions, community interaction, and immediate bot responses.
|
Web Dashboard
Best suited for detailed forms, profile editing, settings, management pages, long configuration workflows, browsing stored data, and administrative tasks that benefit from more screen space.
|
The public GorBot dashboard uses Discord OAuth for supported sign-in.
This allows the web layer to associate the logged-in user with their Discord identity and apply the permissions and ownership rules required by supported dashboard features.
Authentication is only the first step. Authorization still determines what the user may actually view or change.
For example:
- a normal user can manage their own supported character information;
- an NPC owner can manage NPCs they own;
- a server owner or authorized manager can access server-management features;
- protected platform administration remains restricted separately.
|
Create, browse, edit, search, and manage persistent roleplay characters through a dedicated interface designed for profile data and long-form editing.
|
Manage NPC profiles, portraits, profile styles, custom fields, cloning, public sharing, and global publishing through an interface better suited to persistent world-building.
|
Certain dashboard features require live communication with the managed GorBot Discord runtime.
The modern GorBot platform uses managed dashboard relay infrastructure so web requests can reach healthy Discord nodes without requiring a public management port on each node.
This allows the dashboard to support live Discord-side actions while preserving the larger high-availability design of the cluster.
The relay system is designed around active shard-owning nodes and healthy standby capacity so live dashboard control can remain responsive without requiring every managed node in a large fleet to poll at the same aggressive rate.
RackNerd SQL acts as the authoritative shared GorBot state for the managed platform.
This is important because GorBot can run across multiple Discord nodes.
For systems such as Characters and NPCs, the web dashboard increasingly reads authoritative shared data directly where appropriate while still routing protected mutations through the application paths that perform ownership, permission, and validation checks.
This helps prevent a user from seeing different stored information simply because two requests were handled by different healthy nodes.
|
Central Control Plane
The RackNerd-hosted web platform remains the central management surface rather than living only on one Discord node.
|
Multiple Managed Nodes
GorBot can distribute Discord Gateway work across multiple siblings with automatic failover and weighted load sharing.
|
Relay Failover
Live dashboard-control requests can use healthy relay nodes instead of assuming one fixed Discord machine will always be available.
|
The modern dashboard has been optimized so pages can request the data relevant to the view being opened instead of forcing unnecessary live-control work across the entire platform.
This is especially important as GorBot grows.
A responsive dashboard needs to remain practical for:
- ordinary users opening profile pages;
- server owners moving between management sections;
- administrators checking live state;
- larger future node fleets;
- roleplay communities with growing Character and NPC collections.
The goal is to keep the interface useful as both the feature set and the number of managed communities increase.
|
Roleplay
Characters, NPCs, profiles, and other roleplay-oriented systems.
|
Community
Server identity, community-facing features, tracked content, and supported engagement tools.
|
Administration
Server-management controls available only to users with the required authority.
|
|
Moderation
Supported moderation, permissions, safety, and staff-management features.
|
Automations
Configurable workflows and event-driven behavior that would be awkward to define through commands alone.
|
Platform Operations
Protected Admin Gateway tools for cluster health, updates, backups, provisioning, diagnostics, and platform maintenance.
|
GorBot separates authentication, ownership, and authorization.
Logging into the dashboard does not automatically grant administrative authority.
Depending on the feature, access may depend on factors such as:
- Discord identity;
- ownership of the record being modified;
- server ownership;
- Bot Commander or other authorized roles;
- administrative permissions;
- protected Admin Gateway access.
Sensitive platform secrets and node credentials are not intended to be exposed through ordinary dashboard pages.
Gor Ultima and GorBot are part of the same overall project and ecosystem.
The RunUO server provides the persistent in-game world. GorBot extends the project into Discord, web-based management, roleplay profiles, NPCs, automation, community administration, and the infrastructure that connects those systems.
The dashboard is the web-facing part of that ecosystem.
It gives the project a place to handle detailed management and persistent information that would not fit naturally inside the game client or Discord command interface.
|
Do I need the dashboard to use GorBot?
Not for every feature. Discord remains a primary interaction surface. The dashboard is used when a feature benefits from more detailed web-based management.
|
Why use the web instead of slash commands?
Complex forms, large profiles, long settings pages, browsing, and administration are easier to manage on a dedicated web page than through a sequence of temporary Discord interactions.
|
|
Can every logged-in user see admin tools?
No. Dashboard access is permission-aware. Administrative and platform-management features remain restricted to authorized users.
|
Where do I manage characters?
Use the Character Library in the GorBot dashboard.
|
|
Where do I manage NPCs?
Use the NPC Database, which provides NPC creation, editing, cloning, portraits, sharing, and publishing tools.
|
Does the dashboard stop working if one Discord node goes offline?
The modern GorBot architecture is designed around a central RackNerd control plane and multiple managed Discord nodes so one node failure does not define the availability of the entire web platform.
|