From the development notebook. These entries discuss story details and describe the game at the time of writing.
The old game earns the crossing
The Apple IIe opening became more like a remembered party adventure in 0.8.0. John finds the six men together, recalls their names and directs an original turn-based encounter. The secret door comes after they have fought together. It appears on the paper where the old game should show only stone.
The next clarity pass, 0.10.1, made the crossing easier to understand. Cold air reaches the real keyboard. The Fighter mirrors John’s hand. John reaches toward the page, and the room on the screen becomes the room around him.
The first embodied moments now establish that John remains John inside the Fighter. The same men have come through with him. Courage becomes something he can feel beneath his own fear, and following the handwriting gives him an immediate purpose. The arrival can be dismissed once the camera enters the body, and completes automatically if the player waits. See The door on the paper.
Places that can be remembered
Build 0.11.0 makes the rooms distinguishable through their materials, light and use. Repeating the same stone and cyan light everywhere made it difficult to remember where something happened.
The vault now has woven maze tapestries, brass details, a coffered ceiling and suspended candlelight around the armillary. The archives use damp mineral colors and stored paper. A hearth and worn rug give the refuge a warmer center. Used cups, candles and a manual give the desks a human scale. Farther down, pale stone and worn standards change the character of the halls.
The tapestry is a generated art asset made for the game. Draped cloth geometry, regional materials, surface maps and prop arrangements carry it into the actual environment. It is decoration, separate from the father’s authored notebook pages. The art goal is a place the player recognizes on returning, where a familiar object can carry an unfamiliar feeling.
Rendered review led to a more enclosed vault roof and writing tables with legs and braces. The executable builds and all 398 automated tests pass, including the existing continuous campaign route. This establishes a working release, while live performance, audio balance and the emotional effect of returning to these rooms still need human playtesting. The environment pass records the assets and limits.
His father returned to the computer too
The author proposed an important new connection: when John’s father felt disconnected from his son, he would start the old computer to remember the time they had shared. John’s return could eventually reveal that his father had made a similar return of his own.
This makes the saved party and the old machine more than remnants of childhood. They may also have been the father’s private way of remaining close. It leaves room for both men’s experience; it need not resolve every disagreement or tell the player which feelings to have.
An opening movie in which John visits the house and interacts with his mother is now on the development roadmap. Something she says could acquire its full meaning later in the dungeon. The scene, its dialogue and the exact moment of realization are planned work, not part of the released opening. Any new dialogue will be fictional scene writing, not an additional quotation attributed to the author’s actual parents.
Remember the living
The author reached the childhood chart and could not tell what to do next. The next step existed, but the game withheld the Bishop instruction until John stood beside the correct wall. We made the route explicit at the discovery: follow the west aisle north, find the old writing, inhabit the Bishop and read it before approaching the compass. A mystery needs a question the player can act on.
The opening battle had the opposite problem. Its commands worked, but they carried too little weight. The author's memory of typing spell names led us back to the original Apple II manual and the deliberate rhythm of selecting every man's action before committing. WARD and FIREBOLT now ask for a word at the keyboard. The manual is always available. Consulting it belongs to the experience of balancing impatience with preparation.
The author chose avoidable loss rather than a scripted death. Enemies now announce whom they will converge on. Guarding, supporting or removing the threat can keep everyone alive. Rushing can leave an empty row. Winning the fight does not automatically fill it.
John must call the missing man back through his name or aspect. Each class has a different remembered detail; the recovered roster remains available if the player needs help. The later journey journal preserves whom John recalled. There is no extra power for losing someone. The intention is to make the same six footsteps matter more when the screen becomes a room around him.
This pass still needs the human test: does the player understand the threat, and does calling someone back feel like attending to him rather than entering a password? The battle and route guide records the implementation and its limits.
The author's Steam Deck question exposed a practical problem: the executable still depended on this development computer's asset path. The portable build now looks beside itself first. A Windows package with Proton instructions and an 800p viewport gives us a concrete route to handheld testing. Compatibility, performance and controller feel on actual Deck hardware are still open questions; producing a ZIP does not establish those answers.
The men behind the letters
Build 0.13.0 changes what recovery means. The author supplied the old names in order: BAC, LAC, VAC, PAN, SYD and MAC. Instead of asking the player to invent someone, each man offers the name that was already there. John first recognizes a gesture or the face he once imagined, then a name, then his relationship to that person. Deliberate page breaks and a separate acknowledgment let those arrivals breathe.
PAN makes the remembered arrangement wrong in a useful way. He was Dad's neutral Thief, among five of John's good-aligned men. John and Dad had deliberately chosen different alignments to compare the game. Those labels belong to the old character sheets; they do not describe the moral worth of either father or son.
When asked whether to announce a rescue quest immediately, the author chose to let PAN's presence raise the question. He added the missing piece: John's own Thief, NIP, stayed at the Adventurer's Inn. Dad had borrowed the other five to retrieve PAN, hoping PAN could help him recover the rest of his own team. NIP now has a three-part optional conversation and a visible place at the table. He remains there; visiting him does not silently change the active party.
This changes the meaning of forty years. That is how long John has been away, not how long the disk has been silent. MAC's recognition recalls the mother's account of Dad turning on the computer when he missed John. John had pictured a man remembering a shared evening. Now he can imagine his father continuing a journey with the characters his son had made. The full mother-and-son house scene is still on the roadmap.
The modern journal keeps the six recollections and the Inn conversation, with pages so the story remains readable at handheld resolution. Older chosen names remain untouched; new recoveries use the supplied identities. The distinct conversations and gestures are fictional connective writing around the author's history. No new father quotation, character voice recording, alignment mechanic or later rescue destination has been invented as a fact.
The Windows portable package is refreshed alongside the code, README, changelog and version history. Hidden 800p review also led to a fully opaque journal backing so world and HUD text cannot compete with the recollections. Verification results are recorded in those release documents; real Deck compatibility remains a hardware playtest, and the emotional pacing still needs the author's ear.
The first Deck test does not reach the room
The author's first hardware report was a white window followed by a crash, then a frozen white window, under Proton Experimental. The terminal and window appeared, but the computer scene did not. A portable archive and successful Windows captures had not established that the game could initialize on the Deck.
Inspection found two portability assumptions. Startup forced the Windows DX12 renderer, and normal checkpoint storage still used a path compiled from the development computer. Build 0.13.1 tries Vulkan for the Deck and resolves saves beside the portable assets. The existing save error handling means the path bug alone does not explain the crash. We should not call either change a confirmed fix before the author retests.
The earlier hidden captures deliberately avoided real checkpoints, which also left that normal-startup path outside the portable smoke test. New focused tests cover renderer selection and portable save resolution; opt-in startup logging makes the selected paths and Rust failures inspectable. Proton's own log is still needed for native graphics failures. Local rendering checks retain the host's working DX12 backend and are recorded as Windows checks, not Deck validation.
The next answer must come from the handheld: can it reach the computer, continue a journey and render the modern dungeon? Until then this is a diagnostic build. Protecting the player's progress and making failure explainable are part of making a place worth returning to.
A journey in your hands
The next report finally reached the game: the author confirmed that 0.13.1 worked on the Deck. Then came the gaps a desktop test could not answer. The controller did nothing, the game was windowed, and leaving it was not obvious. A successful first frame was only the start of making the handheld version usable.
Build 0.14.0 gives the game native gamepad input. The old computer can start with A. The left stick steps and turns through the green maze, while the D-pad chooses the old numbered battle commands. The manual remains useful: a player can read and select the printed spell or remembered name without summoning a keyboard. In the modern dungeon the sticks become analog walking and looking, and the triggers become attack and guard.
There are more meaningful actions than there are buttons. View opens a paged command menu for the Inn, maps, company journal, magic, orders and equipment. Browsing it pauses the modern world without cancelling an earlier tactical pause. Confirming an action must not also swing a weapon or dismiss the next page. Focus loss and disconnected controls receive the same care: returning to the game should not make John move or attack before the player is ready.
Leaving is a first-class action too. View, Menu/Start and A confirms Save and quit. The checkpoint system sees that command before the controller layer restores the physical keyboard state. Quit also works when storage is unavailable; safe-save rules still govern what can be preserved. The handheld now requests fullscreen, while hidden review captures remain windowed and never take desktop input.
The guide records Steam's standard Gamepad template, rather than asking the player to invent a keyboard layout. The author has confirmed startup on hardware; this release's controller feel, fullscreen behavior and exit flow still need their Deck retest. No new story chapter was added while these basic interactions were incomplete.
Working buttons are not readable choices
The author got 0.14.0 running after a reported truncated transfer. The D-pad did control the game, but the relationship between directions and numbers was hard to decipher. The distinction is useful: a binding can pass an input test and still fail to explain itself to a player.
Build 0.14.1 makes the recovery menus conventional. Up and down highlight a visible choice; A commits it. The old keyboard numbers remain, and the deliberate reading beats remain. The computer exposes X twice for a new journey. The old disk's NEW GAME and QUIT still belong to its fictional loop back to the lost characters, so the actual start and exit controls must be unambiguous around that fiction.
The missing voice report also needed a precise answer. The opening has one short father fragment at about seventeen seconds; John's thoughts are subtitles. All nine packaged recordings decode, and the source ZIP passes its checks. That does not prove what came from the Deck's speakers. A voice-test command now enables sound and voice and plays a known line, with ON/OFF settings visible in the controller menu. A loading guard keeps a spoken cue from using up its lifetime before its file arrives. No new words have been attributed to the author's father.
A source archive passing CRC does not prove a transfer arrived complete. Packaging now finishes and verifies a temporary file before publishing the ZIP name, then writes a SHA-256 sidecar for checking the copy. This pass addresses explanation and observability alongside the controls themselves; the next hardware report should be easier to interpret.
The final local check passed 422 workspace tests, including a controller test that caught a missing selection-context update before publication. The corrected input path now drives the visible selection and blocks held confirmation when the scene changes. The extracted archive starts with its own assets and save path, and its checksum matches. The remaining check belongs on the Deck: how clearly the prompts read in the hand, and whether the voice-test line reaches its speakers.