GorBot is part of Gor Ultima — the same overall project and ecosystem.
Gor Ultima began as a customized RunUO server built around a persistent Gorean roleplay world. As that world grew, its Discord presence also needed to become more than a simple chat companion. The Discord bot was developed as a plugin and enhancement layer for the RunUO server, helping connect the game world, its players, its roleplay, and its surrounding community.
Over time, that Discord-side system grew into what is now known as GorBot.
Today, GorBot is a major part of the Gor Ultima ecosystem. It supports roleplay, community administration, character and NPC systems, moderation, automation, server onboarding, security, web publishing, multi-node operations, and other services that extend beyond what the game server itself can provide.
The RunUO server provides the game world. GorBot provides the Discord, web, automation, publishing, management, and roleplay systems that help connect that world to the community around it.
The original purpose of GorBot was closely tied to the RunUO server.
It was designed to enhance Gor Ultima by allowing Discord and the game world to work together more closely. That included support for server-side integrations, roleplay tools, community communication, character identity, NPC interaction, administration, and other systems that could extend the experience beyond the game client.
As development continued, GorBot became increasingly important to the roleplay side of Gor Ultima as well.
Players do not spend every moment inside the game client. Roleplay communities live across multiple spaces — in Discord channels, character profiles, persistent NPC records, event systems, server administration tools, shared lore, and community management. GorBot was expanded to support those needs as part of the same Gor Ultima ecosystem.
That evolution turned GorBot from a supporting plugin into a broader platform component.
Gor Ultima — RunUO World The RunUO server provides the persistent game world itself: characters in the shard, combat, exploration, classes, progression systems, crafting, cities, Gorean society, companions, quests, NPCs, and the many systems that make up the in-game experience. | GorBot — Discord & Community Layer GorBot extends that same project into Discord and the web with character profiles, NPC tools, roleplay systems, moderation, automation, dashboards, shared state, community management, and connections back to the game world where appropriate. |
Portal & Admin Gateway The current Portal & Admin Gateway provides the public portal and protected operations gateway for accounts, plans, nodes, data, updates, backups, diagnostics, website management, mail, unified Contact Us routing, canonical Domain & URLs control, and the centralized Redirect Service. Server Premium subscriptions are live through Discord and are administered as Discord-server entitlements rather than player subscriptions. | Website CMS The Website CMS supports normal and source editing, MediaWiki-compatible source syntax, responsive previews, page-title control, revisions, menus, media, SEO, portability, cache-management tools, and domain-portable root-relative links. Official GorBot legal, support, plans, navigation, and documentation content is published directly through this CMS, while selected external or changeable destinations are centralized through the Redirect Service. | DiscordBot / NodeApp The current DiscordBot / NodeApp runtime powers Discord-facing character, NPC, Player Studio, Community Power, moderation, automation, onboarding, command-access security, discovery, utility, roleplay-economy, and community workflows across managed servers. | Data & Deployment The current shared-data schema and release system preserve authoritative state, controlled activation, preflight validation, backups, diagnostics, Redirect Service state, and repeatable deployments without tying the platform to one machine. |
Discord member accounts, server subscriptions, and private CMS staff accounts are deliberately managed as different responsibilities. That separation lets ordinary users access player features while authorized operators and future support personnel receive only the administrative tools their assigned role requires.
GorBot was developed first for the needs of the Gorean community surrounding Gor Ultima.
That remains an important part of its identity. Gorean roleplay, persistent character identity, social structure, NPC systems, and immersive community tools all influenced how GorBot was designed.
However, many of the problems GorBot was solving were not unique to Gorean roleplay.
Other roleplay communities also need persistent characters, flexible profiles, NPC databases, moderation, automation, event tools, server administration, community organization, and ways to manage complex worlds without relying on many disconnected bots.
Because of that, GorBot has expanded to support many kinds of roleplay communities — and even non-roleplay Discord communities looking for a more complete all-in-one platform.
Gorean Roleplay The original foundation. GorBot continues to support the specialized identity, social structures, character systems, NPC tools, and immersive roleplay needs that inspired its creation. | Other Roleplay Worlds Fantasy, science-fiction, modern, historical, tabletop, and custom roleplay communities can use flexible profile templates, custom fields, NPC systems, community tools, and other features without being forced into Gorean terminology. | General Communities Servers that are not focused on roleplay can still make use of GorBot's moderation, administration, automation, role management, announcements, dashboards, and other community-management capabilities. |
Characters, Profiles & Private Notes Players can maintain persistent roleplay identities with flexible profile styles, custom fields, portraits, privacy controls, publishing, import and export tools, and an active-character workflow. Each account can hold up to 150 characters, with the five most recently activated kept close at hand. Personal tools: private Character Notes and an account-scoped Character Speaking Prefix help players organize roleplay and speak as the selected character without changing another player's settings. | NPC Database & Roleplay Identity The shared NPC database supports creation, editing, portraits, browsing, publishing, sharing, cloning, ownership, and staff management. Players can maintain up to 30 NPCs while communities build a reusable cast instead of losing important supporting characters in old chat history. Roleplay continuity: structured NPC records keep names, details, appearance, ownership, and availability consistent across scenes and participants. | Web Dashboard & Personal Tools The dashboard gives players, server owners, and authorized staff a practical way to manage complex features that would be awkward inside a command response. Character libraries, NPC tools, server configuration, roleplay settings, diagnostics, and guided setup share one consistent interface. Designed for continuity: dashboard navigation preserves the user's position while switching sections, reducing unnecessary jumps during longer administrative sessions. |
Roleplay Wallets & Server Economies GorBot's modern Economy engine is scoped to each Discord server. Owners can choose a built-in or Custom / Homebrew economy, define wallet behavior, currencies, denominations, jobs, organizations, treasuries, and supported Premium exchange/activity features without forcing one universal currency model on every community. Flexible by design: players choose only from currencies enabled by their server, balances remain isolated across Discord communities, and detailed guidance is available on the Currency System page. | Moderation, Cases & Cleanup Authorized staff can issue warnings, maintain cases and notes, perform kicks and bans, schedule timed actions, and use controlled message-cleanup tools. The purge command removes a requested number of recent messages when the user has the required authority and Discord permissions. Accountable administration: permissions checks, audit history, moderation exports, and role-aware controls help owners understand who changed what and why. | Automation, Welcome & Community Workflows Communities can configure event-driven automations, welcome and goodbye flows, reaction roles, embed templates, custom commands, timed messages, ticket panels, tracked welcome channels, statistics channels, social alerts, and other repeatable workflows. Flexible triggers and actions: where configured, workflows can react to messages, reactions, buttons, role changes, voice activity, schedules, and other supported Discord events. |
Command Access, Permissions & Security GorBot combines Discord authority with server-specific safeguards. A Blocked Command Role can deny both prefix and application commands even when a member otherwise has elevated bot access, while Command-Silent Channels prevent command use in selected spaces. Security support: Permissions Doctor, Security & Trust tools, feature toggles, protected secrets, and explicit role checks help operators find unsafe or incomplete configurations. | Website CMS & Public Publishing The internal CMS manages public pages, menus, categories, media, search health, system pages, SEO, settings, and portable configuration. Editors can switch between a normal editor and a source editor, use MediaWiki-compatible source syntax, preview desktop, tablet, and mobile layouts, and publish the full revision with one save action. Official GorBot legal, support, plans, navigation, and documentation content is now hosted directly inside this CMS. Compatibility layer: trusted native parsing is used when available, with a safe fallback renderer, title-visibility control, revision history, parser-cache purge tools, root-relative internal navigation, and stable Redirect Service aliases for approved external/changeable destinations. | CMS Accounts & Support-Team Access CMS accounts are intentionally separate from ordinary Discord member accounts. The owner can create additional staff identities and assign focused responsibilities such as platform administrator, CMS manager, publisher, editor, support agent, or auditor without granting everyone full control. Protected access: setup links, mandatory time-based one-time-password authentication, status controls, last-login visibility, and role-based permissions support a future team while preserving owner oversight. |
Cluster, Nodes & Shared State The platform can supervise multiple managed Discord nodes through a centralized control plane. SQL-backed authoritative state, node health, readiness checks, failover support, load sharing, controlled releases, and web-based operations allow GorBot to grow beyond a single process or machine. Safer concurrent work: revision checks and merge-aware configuration flows reduce the risk that one operator silently overwrites another operator's newer changes. | Media, External Storage & Portability Managed media tools support uploads, image handling, reusable assets, and public-page presentation. External Storage Locations provide a control point for storage backends, while CMS portability tools package site content and configuration for safer migration, backup, and recovery work. Operational goal: content and assets remain manageable as the website grows, without forcing editors to alter executable PHP or scatter files across the live server. | Server Discovery & Community Growth Opt-in Server Discovery lets participating communities publish a public server profile and keep it visible through supported activity and bumping tools. It gives roleplay and general communities a built-in path to describe themselves without turning private configuration into public information. Guided onboarding: free onboarding tracking and premium options for private player rooms, access grants, timeout removal, and optional automatic cleanup help new arrivals move through a clear process. |
Backups, Releases, Mail & Diagnostics The Admin Gateway brings configuration backups, release uploads, activation preflight, rollback-aware deployment, platform diagnostics, audit information, administrative mail, and public Contact Us routing into the same protected operating environment. Unified communication: support, billing, bug reports, privacy/security requests, and feature feedback can be routed by category to configured mailboxes through Contact Us. New public feedback no longer depends on a separate Feedback Inbox workflow. Designed for maintainability: releases are validated before live files change, and handoff artifacts preserve the source, deployment context, hashes, and running change history needed by the next operator. |
GorBot does not hide its Gorean origins. They are part of the project's history and continue to influence many of its roleplay-focused systems.
At the same time, the platform is being designed so communities are not forced to use a single setting or vocabulary. Character and NPC profiles can use Gorean, standard roleplay, fantasy, tabletop, modern or science-fiction, and freeform styles, with room for custom information where a predefined format is not enough.
A Gorean server can remain deeply Gorean. A fantasy server can build its own identity. A science-fiction community can use entirely different terminology. A tabletop campaign can structure characters around its own world. A general Discord community can simply use the administrative and community-management tools it needs.
GorBot now uses a unified <a href="/cms-page.php?slug=contact-us" target="_self">Contact Us</a> form for public inbound communication.
Visitors choose the reason that best matches the request, including:
- General Support;
- Billing / Server Premium;
- Account / Login;
- Server Owner Support;
- Economy / Currency;
- Bug Report;
- Feature Suggestion / Feedback;
- Privacy / Data Request;
- Security Concern;
- Abuse / Moderation Concern;
- Legal;
- Copyright / DMCA;
- Other.
The selected reason routes the message to the appropriate configured GorBot mailbox without exposing private mailbox credentials or forcing the visitor to know which email address handles a specific issue.
What happens when a message is submitted
A valid request is checked server-side, routed through the configured mailbox, and uses the visitor's email address as the reply address. A successful submission displays a reference number such as GOR-20260822-ABC123 so the visitor can keep a record of the request.
The form intentionally accepts no file attachments. Public submissions also apply CSRF protection, validation, a hidden bot/honeypot field, browser/network rate limits, bounded field lengths, and a required acknowledgement not to send secrets.
Feedback is part of the same workflow
The older standalone Submit Feedback / Beta Feedback path has been consolidated into:
Contact Us → Feature Suggestion / Feedback
New public feedback is routed by email rather than creating a new entry in the old public Feedback Inbox workflow. Historical feedback records remain available for administrative history/recovery.
Never submit passwords, bot tokens, API keys, database credentials, OAuth secrets, mailbox passwords, recovery codes, or other sensitive credentials through the public form.
Integrated Instead of Fragmented Where practical, GorBot brings related features into one platform so communities do not need to maintain an increasingly complicated collection of unrelated bots, dashboards, and external tools. | Connected to the Game World Because GorBot grew from Gor Ultima, it can participate in a larger ecosystem where Discord, web systems, and the RunUO world can cooperate when game-side integration is appropriate. |
Flexible for Other Communities Features developed for Gor Ultima are increasingly designed so they can also serve communities with entirely different themes, settings, structures, and goals. | Built to Keep Evolving Development continues across roleplay systems, administration, moderation, infrastructure, automation, shared state, web management, publishing, security, and future NPC capabilities while preserving a stable foundation for existing users. |