--- import Screenshot from '../Screenshot.astro'; /** * The homepage's screenshots, one per game. PLAN.md §13 phase 9, D4 / D44; §16 phase 18. * * ----------------------------------------------------------------------------------------- * WHY ONE PER GAME, AND WHY THESE * ----------------------------------------------------------------------------------------- * `DataPath` above it draws the claim — a private game server, a sidecar, a public site — * and a diagram of a data path is a promise that the data arrives. This is the page where * it arrives, captured from a deployment wired to a running game server, so the section * directly under the diagram is the diagram's evidence. * * It is one game's screen, and says so (D76, taken in phase 17 under D67): the screenshot is * tagged `uo` in `screens.mjs`, so it prints "Ultima Online" beside it and may keep that * game's words in its alt and caption. A core screen was the alternative and was declined: * the claim here is live game state on a public page, which no core screen shows. Phase 18 * added a Rust capture beside it, labelled the same way: the live map, because every pixel * of it is the running server's — the Rust demo's players are a demo cast (D81), and the * map shows none of them. * * A gallery here would compete with `Capabilities` further down, which is the part of the * homepage that enumerates. So: one figure per game, its signature screen, and the rest of * the set on each game's page under `/modules/`, where each sits beside the claim it supports. */ ---

What it looks like

The other end of that diagram

Two demo deployments, each with a real game server behind it. On the first, the gold supply, the state of the link and the player online are all read from an Ultima Online server over the bridge. On the second, the map is the running Rust server's own: its island, its monuments, and the events on it as they happen.