All checks were successful
PR checks / checks (pull_request) Successful in 2m55s
Nine captures tagged rust (D65): the server list, feed, leaderboard, live map, permissions and the RunicNPC profile editor on the web, and a server's feed, its map and the player's Rust account in the app, from an Android-app edge debug build. D80: every name in a capture is a role (admin, moderator, player...), from this phase on. D81: the Rust demo's players are mock data written by scripts/mockRustDemo.mjs; the server, its status, map, permission groups and RunicNPC sync state are the real Oxide test server's. The captions and /modules/rust/ and /app/ say which part is a demo cast. seedDemo.mjs gains --game rust (server row with a weekly wipe, public presence for the demo, two NPC profiles, a VIP group). captureScreens.mjs gains a click list per screen. The homepage shows the Rust live map beside the UO capture (D76); three Rust docs pages carry their screen. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
64 lines
2.6 KiB
Plaintext
64 lines
2.6 KiB
Plaintext
---
|
|
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.
|
|
*/
|
|
---
|
|
|
|
<section class="page section looks">
|
|
<p class="eyebrow">What it looks like</p>
|
|
<h2>The other end of that diagram</h2>
|
|
<p class="prose looks__lede">
|
|
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.
|
|
</p>
|
|
|
|
<div class="looks__pair">
|
|
<Screenshot id="shard-status" />
|
|
<Screenshot id="rust-map" />
|
|
</div>
|
|
</section>
|
|
|
|
<style>
|
|
.looks h2 {
|
|
margin: 0.35rem 0 0.75rem;
|
|
font-size: clamp(1.6rem, 3.2vw, 2.1rem);
|
|
}
|
|
|
|
.looks__lede {
|
|
margin: 0;
|
|
max-width: 46rem;
|
|
color: var(--muted);
|
|
}
|
|
|
|
/* Side by side where there is room for two screenshots to stay readable, stacked below. */
|
|
.looks__pair {
|
|
display: grid;
|
|
gap: 0 1.5rem;
|
|
grid-template-columns: repeat(auto-fit, minmax(min(100%, 30rem), 1fr));
|
|
}
|
|
</style>
|