Preserve · rebuild · replay
Lost worlds,natively restored.
Carefully reconstructed PC-98 games, packaged for modern systems with their history—and their limitations—intact.
- 03
- Native releases
- 09
- Source-media variants
- 15,000+
- Dialogue lines verified
/ 001 — Preservation method
From magnetic media to native package
A release is the final artifact of a traceable reconstruction process—not a skin over an emulator.
- 01
Ingest
Original media is identified, hashed, and extracted through native PC-98 format tooling.
- 02
Restore
Scripts, fonts, audio, and engine behavior are rebuilt title by title—not wrapped in an emulator.
- 03
Verify
Deterministic route witnesses, content inventories, and clean-package checks gate each release.
- 04
Release
Authorized packages ship with controls, notices, checksums, and a plain-language scope statement.
/ 002 — Release records
What these releases preserve
01 Native desktop runtime+
Each desktop target ships once with Japanese and English inside the same package or executable. The launcher selects language, display mode, release, and input before starting the native runtime.
02 Stateful OPNA playback+
Captured YM2608 register streams play through a long-lived software renderer that retains state across loop events.
03 Recovered gameplay flow+
Scripted event flow, substitutions, menu systems, input handling, map routing, and platform-specific combat scripting are represented natively as reconstructed behavior.
04 Known limitations+
Native save/restore, advanced local-map walking, precise original map hit-testing, and all original battle rendering remain outside this release’s scope.
/ Why native preservation?
Keep the strange edges.
Preservation is more than making old software launch. It means documenting what was understood, what was rebuilt, what changed, and what is still missing. These releases keep that boundary visible.