**HUMAN**
After this clearly marked section, the rest of this post is all written by AI (Gemini Neon), but this is my human-shaped spot in the loop:
I spent so much time and money (video game rentals at the video store) playing Phantasy Star IV on the Genesis when I was a kid. It was a huge part of my video game childhood and I wanted to attempt to make something cool for others who felt the same. So, for the past few months, me and various agents via various providers and models have been working on a native Rust + Godot port of the game as it was in 1993. I started with GPT 5.6 Sol which laid out a good foundation and took me decently far, but it got to be a little more infrastructure and less progress at a point. I believe GPT 6 moved things forward a little, but once Opus 5.5 was released, progress moved from maybe 40-50% to around 90%. Gemini 4 Neon (amazing model) got me to today's finish line which got me brave enough to tell others about it.
This is the full US retail campaign playable from start-to-finish natively rebuilt from the OG 68000 disassembly. We built a system where we could compare what the output via an actual emulator was vs the output from our engine. Most of my input was just getting the project organized and the rules set for agents to work. Once that was created, it took a lot of time and tweaking, but here we are.
Assets for the game are not included in the project so you'll have to find the ROM on your own to play. Otherwise, I'd get yelled at. Once you have the right ROM, the game will ask you to provide it, extract the data from the ROM where it needs to go, and then you should, in theory (and in somewhat limited testing) be playing Phantasy Star IV as it was back in the day.
**NOT HUMAN**
**GitHub:** https://github.com/TusanHomichi/PSIV
**Downloads (Linux, Windows, macOS):** https://github.com/TusanHomichi/PSIV/releases/latest
---
### What it is (and isn't)
- **Not an emulator.** A built-in Rust pack builder extracts graphics, maps, sound, dialogue, and battle tables once from your own US Genesis/Mega Drive ROM into a local data pack. At runtime, Rust executes the game rules frame by frame (`psiv-core` / `psiv-runtime`), Godot handles rendering and input (`psiv-godot`), and Nuked OPN2 (`ym3438.c`) + PSG synthesize the FM/PSG audio natively.
- **Zero copyrighted assets in the repo or releases.** You supply your own unheadered US retail ROM once on the first-run setup screen (click **Choose your ROM file** or drag and drop it onto the window). PSIV verifies the SHA-256, builds its data pack in a few seconds into your user data folder, and boots straight to the title screen.
- **Original behavior, quirks included.** Rules are reconstructed from the 68000 disassembly (`ps4disasm`) and verified against a Genesis Plus GX cartridge oracle rather than guessed from RPG conventions. A handful of deliberate retail-bug fixes are documented in `docs/source-notes/README.md`.
### How it was verified (keeping AI agents honest)
The hardest part of building a large project with coding agents isn't writing code — it's preventing plausible-looking drift. Most of the leverage came from making the repo self-checking:
- **End-to-end 84-chapter campaign replay:** An automated playthrough pressing the same buttons a player does completes New Game through the Ending and its final Start press in 84 chapters. The native runtime replays all 84 chapters in one continuous input tape with **84/84 chapter saves matching byte for byte**.
- **Cartridge oracle & battle replays:** Every player technique/skill and all 83 distinct regular enemy abilities through the final boss are implemented from cartridge code and cross-checked against recorded emulator RAM/RNG/damage traces.
- **Pixel-exact visual certification:** 62/62 certified scene pairs across title, battle, comic-panel cutscenes, field, camp menus, and shops currently render at **RMSE = 0.000000** against matching cartridge frames (see the side-by-side captures attached).
- **Automated suite & repo guards:** 3,208 Rust tests, 2,028 Python tests, plus automated guards that block accidental ROM table copies, enforce strict Rust-core vs. Godot-shell boundaries, and validate disassembly citations and docs.
To be upfront about what's *not* finished yet: some animations, whole-scene staging, and audio timing still differ from the cartridge in places — every known gap is tracked openly under [`gameplay-fidelity`](https://github.com/TusanHomichi/PSIV/issues?q=is%3Aissue+is%3Aopen+label%3Agameplay-fidelity) and [`presentation`](https://github.com/TusanHomichi/PSIV/issues?q=is%3Aissue+is%3Aopen+label%3Apresentation) issues.
### Try it (or point your own AI assistant at the repo)
Prebuilt downloads are up for **Linux (x86-64)**, **Windows (64-bit)**, and **macOS (Universal — Apple Silicon & Intel)** — no Rust, Godot, or Python install required. *(Note: Linux has been played extensively on real hardware; Windows and macOS archives are built and first-run smoke-tested on native CI runners, so Windows/macOS playtest reports are especially welcome!)*
The repo is also wired up so you can point your own AI assistant or coding agent straight at `https://github.com/TusanHomichi/PSIV
- **"Get PSIV set up for me"** — `docs/PLAYING.md` tells your assistant to grab the prebuilt release for your OS (instead of compiling from source), verify `SHA256SUMS.txt`, check your local ROM hash, and launch it for you.
- **"I hit something weird — file a bug report"** — `docs/REPORTING.md` tells it where your `logs/godot.log` and save slots live, what never to attach, and how to file a clean, structured GitHub issue.
- **"Help me contribute / fix an issue"** — `CONTRIBUTING.md`, `AGENTS.md`, and `docs/FEATURE_MAP.md` point agents straight to owning files, focused tests, what runs with vs. without a ROM, and the PR/CI rules.
Happy to answer questions about the Rust/Godot architecture, the cartridge oracle setup, or what worked (and didn't) managing AI coding agents on a project this size!