Crossworlds BCE β Project Wiki
- 2026-08-08 β Wiki audit: colliding topic pairs were classified into current references and preserved historical snapshots; no documentation was deleted. The site builder now gives historical pages stable archive URLs, renders wrapped list items correctly, and supports links to heading anchors. See Wiki Governance & Audit.
- 2026-08-08 β MuffinCore service-context audit: every service/database node now explains architectural purpose, dependencies, and caveats.
ROD Realtimeis explicitly identified as legacy Rate of Decay naming and distinguished from the Unity/Mirror game server. See Bot Fleet & VPS Operations β Brain map service-context audit. - 2026-08-08 β Developer intent review: 2,138 visible messages across all 43 text-capable channels in Crossworlds (DEVELOPER) distilled into Developer Intent & Game Direction. The page records conclusions, confidence, settled decisions, and open questionsβnot conversations.
- 2026-08-08 β Live bot/VPS audit: ten bot instances verified, Dennis confirmed staged but inactive, service/port/firewall reality reconciled, and security/operations follow-ups recorded in Bot Fleet & VPS Operations.
- 2026-08-08 β Deep history/context audit: all 705 reachable Git commits and 1,330 accessible MuffinDev Discord messages reviewed. Durable rationale, accepted decisions, reversals, playtest reports, bot requirements, and open verification work are consolidated in Historical Context & Decision Register.
- 2026-08-05β07 β Multi-character API shape agreed in Discord (implementation still requires verification); downloadable Windows clients are built through the BCE Unity menu and published through the admin portal. See Historical Context & Decision Register.
- 2026-07-29 β Admin dashboard: browser build upload (zip β auto-extract/chmod into the live run dir) and a misc-files section added to the Deploy tab; multi-user accounts replacing the single shared login (
dashboard_userstable, bcrypt, per-userlast_login); Agent Console and Agent Audit Log restricted to the owner account. New Admin Dashboard page covers all of it. - 2026-07-28 β Agent Console shipped in the admin dashboard: a locked-down AI ops agent (read-only diagnostics; approval-gated service restarts and staging-DB writes; full audit log). Dashboard login moved off HTTP Basic Auth to a real session-cookie page, now served over HTTPS. See Admin Dashboard.
- 2026-07-28 β Discord bot renamed MuffinDev β Help (
Help#8358); tuned to favor answering over riffing; live in a second Discord server, restricted to#helpdesk, mention-only (no unprompted auto-replies). See Help Bot. - 2026-07-28 β Helpdesk ticket system launched: Help opens a ticket automatically when it can't answer, or on request; also submittable from the playcrossworlds.com homepage widget. Tracked in a new Tickets tab on the admin dashboard.
- 2026-07-27 β Wiki content pass: 4 new pages (Quests & Quest Forge, Visual Effects & VFX Pipeline, Player Movement/Camera & Controls, Development History & Timeline) plus refreshes across several existing pages.
- 2026-07-27 β Fixed a dashboard bug that showed the game server as falsely "down" (was checking a nonexistent systemd unit name) and a broken homepage feedback form.
A factual snapshot of the project as it stands in the current build β the version in front of us, not a plan. Where source docs disagree, this wiki follows what the code and the live server actually do and records the conflict in Canonical Facts & Doc Divergences.
Crossworlds BCE is a co-op dark-fantasy action RPG for a small crew of friends β a Unity 6 client and self-hosted dedicated server, with persistence handled by a Node/Express API over MySQL.
"RoD" / "Rate of Decay" survives only as legacy naming (Rod* script prefixes, the rod-realtime service, an old rod-server unit file). The current project is Crossworlds BCE. The old brief's "Corrosion / Entropy gear-decay / SQLite / A* / UniTask / six classes" describe systems that do not exist in this repo.
The stack at a glance (live)
| Layer | What it is |
|---|---|
| Client + dedicated server | Unity 6000.4.11f1, URP, Mirror over KCP (UDP 7777) |
| Auth / game API | Node.js + Express β crossworlds-auth service, port 3000, /opt/crossworlds-auth/server.js |
| Admin dashboard | crossworlds-dashboard service β nginx TLS on :4000, Node app internal on :4001; multi-user login |
| Realtime co-op | rod-realtime (Socket.io) service, port 5000 |
| Database | MySQL 8, DB crossworlds (user crossworlds) |
| SpacetimeDB | spacetimedb service, local 127.0.0.1:3500 β present, not wired into the documented client flow |
| Monitoring | Uptime Kuma, port 3001 |
| Web / delivery | Nginx, playcrossworlds.com (IP 15.204.243.36) |
Authority is split across two servers: the Unity/Mirror game server (crossworlds-server) is authoritative for real-time state (enemies, waves, boss phases, ability effects, chat, positions), while the Node API is authoritative for persistence β accounts, characters, inventory, progression, crafting, and kill-reward validation.
Contents
Foundations
Networking
- Mirror Networking & Discipline
- Login & Authentication Flow
- Zones, Scenes & Multi-Zone
- Waypoints, Portals & Travel
- Party System
Backend & Data
Combat
- Combat Core and Loop
- Heroes and Classes
- Ability Atlas and Synergies
- Combat Design Bible
- Enemies, Waves and Bosses
- Progression & Hero Mastery
Content & UI
- Getting Started & How to Play
- Loot, Inventory and Crafting
- Gathering & Professions
- NPCs & Interaction
- Quests & Quest Forge
- Mounts & Traversal
- Player Movement, Camera & Controls
- Audio, Music & Game Feel
- Visual Effects & VFX Pipeline
- UI & HUD Systems
- GM Console and Tools
Process
- Build & Deploy
- Bot Fleet & VPS Operations
- Admin Dashboard
- Editor Tooling
- Implementation Status
- Known Issues & Tech Debt
Reference
- Wiki Governance & Audit
- Tech Stack & Versions
- Canonical Facts & Doc Divergences
- Development History & Timeline
- Historical Context & Decision Register
- Developer Intent & Game Direction
Where to start
- New player? Getting Started & How to Play β logging in, picking a class, controls.
- New to the codebase? Architecture & Topology β Mirror Networking & Discipline.
- Working on combat? Combat Core and Loop β Heroes and Classes β Ability Atlas and Synergies.
- Backend / API? Auth & Game API and Database Schema.
- What actually works right now? Implementation Status and Known Issues & Tech Debt.
- Running/servicing the live server day-to-day? Admin Dashboard β services, deploys, GM tools, helpdesk, and the approval-gated Agent Console.
- How did it get here? Development History & Timeline β the build's evolution, milestone by milestone.
- Why is it built this way / what did the team decide? Historical Context & Decision Register.
- What game are the developers trying to make? Developer Intent & Game Direction.
- Confused by conflicting docs? Canonical Facts & Doc Divergences is the tie-breaker.