Canonical Facts & Doc Divergences

The docs contradict each other in specific, load-bearing ways. This page is the tie-breaker โ€” the values below are what the current code and live server actually use, verified directly.

โ„น๏ธ Why this page exists

The project accreted multiple CLAUDE.md files, a stale SERVER_REFERENCE.md / VPS_SERVER.md, and design docs written under old names. They disagree on class names, DB name, engine version, service names, and endpoint lists. The reconciled facts are below.

Brief vs. repo

The old brief saidThe repo actually has
"Corrosion / Rate of Decay"Crossworlds BCE โ€” RoD survives only as legacy naming
SQLite persistenceMySQL 8 via a Node REST API โ€” Unity never touches a DB
A* Pathfinding ProUnity built-in NavMesh
DOTween / UniTaskNeither installed โ€” manual lerp/coroutine; UnityWebRequest for HTTP
"Entropy" gear-decayDoes not exist
Six classesFive heroes (a sixth model, Brandalf, is only the Arcanist's preview)

The class name-vs-index tangle (verified)

The index is canonical and immutable. The names diverge between client and server today.

IndexClient name (current code)Server CLASS_NAMES (live)Notes
0MarauderEngineerConstruct/deployable class. Name history: Engineer โ†’ Warden โ†’ Marauder (client)
1TemplarGuardianTank. Renamed client-side from Ironclad โ†’ Templar on 2026-07-31
2Night HunterShadowbladeStealth/burst. Renamed client-side from Shadowblade โ†’ Night Hunter on 2026-07-31
3ClericClericโ€”
4ArcanistArcanistโ€”

Sources verified: client PlayerIdentity.ClassNames and CharacterSelectManager say Marauder/Templar/Night Hunter for indices 0/1/2; live /opt/crossworlds-auth/server.js CLASS_NAMES still says Engineer/Guardian/Shadowblade. Expect those server strings in DB rows until a coordinated client + server + DB migration aligns them.

โš ๏ธ A rename is a coordinated deploy

Aligning indices 0/1/2 to Marauder/Templar/Night Hunter on the server needs a Unity client + server deploy plus DB migrations (UPDATE characters SET class_name='Marauder' WHERE class_index=0, and equivalent for indices 1 and 2). Never renumber the index. See Heroes & Classes.

Service & infrastructure facts (verified live)

FactCanonical (live)Stale sources
Unity version6000.4.11f1Older docs: 6000.4.10f1 / 6000.0.77f1
Auth service / pathcrossworlds-auth, /opt/crossworlds-authVPS_SERVER.md: rod-auth, /opt/rod-auth
Game server servicecrossworlds-server (:7777)Legacy rod-server.service unit still on disk
Dashboardcrossworlds-dashboard โ€” nginx TLS on :4000, Node app on internal 127.0.0.1:4001 (since 2026-07-28)Older docs: plain HTTP directly on :4000
Realtime co-oprod-realtime, Socket.io, :5000RoD is legacy Rate of Decay naming; this companion is distinct from authoritative Mirror/KCP gameplay.
SpacetimeDBspacetimedb, local 127.0.0.1:3500Present and proxied, but not proven to be in the current client/persistence path.
Database name / usercrossworlds / crossworldsSERVER_REFERENCE.md: rod_online / rodgame
Server binaryCrossWords.x86_64 (see Build & Deploy โ€” verified from BuildScript.locationPathName)Older docs/this table previously said CrossworldsBCE.x86_64; also seen: Crossworlds.x86_64 / Portalis.x86_64 / RateOfDecay
XP columnexperienceSome code used xp
Dashboard authMulti-user, DB-backed (dashboard_users table, bcrypt, is_owner flag) since 2026-07-29Was a single shared username/password in .env
Agent Console servicesclaude-agent-bridge (:3020, localhost-only)Not in older docs โ€” see Admin Dashboard
Dev/staging environmentcrossworlds-auth-staging (:3010, open externally โ€” not localhost-only, since the client's Prod/Dev toggle hits it directly) + crossworlds-server-staging (:7778/UDP), own crossworlds_staging DBWas Agent-Console-only and localhost-bound as of 2026-07-29; became the real dev environment 2026-08-02 once the client's ServerConfig.DevAuthPort/DevGamePort were pointed at it. See Login & Authentication Flow and Build & Deploy
โ„น๏ธ Two game-server units exist

The active game server is crossworlds-server.service. A separate legacy rod-server.service also exists (and has been mis-pointed at a non-existent binary in the past). Always confirm which unit you are restarting. See Build & Deploy.

Two quest systems โ€” only the Unity one is live

There are two independent quest implementations in the project, and docs that predate 2026-07-26 only know about the first:

Server API questsUnity-native quests (live)
Where/opt/crossworlds-auth /api/quests/*QuestLocalRuntime + Quest Forge, in the Unity client/server
TransportRESTMirror (via RodChatManager)
PersistenceMySQLIn-memory only (wiped on server restart)
Client consumerNone โ€” no code calls itThe whole game โ€” givers, objectives, rewards
StatusDormant/dead codeTesting-stage, but this is what players use

When any doc or endpoint list implies "quests = /api/quests/*", treat it as stale. The real quest behavior is Quests & Quest Forge. Wiring the two together (persisting Unity quest state via the API) is unbuilt.

Combat: shipped vs. design

The shipped combat is the five-hero spellbook (Atlas, code-derived). COMBAT.md's "nine cores + MoP talents" is a design target, not current code.


Related: Heroes & Classes ยท Database Schema ยท Architecture & Topology ยท Implementation Status ยท Admin Dashboard