home · write-ups

Technical write-ups

Each write-up starts from something a player has seen - a randomizer seed, a battle that never ends, a fish that never bites - and follows it down into the disc. The rest of the site is reference; these pages are the narrative: what the finding is, how the mechanism works, and what the project built on it.

Investigations

Single findings followed from the symptom down to the instruction. No reference page is required reading first - each article links out to the byte-level detail where it lives.

The endless camera orbit

What it is about. Anatomy of a retail softlock: the "battle freezes while the camera circles the party" bug, traced to an approach animation that dies with nothing to re-stage it, reproduced on demand, and fixed with a nine-word in-place rewrite.

Why you might care. If Gaza's second fight ever ate a save of yours, this is what happened - and the fix ships in the browser ROM patcher.
The Spirit fish gate

What it is about. Fishing's rarest catch, decompiled: the Spirit's spawn column is not on the dice at all. It sits behind a six-condition strike-time gate, and only one of the four "Good!" reel cadences selects it.

Why you might care. Twenty years of player folklore about the Spirit, each observation mapped to the mechanism that produced it, with the real per-catch probabilities.

Glitches and oversights

A series: the community's glitch list, one page per area of the game, each case traced to its cause.

Glitches and oversights, traced

What it is about. The community's list of Legaia glitches, each followed into the disc's code: the flute that erases a boss's turn, the attack name that sits off-centre, the Incense tick that walks through a cutscene trigger, the summon level that copies Palma's.

Why you might care. Every case gives the cause in plain words, a diagram, and the addresses to check it in a debugger - including the ones the trace could not settle.

Disc patching

A series of seven tiers, read in order: each technique is what the one before it could not do.

Patching a sealed disc

What it is about. How the randomizer rewrites a retail Legaia disc with no source and no SDK - a ladder of seven injection techniques, from same-size byte edits up to hosting a whole new screen in an overlay's dead space and carrying a community RAM patch on disc behind an injected loader.

Why you might care. If you have wondered how a randomizer can exist for a game that was never meant to be modified, this is the answer, one technique per page, with a generated mod catalog + roadmap.

How to read these

  • Each page opens with the finding in plain words, then the mechanism, then a How we know table with the function addresses and dump files.
  • Addresses are PlayStation virtual addresses. 0x8000xxxx is the always-resident executable; 0x801C0000+ is the window the game pages its per-mode overlays into.
  • Register-level walkthroughs sit in collapsed Details blocks - open them when you want the proof.
  • No Sony-owned bytes appear here or anywhere in the repo - only addresses, offsets, and the project's own from-scratch code.

See also

Reference Randomizer / disc patcher ROM patcher (in browser) Static overlay pipeline Shop subsystem Battle action SM Playable minigames