From the development notebook. These entries discuss story details and describe the game at the time of writing.
A doorway should look open
The author sent a screenshot of stone blocks hanging across the top of a doorway. The route was technically passable, but the room was telling the player otherwise. The mistake was shared: archive cladding assumed every wall was full height, even the short lintel above a door. The visible stones and the collision opening no longer described the same space.
We now build courses within each supporting section's actual bounds. That same method gives later rooms staggered masonry and dresses the previously plain end walls. The fix belongs to the construction rule, not to a few stones removed from one screenshot.
The next visual step follows from that repair. Cut arch stones have curved faces, bevels, mortar joints and a projecting keystone. Wide arches flatten before they reach the ceiling. The archives have tiled barrel vaults, and the practical lights have forged guards. The intention is a dungeon whose parts appear to carry one another's weight, with a clear route through them.
The existing memories, handwriting, voices and choices remain the reason to walk that route. This pass changes the architecture around them. It keeps the High/Balanced profiles and bounded shadow costs, and adds close capture views for the affected entrances so future changes can be inspected from the player's height.
The author then reached the Compass Door and could not tell whether the childhood map had been collected. That uncertainty is a presentation failure: the locked door ignored interaction before its prerequisites, and a confirmed choice still required a return to the desk or bench without a useful door prompt. It now responds with a guide showing what is done and what remains. The chart has an unmistakable recovered/missing heading, the diagram follows the actual aisles, and the guide names the nearby landmark and facing direction. The choice still matters; the act needed to complete it is explicit. No restart or personal save edit is required.
Release validation: all 443 tests passed, including the Compass Door guidance regression and older-save gallery checks. Formatting, strict Clippy and the PC build passed. Four close doorway views and the adjoining rooms were reviewed on the AMD renderer; the missing/recovered chart guides fit both PC and 1280 x 800 Balanced views. The refreshed 60.9 MiB portable package passed its archive and file-hash checks and rendered from its own extracted folder. The normal shortcut is refreshed. These checks used no desktop input or personal saves; handheld hardware performance and the clarity of the route in human play still need review.
A room still waiting
The game worked on the Deck, but the author still could not find a comfortable way to leave it. A command hidden behind a second button or a fourth page was technically reachable and practically obscure. This pass puts Resume and Save and quit together on the first menu page, with Menu/Start opening it from play. Opening films now stop their clocks while the menu is open; the story should not move on while someone is looking for the exit.
The request for an in-game keyboard was equally useful. Typing a remembered spell is part of the old game's texture, but deciphering controller directions is not. The new letter grid lets the player move, type, erase and submit with the controller, while keeping the manual and roster available. It uses the same validation as physical text. A wrong word costs nothing, and a held A does not both type and commit.
The larger change is why the computer is here. Mom is moving. John comes to help, carrying a recent separation with him, and finds the machine in a carton beneath his old desk. The author settled a new timeline: forty years old, twelve when he played, Dad gone ten years. A bag in the car and a conversation he kept postponing give the present weight before the dungeon asks anything of him.
Mom knows the shape of the difficult relationship, but she does not deliver its explanation. She keeps the kettle out. She remembers the drive during the last winter. She leaves the paper where it was and goes back to the kitchen. The game and the notes were a rare shared language between father and son; we want the player to notice what was easier on the page without a speech naming it.
The current production uses three original cinematic illustrations, restrained motion, player-paced subtitles, existing room ambience and a score. This is a concrete playable opening, not a claim of fully animated human performance. It gives us a scene worth casting and animating later. Moving to Unity or Unreal would not decide how Mom looks away or how long John waits before answering.
The King/Father may eventually help the protagonist do what Dad could not. That does not yet tell us what Dad left inside the game. We have kept that answer open. Personalized protagonist name and gender are also future work; the current story remains John, with an unspecified former partner. The party's established names and separate histories stay intact. The cup in the kitchen gives the journey somewhere living to return to.
The full workspace passed 427 tests, including the route from the house to Floor 4 and controller-driven spell correction and recall. A misleading full-frame preview prompted extra investigation of the captions. Direct inspection of the caption regions confirmed that the text was in the recorded files; pixel checks across a 48-frame sequence found it throughout. The final UI uses a simple heading backing and avoids invalidating unchanged text every frame. The house tests passed again after those refinements, and repeated extracted-build captures verified the composition. Local 800p renders and archive checks are evidence of the shipped composition and files, not a substitute for the next Deck playtest. No desktop input or player save was used in these checks.
Casting her years
The first listening feedback caught a casting problem: Mom sounded about twenty.
Warmth alone did not give her the years the scene needs. A follow-up audition
compares two American stock blends and the British blend used for Gertrude in
the author's Hamlet project. Each reads the same three lines at the same pace,
with the released voice available beside them. We are asking for a believable
mother of a forty-year-old, not an artificial elderly effect. The author will
judge that through listening before the seven production takes are replaced.
The audition generator verifies that all installed recordings remain unchanged;
the samples decode without clipping. This is casting work, not another game or
Deck release yet.
The author preferred A's American Sarah / Kore blend, but it still sounded too
young. The British direction is ruled out, and the breathier B was too slow.
The next two short takes stay American and move at a more conversational pace:
one changes the blend to Sarah / Alloy, the other gently lowers A's register
without stretching the words. These remain labeled casting experiments. We
have not mistaken passing audio checks for a believable performance.
Let Mom be in the room
The author asked for a realistic voice in the mother scene and pointed out that Dad already had one. That was the right correction: the local Kokoro pipeline was available. Looking at Doc Hub and Perchance showed a useful production approach already in the user's projects: distinct stock casting, modest blends, sentence-aware pacing and careful levels.
Mom now has seven recordings, including both replies to the tea choice. Her voice is a separate American stock blend, kept close and clear against the room. She does not explain the father-son relationship. She remembers a sound from the kitchen and asks John to bring his cup. John's internal words remain text, giving her an audible presence in the present.
The scene owns its speech: leaving a line stops it, rereading brings it back, and opening the menu pauses it. We do not make the player wait through an unwanted line, or allow an old recording to arrive after the caption has changed. The father's files remain byte-for-byte unchanged. This is a directed synthetic pass; emotional credibility has to survive listening, not just a successful decoder check.
Validation: formatting, strict app Clippy with all targets, executable build and 115 app tests passed, including the full opening-to-Floor-4 route. New checks cover both tea scripts against caption text, waiting for the current audio asset, discarding stale lines, actual recording selection, focus pause, exit cleanup, reread, skip confirmation and voice re-enable. All seven OGG takes decode to finite non-silent audio without clipping; durations and hashes match the manifest. All nine father recordings retain their existing hashes. The 60.8 MiB portable ZIP passed CRC, manifest and SHA-256 checks and rendered the house from an extracted folder with correct paths and no personal saves. Documentation links and the normal shortcut were checked. No desktop input was used. Auditory realism and Deck speaker output still require human listening; hidden renders deliberately mute audio.
Light on the remembered page
The Unreal room made the stone and the papers feel more tangible. The author's next instruction brings that ambition back to the game we can already play: develop Bevy further before considering a migration. The AMD card was already doing the rendering. The opportunity is to use its work more deliberately, with better surface response, contact, light and architecture.
This pass puts the writing desk at the center of that effort. The existing handwriting and graph-paper maze now sit beneath a warm hanging lamp in the dungeon, and the reading nook has an actual timber roof. They should feel like objects someone used. No new sentence from Dad is necessary to make the paper matter.
Stone gets a less noisy mineral surface. Texture filtering keeps its grain from breaking into shimmer at a distance; indoor environment maps give worn metal something softer to reflect. High adds temporal smoothing and contact shading, while the handheld keeps a lighter profile. These are improvements to the existing visual language, not a claim that the current characters or environments are finished production art.
The work also exposed why lighting polish must include engineering. The shadow budget could follow the HUD camera instead of the player, and the first High render failed while allocating shadow maps. The budget now runs after scene updates and world transforms, including frames without an active 3D view. A regression check covers lights created during the frame and the transition into a camera. Render verification must accompany those tests before release.
The practical boundary stays clear: this release changes the game's presentation, not its story, voice or saves. Desktop captures can establish that the effects render and the interface remains legible. They cannot promise a handheld frame rate or replace playing through the journey.
Release validation: formatting, strict workspace Clippy, the build and all 439 workspace tests passed, including the two shadow-budget regressions. After the allocation fix, the AMD RX 6800 rendered the High Vulkan scenes, opening and retro UI successfully. DirectX 12 also rendered with a longer capture allowance for shader compilation. Three samples from the 48-frame camera pan were reviewed. The 60.9 MiB Deck candidate passed CRC, all 118 file hashes and its transfer checksum; an extracted Balanced copy rendered Floor 4 with its own portable paths. The normal launcher and documentation are updated. No desktop input or personal saves were used. This remains a PC validation of the handheld package; Deck performance and extended play still need hardware review.
Mature, with her energy intact
Both American refinements were getting closer, but the author still heard a voice a little too young. He also made clear that she should not sound too old. The direction is maturity with warmth and practical energy: a woman who can tease John about the boxes, then remember an ordinary sound from the kitchen. We have not changed her age in canon or added an explanation of the family relationship.
Build 0.15.3 brings the two close casting directions together for all seven lines: Sarah with a little Kore and Alloy, a gently lowered register, and conversational pacing. There is no additional slowness, tremor or exaggerated frailty. The chosen direction is now in the actual game and portable package, where it can be judged against the room and the subtitles. Previous takes and audition files remain available locally. This is another directed synthetic performance; its emotional credibility is still for the listener to judge.
Validation: formatting and the PC build passed; all three focused mother-dialogue tests passed, covering caption/branch matching, current-asset waiting, advance/exit cleanup, reread, skip and voice re-enable. All seven OGG files decode as finite, non-silent mono 24 kHz audio without clipping; manifest hashes and runtime durations match. Dialogue text and branch assignments are unchanged, and all nine father files match their existing hashes. The 60.8 MiB portable ZIP passed CRC, file-manifest and SHA-256 checks; the extracted 0.15.3 build rendered the house with correct asset/save paths and no personal saves. Updated documentation links and the normal shortcut were checked. No desktop input was used. This voice-only pass did not rerun the full game suite; perceived age and Deck speaker output still require listening.
Test the future before moving into it
The author asked whether we could develop the bones here, then move to Unreal for a stronger visual presentation. We agreed to test a small section early: the impossible door, John inside BAC, a notebook sheet, LAC's familiar concern for the company, and a watchman emerging through the arch. A short teaser should come from that real scene, labeled as an Unreal visual prototype. It should help us judge the migration rather than disguise how much remains to build.
The first obstacle is practical. The checked locations contain the Epic launcher and old sample content, but no Unreal Editor executable has been located. The launcher installation record is empty. That does not rule out an engine elsewhere; we have asked for its location. Visual Studio build tools are available, but compatibility depends on the actual engine version.
While that is unresolved, the existing sculptures now have a standard GLB export preserving their geometry, normals, UVs and vertex colors. Seventeen ambience/music/effect recordings have PCM WAV exports, and three notebook/tapestry images are ready to import. All 35 exports passed their format, geometry or audio/hash checks. The procedural animation and skinning do not travel with a static mesh; that work is explicitly still ahead.
The separate Unreal project, editor import script and forty-second scene specification are prepared. No Unreal import, playable scene, rendered footage or handheld performance has yet been verified. Game 0.15.3 remains the working release. The next step is locating the engine, then building and reviewing the actual scene before deciding how much of the game should move.
The author then confirmed the missing installation and started Unreal under R:\Unreal. The observed folder is UE_5.8, still containing only installer staging data at this check. The import helper now discovers that library and accepts either its parent folder or the version folder. We can proceed with the real engine import once installation is complete.
The menu must mean what it says
The author reached the green screen and could not find N or get Quit to leave. The current build was running; the route into the new house scene was too easy to miss. Worse, the old disk treated NEW GAME and QUIT as fictional errors. That intention was invisible to someone trying to start over or close the game.
Build 0.15.1 removes those loops. New Journey is visible on the title splash and works directly at the disk menu, with confirmation before restarting. Quit means quit. Numeric-keypad choices now match the top-row numbers. The existing save remains available until the restarted journey earns a new checkpoint. The mystery belongs in the dungeon, not in whether a menu command will work.
Validation: formatting, strict workspace Clippy, executable build and 430 workspace tests passed, zero failures, seven ignored documentation examples. New tests cover N on the splash without checkpoint storage, confirmed restart through top-row and keypad choices, retention of the durable save through the house, actual quit, and keeping N/Q out of exploration and text-entry contexts. Hidden Windows DX12 renders reviewed the splash and green disk menu at 1280 x 800. The final 60.6 MiB portable ZIP passed CRC, every manifest hash and its SHA-256 sidecar; its extracted executable rendered the updated splash with correct asset/save paths and no personal saves. Documentation links and the normal shortcut were checked. No desktop input was used; Deck hardware remains untested for this patch.
The quest we thought we finished
The author identified an imbalance: Dad's repeated phrases were becoming instructions on a loop, while the King barely existed. The old game also needed unfinished business of its own. The wizard is a definite surviving enemy. What John and Dad missed is a question we will carry, not an answer to invent in this pass.
The King now waits in the first modern room and asks for the missing map. John says "we" before remembering there is nobody beside the keyboard. Later, he smooths the paper instead of explaining his father's absence. BAC offers to lead; John asks him to say something if he hurries. Small actions let the old partnership and the present company occupy the same scene without a speech explaining them.
The chart discovery gets a pause: a heavy childhood line and a small correction left beside it. The author's new door-marking words belong there, once. His rueful WereBear warning belongs at the refuge, once. Corridor progress no longer calls the same few father fragments. The canonical pages keep their complete original readings.
In the gallery the King makes room for the map. His delivery acquires a little of the father's cadence; no line identifies him. The surviving wizard supplies the external stakes, while John's willingness to leave the map open supplies a smaller change we can see. This advances the existing four-floor journey and does not claim a new playable wizard encounter.
The close encounter also exposed a presentation limit: the distant King silhouette did not hold up at conversational distance. This pass gives him skin, facial features, hair and a muted royal robe, and brings him nearer the gallery table. He remains a procedural character awaiting a proper animation and likeness pass.
Release validation: 446 tests passed, including older-save migration, both audiences and the continuous route. Formatting, strict Clippy and the PC build passed. The closer King and spoken cards were reviewed on High and at handheld resolution. All seven new recordings passed signal and manifest checks; the existing family recordings were preserved. The 61.2 MiB Deck package passed archive and all 128 file-hash checks and rendered from an extracted copy. The normal launcher is updated. These checks used no desktop input or personal saves; listening to the performance and playing on actual Deck hardware remain necessary follow-up checks.
Through the threshold, in another engine
Unreal 5.8.3 is now installed, and the small experiment has become a native scene. The room starts with the six names in green, crosses into BAC's point of view, then gives the player a familiar sheet of paper before introducing danger. LAC's existing concern for everyone else belongs here: recognition should happen through a habit, not a biography.
The notebook remains the emotional anchor. Its warning about the rotating floor is one of the author's remembered lines. The cinematic preview uses Dad's existing mapping fragment; no new voice or answer to what he left behind has been invented. The stone watchman gives the room something to do: observe, guard or retreat, then answer during recovery. Defeat allows another attempt, and victory leaves the room open with a visible way to restart or leave.
The first render was too dark to read the creature. The next pass corrected instanced-material settings, exposed the stone surfaces and added fill so a silhouette did not have to carry the encounter. The character limits are plain, too. LAC and the first-person equipment are still stand-ins; moving engines does not create human performance or finished character sculpture. The transition currently fades between the CRT and room rather than transforming every corridor line into geometry. Those are real next tasks, not improvements we should pretend this build already contains.
The installation also needed the .NET Framework SDK for Unreal's native toolchain, and a project-local cache avoided an unavailable cache service. Build and capture scripts keep the process reproducible. Automated interaction checks exercise the room without desktop input or personal saves. Rendering, technical checks and a packaged launch are useful evidence, but they cannot tell us whether a shield feels good in the hand, whether LAC feels remembered, or whether the soundtrack lands. This separate Windows prototype is the next thing to judge. The working Bevy game and Deck package remain intact.
Validation: editor and standalone C++ builds passed on Unreal 5.8.3. The cooked Windows executable passed all 14 native state checks and produced a reviewed 1280 x 800 notebook/room render. All 1,200 cinematic frames were captured; the MP4 verifies as 40 seconds, 1920 x 1080, 30 fps with finite, non-silent decoded audio and no sample clipping. The final title card was visually reviewed. Tests/captures used no desktop input or personal saves. Hardware controller/Deck play, perceived sound quality, performance benchmarks and complete manual traversal remain unverified.