oskiewar's Steam shell #
An Electron window around the browser runtime — the same xbox/live/oskiewar.js
that oskiewar.com serves and the reel factory renders three times a day. The
rationale for choosing Electron over extending the native shells is in
../STEAM.md under Build strategy; the short version is that this is the one
runtime with production mileage, headless test coverage, and a content-hash
burner watching it.
npm start # needs electron on PATH
../../../node_modules/electron/dist/Electron.app/Contents/MacOS/Electron . # or the repo's copy
How it fits together #
oskiewar.js has no I/O of its own — no fetch, no DOM, no audio, no storage.
It is pure logic reading nineteen host functions that mac-test.html passes in
positionally through new Function. So the shell supplies a host, not a port.
main.jsregisters anapp://scheme and servesxbox/liveoff disk, with the same six out-of-tree assetsxbox/tools/serve-live.mjsmaps (QR encoder, analytics, two cursors, Comic Relief). Keep the two maps in step.preload.jsreads the game source and exposes it as__fightPieceSource, the branchmac-test.htmlchecks before it fetches/oskiewar.js. Taking it also skips the website update poller, which is a live-reload affordance a shipped build has no use for.- The window is pinned to 16:9 via
setAspectRatio. The game fixes vertical to 1080 logical units and derives width from the box aspect, so a 16:9 window is 1920×1080 to the game. There is no set-resolution host call — this is the whole mechanism, and it is also how the store screenshots get their required dimensions. blur/focusdrive the frame driver'ssetVisible, because a backgrounded desktop window never firesvisibilitychangeand would otherwise free-run.
Verified 2026-09-15 #
npm run build:mac packages a signed (Developer ID, not notarized) arm64
app that boots to the real title screen in ~0.8 s with [boot] on
stdout, steamworks.js loaded and SteamAPI_Init reached (it fails only
because no Steam client is running, which is the expected answer on a dev
box). build:linux and build:win produce dir outputs from macOS too.
OSKIEWAR_SHELL_SHOT=/path.png makes a packaged build write what its window
shows after eight seconds and quit — the smoke test, with no screen recorder.
Staging copies the complete shared runtime through oskiewar-manifest.mjs,
including the unchanged web shell, account module dependencies, fonts, and theme
assets. oskiewar-release.json identifies every asset by SHA-256. The shell's
packaged/offline mode disables web accounts and relay publishing; it does not
rewrite a second version of the page. Regenerate with node stage.mjs.
Still owed #
- Overlay check on all three OSes —
electronEnableSteamOverlay()runs, but nobody has seen the overlay draw; macOS is historically the flaky one. - A Windows and Linux boot on real machines (they are cross-built here and never launched).
- A pad-only pass boot → rematch before ticking Full Controller Support.
- The appid.
steam_appid.txtholds 480 (Spacewar) until Steamworks assigns one; thennode ../depots/depots.mjs --appid=<n>writes the depot VDFs and../depots/upload.shpushes all three builds with steamcmd.