Entry 001 / 27 September 2026

Building the foundations of a Days remaster

We are working toward a faithful reconstruction of Kingdom Hearts 358/2 Days using Kingdom Hearts III as the runtime foundation. The goal is Days gameplay, missions, panels and progression with a modern presentation. This is an independent fan project in early development, with no announced release date.

A small interface, a useful milestone

A cooked diagnostic widget has now loaded, appeared and been removed inside KH3 at its native title screen. That establishes a route for authored UI to reach the game. The partial Days menu is also progressing: separate artwork and logo layers are prepared locally, and the menu navigation core passes 10 offline tests.

This is not yet the complete in-game Days menu. Artwork rendering, input ownership and real New Game/Load destinations still need integration and runtime verification.

Using the original as a laboratory

We replay recorded inputs from controlled states in the original game and capture what happens. A title and Mission Mode suite has passed 26 reference comparisons. Movement and jump experiments also reproduce sampled behavior, including different arcs for short and held jump input.

Some memory fields are useful candidates for future telemetry, but their units and ownership are not fully established. These observations are research results, not a claim that matching player physics already runs in the remake.

Foundations before content counts

The reusable mission core passes 13 synthetic tests and has received an independent Claude review. Recovered mission records help organize research; they do not represent playable missions. We still need native gameplay adapters and a complete end-to-end mission.

Earlier bounded experiments reached controllable Roxas and an authored test map. Startup failures in later trials mean a reliable production entry route remains an active engineering problem.

Protecting the ordinary game

The intended Days launcher will start the player's owned KH3 installation and provide its own menu and state. Base KH3 and Re Mind must remain playable. Temporary deployment rollback and save/config inventories are already part of testing, but full save isolation and coexistence are not yet proven.

Next

The immediate priorities are reliable menu entry, input ownership, save routing and gameplay initialization. After that, the aim is one representative mission that can be completed, saved, restarted and compared against the original before expanding content.

Future work includes the full panel system and research into integrating the collection's Days movie scenes at the correct story points. Asset work follows a reuse-first process; original game assets, ROMs, saves and keys are not distributed in project materials.

This log will report evidence, failures and remaining uncertainty alongside each milestone.