Build note
Ledger runs in a browser tab: notes on the local builds
The three entries on the shortlist are not store apps. They are HTML pages under /play/ on this domain. This note explains what that means for a visitor who expects a download button.
Step 1 — What "local browser build" means
Each build is a self-contained page with its own art, audio and loop. Opening the URL loads it like any other page. There is no package to install and no store receipt. The desk hosts the files; the visitor's browser runs them.
Step 2 — What is not on the card
Store ratings, review counts and download bands do not exist for these builds. The desk does not invent them. The facts line on every card states the absence plainly.
Step 3 — Storage inside the build
A build may keep high scores, missions and skin unlocks in the browser's local storage under its own keys. Clearing site data for eldritchgamesda.com resets those keys. The site-level consent key egd_runebench_consent is separate and only remembers that the cookie notice was closed.
Step 4 — The Close contract
Every build carries a fixed Close control in the top-left corner. It must remain visible on the menu, during play, on pause and on the results screen. If the visitor arrived from a page on this domain, Close returns there; otherwise it returns to the homepage. The desk treats a missing Close as a failed way-back reading.
Step 5 — Phones and desktop
All three builds accept touch for lean or steer. Desktop keys remain available. The bench logged both before setting the order. Performance depends on the device; the desk does not claim a frame-rate warranty.
Step 6 — What affiliation is refused
The site has no tie to Google Play, the App Store or the original toolchains that produced the builds. Names on the pages belong to their owners. Editorial demos on this domain are not a distribution channel for someone else's commercial app.
Step 7 — How to report a break
If a build fails to load, traps the tab or loses Close, write through the contact page. Include the browser and whether the failure happened on phone or desktop.