Getting started with the release tools

Bring your own disc

One rule shapes everything here: the project ships no Sony-owned bytes. The archive contains only the project's own compiled tools. Every tool operates on a disc image you supply - a raw Mode 2/2352 .bin dump of your own Legend of Legaia (USA) disc, SCUS-94254. A .cue sheet is accepted anywhere a disc image is: the referenced BINARY track is resolved automatically.

Commands on this page use the bare ./tool form, as run from inside the unpacked archive directory. If you build from source instead, the same binaries land in target/release/ (cargo build --release), so substitute ./target/release/tool.

1 · Download and verify the archive

Each tagged release publishes one archive per platform plus a SHA256SUMS manifest (see tooling/releases.md for how they are built):

• legaia-tools-<version>-x86_64-unknown-linux-gnu.tar.gz (Linux, glibc 2.28+)
• legaia-tools-<version>-aarch64-unknown-linux-gnu.tar.gz (Linux on ARM)
• legaia-tools-<version>-x86_64-pc-windows-gnu.zip (Windows)

sha256sum -c SHA256SUMS --ignore-missing
tar -xzf legaia-tools-<version>-x86_64-unknown-linux-gnu.tar.gz
cd legaia-tools-<version>-x86_64-unknown-linux-gnu
./legaia-extract --version

Every binary answers --version and --help; subcommand help (./asset monster-archive --help) states where each input comes from.

2 · Check your disc image

./disc-extract verify "/path/to/Legend of Legaia (USA).bin"

A good USA dump prints:

[ok] matches: Legend of Legaia (USA) - SCUS-94254

An unrecognized dump (a PAL disc, a re-track, a bad rip) prints an [unknown] line with the computed SHA-256 instead of failing - the extraction tools still run on it, but the fingerprints, offsets, and the randomizer's patches all target the USA build. A file that is not a Mode 2/2352 image at all is rejected up front with not a Mode2/2352 disc image: <path>.

3 · Extract everything in one shot

./legaia-extract "/path/to/Legend of Legaia (USA).bin" --out extracted

On a modern machine this takes about five seconds and writes roughly 1.1 GB. The pipeline runs eight steps: disc verify, ISO9660 walk (the disc's 45 files), PROT.DAT split (1233 entries, named via CDNAME.TXT), per-entry format categorization, streaming sub-asset extraction, streaming-TIM PNG conversion, the TIM-catalog TSVs, CD-XA demux to per-channel WAVs (316 of them), and finally the dialog-font artifacts. Skip flags exist for each slow or optional step: --skip-verify, --skip-png, --skip-xa, --skip-catalog, --skip-font.

What lands where:

extracted/
├── PROT.DAT                 - the game's main archive, raw copy
├── CDNAME.TXT               - entry name map
├── SCUS_942.54              - the game executable (data-table source)
├── MOV/                     - FMV movies (MV1.STR ...)
├── PROT/                    - one file per PROT entry, plus categorize.json
├── streaming/               - sub-assets unpacked from streaming containers
├── XA_WAV/                  - streamed audio, one WAV per channel
├── font/                    - dialog-font atlas + widths (engine + viewer read this)
├── prot_tim_catalog.tsv     - texture inventory (raw TIMs)
└── prot_tim_deep_catalog.tsv - texture inventory (TIMs inside LZS)

The final summary points at the texture path: bulk texture export is a separate two-command step (asset tim-scan + tim convert-dir) covered in extracting assets. Everything downstream - the asset scenarios, the engine and viewers, the modding tools - reads either this extracted/ tree or the disc image directly.

4 · The tools at a glance

Pipeline and per-format extractors:

Game-data, playing, and modding:

Reverse-engineering aids (useful once you go deeper):

See also