Orbital Frontier — world status

Bodies

Body	Type	Orbits	Radius	Gravity	Atmosphere	Sphere	Year	Day	Vessels

Vessels

#	Name	Owner	Actions	Body	State	Altitude	e	Next	Lost	Built from	Resources	Parts	Mass

Players

User id	Resources	Achievements	Readings	Ships	Contracts	In flight	Since

Server

Tick time

world step whole tick

Parts

Every part the game is built from lives in one catalog on this server, and this is where it is edited. A change takes effect at once and there is no history: a vessel already in orbit is flown and stepped with the definition as it stands here, so halving an engine's electricity draw slows the drain of every ship already carrying one. Each part carries a hash of its own values; a rocket records the hashes it was built from, which is how the built from column on the world page can say a ship was assembled against older parts. Games download the catalog at startup and cache it, so an edit reaches a player on their next launch.

Part	Id	Category	Mass	Cost	Hash	Actions

Achievements

One entry is a trigger on a game event plus the reward it pays. The game asks for the enabled list when it starts (GET /achievements) and checks every entry against the events a flight raises, so an entry added here is earnable on the player's next launch — and a reward edited here is paid at the new figure from then on, never retroactively to the players already holding it. Disabling an entry hides it from the game but leaves it standing on the records of everyone who earned it. Who holds what is granted and revoked one player at a time, from the Achievements column on the world page.

Triggers and conditions — what an entry can ask for

Id	Title	Description	Reward	Trigger	Flags	Actions

Contracts

One template is a job a company offers: every goal met in ONE flight, for an advance paid on accepting and a reward paid on completing. The game asks for the enabled list when it starts (GET /contracts) and every player's board is drawn from it, so a template added here is on the boards its tier allows within seconds — and a price edited here applies to the offers drawn from then on, never to a contract a player has already signed, which carries the figures it was accepted at. Disabling one takes it off every board and out of every future draw; contracts already under way run to their deadline. The boards themselves — who has accepted what, and what it is costing them — live on each player's record, in the Contracts column on the world page.

Goals, money and the board — what a template can ask for

Id	Title	Client	Description	Tier	Money	Clocks	Weight	Goals	Flags	Actions

Refreshes every 5 s from /stats. The Tick time chart under the server tiles is the simulation's benchmark (GET /ticks, the last 600 timings): the world step line is World.tick() alone — every vessel walked along its rails, handed across the spheres it reached and its resources stepped — and the whole tick line adds the logging and the save around it. Hover a point for the moment it was taken, both figures, how many vessels the world held and the warp rate; warping the world from the map screen is how to see the step grow. A vessel's name (and a saved ship's, in the hangar dialog) opens a picture of it drawn from its part graph and the game's own part design files (GET /designs, painted by /ship_art.js) — parts only, no effects. Every vessel names the player who launched it and the body they launched from (Owner); the world keeps that owner, so a later write from the game cannot move a ship to somebody else, and GET /users/:id/vessels is one player's own fleet. A vessel's buttons set its resources part by part (PATCH /vessels/:id/resources), put it on a new orbit (PUT /vessels/:id/orbit), duplicate it (POST /vessels/:id/copy) or delete it; the game picks changes up on its next sync. A player's save sets their resources (PATCH /users/:id); the achievements count in their row opens a dialog with one check box per achievement that grants or revokes it (PUT / DELETE /users/:id/achievements/:ach, reward paid or taken back); the readings count opens a dialog listing every instrument reading the player took (logged by the game with POST /users/:id/readings), each with a delete button (DELETE /users/:id/readings/:rid); the ships count opens the player's hangar library (saved by the game with PUT /users/:id/ships/:name, the same list on every device they sign in on), each ship with what it is made of, what it masses and costs against today's catalog, and a delete button (DELETE /users/:id/ships/:name). The Parts page edits the one part catalog this server owns (GET /catalog, PATCH /catalog/parts/:id) — the game downloads it at startup and caches it. The Achievements page (the achievements tile is a shortcut to it) edits the catalog the game loads at startup (GET /achievements), where entries are added (POST /achievements), edited (PUT /achievements/:id) and disabled; who holds what stays on the world page, in each player's row. The Contracts page (the contract-templates tile is a shortcut to it) does the same for the contract templates (GET /contracts, POST /contracts, PUT /contracts/:id): what each company asks for, what it pays up front and on completion, how long the offer and the deadline run, and the goals — every one of which must be met in a single flight. Both pages carry the same reference for the events and conditions a trigger may name, and check what you type against it; a player's own board (what they have accepted and what it is costing them) is on the world page, in the Contracts column of their row. The Releases page lists every TestFlight build the ship pipeline has told this server about (GET /releases, written with POST /releases) — the name each one went out under and the exact "What's New" its testers read, which App Store Connect otherwise keeps behind an API key. Each release also takes one picture (PUT / DELETE /releases/<build>/image, stored beside the log and served at GET /releases/<build>/image). The Map page draws the whole system from GET /map — every body as a circle of its real radius, every orbit as its conic, every vessel as a dot — with the wheel or a pinch to zoom, a drag to pan, a tap to inspect (a ship's card opens its picture with View ship), and the chips along the top to lock the camera onto a world (?view=map&focus=moon opens straight there). The Warp row along its bottom is the world's own time control (POST /clock): the server runs the shared clock that much faster — up to 1000× — so an orbit that takes an hour closes in four seconds and a sphere crossing a week out happens while you watch. It is the whole world's, not this page's: while warped the server steps everything five times a second so no hand-off or reentry is jumped over, and every game is told the rate beside the time and runs at it, so a player who opens the app finds the world where the warp has taken it. Also: /world, /map, /users, /bodies, /catalog, /resources, /health.