317
edits
Pokédex data structure (Generation III): Difference between revisions
Pokédex data structure (Generation III) (view source)
Revision as of 16:11, 1 December 2016
, 1 December 2016no edit summary
(→Specs: Added padding) |
No edit summary |
||
| Line 37: | Line 37: | ||
* '''Weight''' is measured comes in hectograms (10<sup>-1</sup> kilograms), and is then converted to other units in specific versions of games. | * '''Weight''' is measured comes in hectograms (10<sup>-1</sup> kilograms), and is then converted to other units in specific versions of games. | ||
* '''Description pointers''' show the game where the description for the particular Pokémon is. The GBA is Little Endian, and that a ROM file is loaded at an offset of 0x08000000. | * '''Description pointers''' show the game where the description for the particular Pokémon is. The GBA is Little Endian, and that a ROM file is loaded at an offset of 0x08000000. | ||
:Ruby | :Ruby and Sapphire, being the only games that have two pages of text, are the only games that use both. FireRed and LeafGreen have the second description pointer pointing to an empty string which is never read, and Emerald removed Description pointer #2 entirely. | ||
* '''Pokémon offset''' is a signed 16-bit integer; therefore, if the raw value is 0x8000 or greater, then it is negative, with 0x8000 as -32,768 and 0xFFFF as -1. | * '''Pokémon offset''' is a signed 16-bit integer; therefore, if the raw value is 0x8000 or greater, then it is negative, with 0x8000 as -32,768 and 0xFFFF as -1. | ||