An independent fan remake
Rebuilding the journey of 358/2 Days.
Days gameplay. A KH3 foundation.
Faithful by design. Verified through play.
Our production standard: original-game research, repeatable comparisons and full-campaign verification. The first engineering milestones behind the remake.
Read the development log ↗The project
We are rebuilding Kingdom Hearts 358/2 Days on the Kingdom Hearts III runtime foundation. Our mandate is clear: preserve Days’ gameplay, missions, panels, progression and encounters while bringing its presentation forward.
Our intended Days launcher will use the player's owned KH3 installation, with separate Days state and an ordinary KH3 launch option. Base KH3 and Re Mind must remain playable.
Movie cutscenes from the collection are also part of the research roadmap, alongside reuse and adaptation of compatible assets.
Record controlled experiments. Measure behavior before deciding how to reproduce it.
Reliable entry, menus, player systems and separate save ownership.
Connect combat, objectives, rewards and persistence before expanding content.
Bring the campaign together and test the full journey from a clean save.
The original Days is our specification. Our goal is to preserve its rules, missions and progression within a modern presentation. This standard guides implementation, testing and every decision about the remake.
Movement, combo timing, magic, Limit Breaks, damage and boss patterns. Panel placement, links and statistics. Mission objectives, spawns, rewards and room layouts. We study the original directly and record what it does.
Repeat recorded inputs from controlled states, then test the equivalent scenario in the remake. Compare timing, movement, damage and mission state. Correct discrepancies and rerun earlier checks. Reference experiments are underway; full paired gameplay coverage remains ahead.
First, one complete mission. Then a clean-save playthrough through the campaign, checking unlocks, bosses, transitions and saves after restarting. Document intentional presentation changes and every unresolved gameplay difference.
A diagnostic widget displayed inside KH3. Bounded Roxas and test-map experiments. Repeatable original-game menu and movement observations.
Menu navigation is implemented. Current integration focuses on artwork, controller input, game entry and separate save routing, followed by in-game verification.
The next production gate is a complete, tested mission. Panel systems, combat fidelity and campaign content follow the dependency roadmap, with a full playthrough required before release.