Development status
What exists today, stated plainly
No player counts, no uptime charts and no fictional statistics. This page reports the capabilities present in the repository and the ones that are not built, and is updated as the work lands.
Why there are no live figures here
A status page showing invented player counts would be worse than no status page. When a public server exists, this page will report real availability from the platform itself.
Game framework
Game framework: capability report
Each row states what is present and what a member would actually be able to do.
Persistent accounts and characters
AvailableAccount and character lifecycle with ownership validation, approval state and persistent identity.
Game sessions and state persistence
AvailableLease-based sessions, heartbeats, atomic position persistence and reconnect handling.
Local text roleplay
AvailableLocal in-character chat, /me and /do actions, local out-of-character clarification, with proximity and rate validation on the server.
Permissions and audit events
AvailableRole and permission checks with recorded audit events for sensitive operations.
Employment and the economy
Not implementedDesigned, not implemented. No wages, prices or ledger operations exist yet.
Property and vehicle ownership
Not implementedDatabase structures exist; the ownership services and the flows a player would use do not.
World simulation
Not implementedWeather, time policy, scheduled events and supply and demand are planned.
Website and portal
Website and portal: capability report
Each row states what is present and what a member would actually be able to do.
Public website and information pages
AvailableThis site: about, philosophy, rules, getting started, roadmap, FAQ, staff, contact, status and legal pages.
Portal sign-in and registration
PartialThe website implements the full boundary — session cookie handling, validation, error surfaces — against a backend contract that does not exist yet. Development builds run against a labelled local adapter.
Character creation from the portal
PartialImplemented against the existing backend contract: a pending character plus a character application, with idempotency protection. Long-form application fields await the applications contract.
Applications, notifications, activity
Not implementedInterfaces and proposals are documented; the backend endpoints are pending.
Staff administration
Not implementedScheduled with milestone 3. No administrative screens are exposed today.
Platform
Platform: capability report
Each row states what is present and what a member would actually be able to do.
Public game server
Not implementedThere is no public server. Current platform target: GTA V / FiveM with OneSync, on a licensed private development server.
GTA VI support
Not implementedGTA VI support depends on a licensed, technically supported multiplayer platform that does not exist today. No GTA VI server is operated, promised, or advertised.
FXServer runtime verification
PartialAutomated tests prove domain behaviour and compilation. A licensed-server smoke test and multiplayer abuse testing remain a separate, unrecorded gate.
Milestones
Where each track currently stands
The full breakdown, including the evidence required to call a stage complete, is on the roadmap.
Milestone 1 — Website foundation
In progress0 of 5 tracked items done · 5 in progress
Milestone 2 — Functional account portal
Planned0 of 4 tracked items done · 0 in progress
Milestone 3 — Community operations
Planned0 of 4 tracked items done · 0 in progress
Milestone 4 — Extended roleplay tools
Planned0 of 4 tracked items done · 0 in progress
Game framework — current increments
Planned4 of 6 tracked items done · 0 in progress
Verification boundary
What the automated checks do and do not establish today.
Lint, strict type checking, unit and component tests, contract tests and production builds run in continuous integration.
Those checks prove domain behaviour and compilation. They do not prove that the game resource runs correctly inside FXServer, and they do not constitute multiplayer abuse testing.
The licensed-server smoke test remains a separate acceptance gate and will be recorded here when it is run.
Read the roadmap