Skip to content

Breath of Fire III: game specifications

Independent research on how Breath of Fire III (US, PlayStation, SLUS-00422) stores and runs its data.

This site covers file formats, memory layouts, record tables, text encoding and the code that reads them. It is for modders and fans who know some PlayStation basics but not this game. Every page states layouts, offsets, values and limits, and marks what is unknown.

  1. One resident program. SLUS_004.22 loads at boot and stays in RAM until power-off. It holds the main loop, the loader, the graphics and sound drivers and the shared helpers (programs).
  2. Overlays. All other code streams from .EMI archives on the disc into fixed RAM windows. A window holds one overlay at a time: the battle program, a scenario controller or the program of one map (loading, memory map).
  3. Data tables. Items, abilities, enemies, text, maps and sound are payloads inside the archives. The game reads them through fixed tables and offsets (game records, game text).

An EMI archive is a sector-aligned list of typed entries (EMI container). Each entry names the RAM address it loads at, so one archive can carry code, data, textures and audio.

  1. Read Notation and conventions once. It defines the number formats, field types, citations and the two evidence tags.
  2. Read the architecture overview for one run from power-on to a running frame.
  3. Read the memory map, the frame loop, the scheduler and loading. Every system page builds on them.
  4. Pick the system you need from Systems: boot, phases, scenario, areas, battle, screens, UI, rendering, audio, saving and state.
  5. Look up byte layouts in Formats and table rows in Data tables.
  6. Change something with a guide. Each guide links to the pages that own the facts.

The glossary defines every term. Open questions lists what the pages do not establish, and sources lists where claims come from.

Concepts

The model every page assumes: notation, memory map, frame loop, scheduler and loading.

Systems

How each part runs: boot, phases, scenario, areas, battle, screens, UI, rendering, audio, saving.

Formats

Byte layouts of the files on the disc, from the EMI container to the memory card save.

Data tables

Row layouts, counts and strides of the tables the game reads at run time.

Guides

How to change text, items, characters, sound, maps, graphics and saves, and what to keep intact.

Appendix

Glossary, open questions, documentation coverage and sources.

You want to Read
Read a number, offset or citation Notation and conventions
Understand how the game runs Architecture overview, then boot and frame loop
Read a file format EMI container, then graphics, audio, areas
Edit items, skills, enemies or shops Edit items, skills and shops, edit characters and enemies, game records
Edit text or dialogue Edit text and dialogue, game text
Edit music, sound effects or voices Edit sound and music, audio formats, STR and XA, audio system
Edit maps and scenes Edit maps and scripts, area formats, areas and the field, scenario engine
Edit textures and sprites Edit graphics and textures, character sprites
Edit or inspect a save Edit saves, memory card save
Look up the battle or field data in RAM Battle records, field and party records
Find a term Glossary
See where a fact comes from Sources

The pages describe one release, the US disc SLUS-00422. Game version lists its Redump checksums.

The site holds no game data and no game assets. Breath of Fire and the game belong to Capcom, and the PlayStation belongs to Sony; they keep their rights. This site is independent and is not affiliated with or endorsed by either company.