Skip to content

FEATURES

What the game does. Each doc answers four questions: what is this, what are the rules and numbers, what does the player do, where does the code implement it.

When the documented numbers and the code disagree, the code wins; surprising numbers are flagged inline.

This is also the only place where implementation status is tracked. The other doc sets (ARCHITECTURE, API, DATA_MODELS, OPERATIONS) describe the target design; status notes (shipped, partial, design-only, known bugs) live next to the relevant feature in this folder. See "Status convention" below.

Index

Definitions

  • definitions.md — Consolidated terminology, game rules, resource types, ship types, and galaxy components glossary.

Gameplay

Economy

  • economy/lifecycle.md — Credit sources, sinks, tax rates, faucet/sink balancing.
  • economy/trading.md — Port classes, dynamic pricing, transaction flow, faction modifiers.
  • economy/haggling.md — Numerical and narrative haggling, 5 port personalities, anti-exploitation.
  • economy/port-ownership.md — Player station acquisition, tariffs, 9 upgrade types, takeovers.
  • economy/station-protection.md — Docked-ship safety: 4-tier security system, hired security-guard NPCs (STATION_SECURITY archetype), anti-theft tractor beam, 40/30/30 docking-fee economics, attack shield for docked ships.
  • economy/docking-slips.md — Slip scarcity: 4-class taxonomy (transient / long-term / construction / specialized), per-station-class slip counts, Tier-A vs Tier-B TradeDock discriminator (Tier-A required for Warp Jumper / Carrier), reservation queue with reputation-gated priority, 45–90 day Warp Jumper queue at peak.
  • economy/tradedock-shipyard.md — Premium hubs, 12-slip shipyards, construction events.
  • economy/contracts.md — NPC and player trade contracts with deadlines, rewards, and insurance options.
  • economy/black-market.md — Illegal goods, contraband detection, stealth routes.
  • economy/mining.md — Asteroid-field harvest loop, Mining Laser upgrades, AM claim licenses, depletion mechanics.

Galaxy

Planets

Status convention

Implementation status is tagged inline next to the feature it describes, using a four-status convention:

Marker Meaning
✅ Shipped Implemented and reachable end-to-end.
🚧 Partial Some pieces in code, some pieces still missing.
📐 Design-only Documented intent; no code yet.
🐛 Bug Known runtime defect against the documented behavior.

Notes are written like:

Status: 🚧 Partial — short note. Pointer at where the target spec lives if cross-cutting (e.g., "see ARCHITECTURE/auth.md").

  • Data models: ../DATA_MODELS/ (entities, schema, FK relationships).
  • API surface: gameserver auto-publishes Swagger at <api-host>/docs and OpenAPI JSON at <api-host>/openapi.json. WebSocket protocol design lives in ../SYSTEMS/realtime-bus.md.
  • Architecture: ../ARCHITECTURE/ (services, deployment).