Sources
The game’s own code and data are the evidence for every layout and name in this wiki. The external research listed here confirms a fact or gives a lead, and it never replaces a check of the game’s bytes. The tables give each source with its terms, what the wiki took from it and the pages it supports. Pages cite and summarize these sources and copy none of their text or tables.
“Terms” is what the owner states. “None stated” means the page or repository carries no license, so all rights stay with the owner and the source is cited only. A “snapshot” is an archive.org copy of the page when one exists.
Community research
Section titled “Community research”| Source | Terms | What we took | Pages |
|---|---|---|---|
| glitch-in-the-herring/bof3-notes | CC-BY-SA-4.0 | US RAM structures (party, combatants, inventory, Fairy village, fishing) and disassembly notes; confirms layouts; its enemy stride (0x140) is the player row’s, while enemy rows use 0x118 |
records |
| GlitchedDragon-dev/BoF3-Data-Doc | none stated | EMI, overlay, texture and palette notes; confirms the container and graphics layouts | EMI, graphics, records |
| abyssonym/vast_violence | none stated | US data-table offsets and record layouts of the randomizer; confirms table coordinates | records |
| glitch-in-the-herring/bof3-save-editor | none stated | party, inventory and flag layouts through the memory-card format; confirms the save-to-RAM mapping | records |
| glitch-in-the-herring/bof3-script-editor | MIT | area event-script opcodes; they do not describe the 0x800D3800 script table |
area |
duckstation/chtdb: cheats/SLUS-00422.cht |
scripts MIT; cheats held by their authors | only addresses, widths and strides, from about 1,170 decoded US cheat lines; no cheat text is copied | records |
libretro/libretro-database: Breath of Fire III (World) (Game Buster).cht |
CC-BY-SA-4.0 | USA-address cheats; 8 rows of the RAM map cite them, and one duplicated P2 magic address is noted | records |
Web pages
Section titled “Web pages”None of these pages grants a license; they are cited and none of their text or tables is copied.
| Source | What we took | Pages | Snapshot |
|---|---|---|---|
Almar’s Guides, Breath of Fire III CodeBreaker codes (character pages for Ryu, Nina, Garr, Teepo, Rei, Momo and Peco; ModifierCodes) |
US RAM addresses and field meanings, one character at a time; the stride between characters | records | 2026 snapshot; Ryu page, 2024 |
| Almar’s Guides, Action Replay codes | the same addresses through a second code set | records | 2025 snapshot |
| GameShark codes, geocities.ws/Tokyo/Fuji/2280 | a third cheat set; 19 rows of the RAM map cite it | records | none |
| psx-spx (community edition of Martin Korth’s nocash document) | SPU registers, ADPCM, ADSR, Gaussian and reverb tables, CD-ROM XA and sector formats, GPU/VRAM | audio format, STR and XA | SPU, 2026; CD-ROM, 2026; original, 2026 |
| Redump database entry, Breath of Fire III (USA) and its public mirror, which agree | the Redump name, and the size, CRC32, MD5 and SHA-1 of the CUE sheet and both tracks | game version | none |
| Sony, PlayStation File Formats manual (TIM, VAB, SEP) | the TIM file format (chapter 3) | none | none |
Sony SDK
Section titled “Sony SDK”Sony proprietary; none of it is redistributed here.
| Source | Terms | What we took | Pages |
|---|---|---|---|
PsyQ 3.7 (Sony SDK, psyq-370.7z) |
Sony proprietary; not redistributed here | the headers and LIB members the retail link used |
PsyQ SDK, graphics, audio |
ps1_sdks (archive.org; PsyQ 3.5, 3.6, 4.0 redumps) and mkst/esa psyq-binaries (3.3 to 4.6) |
Sony proprietary | export-set comparisons between SDK releases, which show that 3.7 is the retail release | PsyQ SDK |
How a fact cites its source
Section titled “How a fact cites its source”- A layout or name read from the game’s data cites a function as
Name (image@0xADDR)(conventions). An external source, if any, confirms it. - A page that rests on a community source names it in the
Evidencebullet of its “Sources and confidence” section and links this page. - A fact that only a community source states is a lead, tagged
[inferred](conventions), until a read of the game’s own code or data confirms it.