Amber Folio — dev page

Files are read in your browser and never leave it. A file whose name is not a legal DOS 8.3 name is refused by the emulator's own filesystem rules and listed as skipped — that refusal is the emulator being honest, not a fault. What you drop is kept in this browser and comes back on its own next visit, and so does anything you save while playing; dropping a second directory replaces the first, and your saved games stay.

every controls improvement, by screen

Everything above is kept on this machine, in this browser, and nothing is uploaded anywhere. Forget everything empties it: the copy you dropped, the games you saved on it, whatever was read out of your journal, and the note that says this copy has answered the code wheel. Your own files on your own disk are untouched — this is a copy the page made, not the original. If a browser refuses to keep something because it has run out of room, the reason is printed in the console below rather than swallowed: nothing already kept is lost when that happens.

Tap a key and the machine gets its scan code, exactly as if you had struck one. Shift, Ctrl and Alt latch - a finger cannot hold one down and press a letter with the other hand - so they stay down until the next key goes under them. There is no key repeat: a finger held on a key is one keystroke. While the keyboard is up the arrow keys and Return drive it rather than the machine, which is the path a gamepad will take in M8; close it and they go back to the game.

With the code-wheel seam on, the game asks you for a word off the wheel exactly as it always did - this emulator does not answer it for you, and cannot. Answer it correctly once, off whatever form of the wheel your copy came with, and this browser writes down that this copy has answered; every visit after that goes from the titles to the menu with nothing asked. Ask me again forgets it.

Your document is hashed in your browser and dropped - no page of it is read, parsed or kept, because a document here only ever demonstrates that you hold it. If this build knows the edition it says which, and any seam waiting on that document lights up in the list above. If it does not, it says so and gives you the file's SHA-256: nobody has fingerprinted that edition yet, and that hash is exactly what an entry for it would be made of. Show it again next visit - this page keeps nothing about it.

Your document is read in your browser and never leaves it, and no page of it is kept — what is kept is the text it was read into, in this browser's own storage, so that reading a journal is something you do once rather than every visit. It stays on this machine, in this browser, and Forget it removes it and anything you corrected. (It shares a database with the copy you dropped, and Forget everything empties both.) Recognition needs an OCR engine beside this page; without one every entry is still located and decoded, and this page says so rather than quietly finding nothing. Cite them all is a debug cheat: it puts every entry, tale and proclamation the text holds onto the game's own Notes log (the journal seam), so you can open each in turn and proof-read what the engine read — and the log stays filled that way, across visits, until Forget it.