Status

Your browser needs:

• WebAssembly and ES modules. Every current browser has them. Without them Amber Folio cannot run.
• Origin-private storage and IndexedDB. Where your game files are kept between visits, along with your settings and your switches. A browser with neither still plays; it just asks for your copy every time.
• An audio worklet. For the PC speaker. Browsers keep sound off until you click or tap, so sound starts with your first interaction.

The emulator runs a game. The parts that let you sit down and play one comfortably in a browser are the next milestone.

• Nobody has played this in a browser yet. The emulator keeps a list of what only a person can check, and it still includes a real copy saved and reloaded in a browser, and whether the game sounds right. Everything else is exercised by recorded sessions rather than by a person at a keyboard. Expect to be the first to find something.
• Nobody has played on a phone yet. There is an on-screen keyboard — an 8-way cluster for walking and fighting, every letter and digit for naming a character, and Enter, Esc, Space and Backspace — split onto both sides of the picture sideways and set below it upright, shown by itself on a touch screen and from the toolbar everywhere else. Holding a key repeats it, the way holding a real one would. Nobody has yet started a game and named a character with it on a phone, or heard a screen reader read its keys.
• Nobody has read a journal entry off a display. The emulator has now read a whole Adventurer's Journal — every entry and every drawing, by the same OCR engine this site serves — but only as files checked against each other. Nobody has looked at an entry on a screen, in the emulator or here, and nothing on this site has been done with a real document at all. The emulator knows one edition of the journal.
• Nobody has answered the copy-protection question here. The game asks it, the enhancement watches for your answer, and this browser writes down that you gave one. All of that is built and none of it has been watched happen: nobody has yet played a second time and seen the question not asked.
• Nobody has loaded an imported save yet. The saves panel exports a saved game or a character as a zip, deletes one, and imports one into the slot you choose, refusing anything that is not a save by name. Nobody has yet loaded an imported save in the game, seen a deleted one gone from its load menu, or found out whether the game lists an imported character that its roster file does not name.
• Nobody has played a copy from a Dropbox link yet. The player downloads your game folder, zipped or as a .tar.gz, or your Adventurer's Journal, from a Dropbox share link. A real copy has come in that way and been recognised, but it was missing a file the game needs, so nobody has yet played a game started from a link, or used a real journal from one.

• Your files never leave the browser. Nothing is uploaded — not a game, a save, or anything made from one.
• No special setup. The emulator runs on one thread, so it works inside an ordinary page with no special setup.
• Browser storage can be evicted. A browser may clear a site's storage when it is short of space, and clearing site data always will. Supplying your game again is quick; keep your own copies of saves you care about — the Saves button on the player's toolbar exports one as a zip.
• Folder drop is Chrome and Edge only. In other browsers you select the files one by one instead.
• A zip or .tar.gz, or a Dropbox link to one, works too. A zip or a .tar.gz of the game folder can be chosen or dropped instead of the folder, in every browser. A Dropbox share link to one is downloaded by your browser straight from Dropbox — it never passes through this site.
• Your journal comes in with the game. The Adventurer's Journal PDF sits beside the game files in the release, so it arrives with the folder; a copy kept elsewhere is shown through a button on the files panel, or from a Dropbox link pasted beside it. A document is hashed in your browser and the emulator is shown the digest alone, and the file is kept here with your copy of the game.
• The copy-protection question is asked once. The enhancement is on from the start, and the game still asks its question the first time. Answer it and this browser writes down that you did — against the digest of the program and nothing else, with no note of the question, the answer or the time. The enhancements panel has a button that forgets it, and the game asks again the next time it starts; switch the enhancement off there and it asks every time.
• The OCR engine is served from this site. Reading a journal needs an OCR engine, about seven megabytes of one. It arrives inside the emulator build, pinned by the same hash, and it is downloaded from this origin when you press the button that reads your journal — never from a content delivery network, and never on an ordinary visit.
• Your saves are kept here, and only here. Anything the game writes is kept in this browser beside your copy and put back the next time you play, and each saved game is kept as one piece, the way the emulator says the game makes one. None of it goes anywhere else: an export is made in the page and saved to your own computer, and syncing saves between your devices is later work.
• Sound starts on a gesture. Browsers keep sound off until you have clicked or tapped. The game starts running on its own; the first tap, click or key press anywhere in the player turns the sound on too.