Roadmap

What exists, what is in progress, what is planned

Statuses describe the repository, not intentions. Nothing is marked done until it is merged, tested and verifiable — and the evidence required to call a stage complete is published alongside it.

23 tracked items4 done5 in progress14 planned

Two tracks, reported separately

The website can reach completion while the game framework is still early. A polished portal is not a playable server, and this page will not blend the two.

Website and portal

Milestone 1 — Website foundation

0/5 done

Project setup, design system, public site, navigation, metadata and the authentication integration boundary.

  • Monorepo packages

    apps/web and packages/ui added to the existing pnpm and Turborepo workspace.

    In progress

  • Design system

    Semantic tokens, typography, states and accessible components shared across the portal.

    In progress

  • Public information site

    About, philosophy, rules, getting started, roadmap, FAQ, staff, contact and legal pages.

    In progress

  • Authentication boundary

    Typed API adapter, httpOnly session cookie handling, structured error surfaces.

    In progress

  • Automated checks

    Unit and component tests, typecheck, lint, production build and an end-to-end smoke suite.

    In progress

Done means: The public site renders with real content, and the portal refuses to show authoritative-looking data while the backend endpoints are missing.

Milestone 2 — Functional account portal

0/4 done

Real backend sign-in, the player dashboard, characters and application tracking.

  • Backend session endpoints

    Registration, sign-in, session refresh, revocation and password reset in apps/api.

    Planned

  • Player dashboard

    Account summary, characters, applications, notifications and recent account activity.

    Planned

  • Character creation and tracking

    Multi-step creation with saved drafts, validation and review status.

    Planned

  • Route protection

    Server-side session resolution with authorization still enforced by the backend.

    Planned

Done means: A member can register, sign in, submit a character application and see its real status without any development adapter in the path.

Milestone 3 — Community operations

0/4 done

Staff review tools, moderation, support, sanctions and audit history.

  • Application review queues

    Assignment, review notes, decisions and requests for more information.

    Planned

  • Account and character administration

    Role-scoped administrative actions with recorded reasons.

    Planned

  • Support and appeals

    Tickets, reports, appeals and outcome records.

    Planned

  • Audit history

    Searchable records of sensitive actions with attribution and request references.

    Planned

Done means: Every sensitive staff action is attributable, reasoned and reviewable, with permissions enforced by the backend.

Milestone 4 — Extended roleplay tools

0/4 done

Businesses, organisations, financial views, property, vehicles and community features.

  • Business and organisation modules

    Ownership, employees, roles, payroll, procurement and licences.

    Planned

  • Financial views

    Ledger-backed statements and transaction history in integer minor units.

    Planned

  • Property and vehicle management

    Persistent ownership records and registry views.

    Planned

  • Community platform

    Forums, classifieds, events and advertisements with in-character boundaries preserved.

    Planned

Done means: Monetary and inventory views read from the authoritative ledger and never compute a balance in the browser.

Game framework

Game framework — current increments

4/6 done

The FiveM resource, persistent accounts and characters, local text roleplay and the platform adapter that isolates engine-specific code.

  • Monorepo and persistence

    pnpm/Turborepo workspace, PostgreSQL with versioned migrations, Drizzle schema.

    Done

  • Accounts, characters, permissions

    Account and character lifecycle, ownership validation, role and permission checks.

    Done

  • Authenticated internal API

    Lease-based game sessions, heartbeats, atomic state persistence, audit events.

    Done

  • Local text roleplay

    Local IC chat, /me, /do and local OOC with server-validated proximity and rate limits.

    Done

  • Employment and economy engines

    Hiring, work assignment, validated completion, payroll and an authoritative ledger.

    Planned

  • World simulation

    Weather and time policy, scheduled events, supply and demand, neighbourhood state.

    Planned

Done means: An FXServer smoke test and multiplayer abuse testing on a licensed private server, recorded as a separate acceptance gate.

Local automated tests prove domain behaviour and compilation only. They do not prove that the resource runs correctly inside FXServer.

Current development statusAnnouncementsAsk about a stage

Support contact for roadmap questions: not published yet.