Pokédex data structure (Generation III): Difference between revisions
Kyoufu Kawa (talk | contribs) No edit summary |
Kyoufu Kawa (talk | contribs) No edit summary |
||
| Line 17: | Line 17: | ||
| Weight (10<sup>-1</sup> kg) || 2 bytes | | Weight (10<sup>-1</sup> kg) || 2 bytes | ||
|- | |- | ||
| Description | | Description pointers || 2 times 4 bytes | ||
|- | |- | ||
| Pokémon scale || 2 bytes | | Pokémon scale || 2 bytes | ||
| Line 36: | Line 34: | ||
* '''Height''' is measured in decimetres (10<sup>-1</sup> metres), and is then converted to other units in some games. | * '''Height''' is measured in decimetres (10<sup>-1</sup> metres), and is then converted to other units in some games. | ||
* '''Weight''' is measured comes in hectogrammes (10<sup>-1</sup> kilogrammes), it is then converted to other units in some games. | * '''Weight''' is measured comes in hectogrammes (10<sup>-1</sup> kilogrammes), it is then converted to other units in some games. | ||
* '''Description pointers''' show to the game where the description for the particular Pokémon is; remember the GBA is little endian and that a ROM file is loaded at an offset of | * '''Description pointers''' show to the game where the description for the particular Pokémon is; remember the GBA is little endian and that a ROM file is loaded at an offset of 0x08000000. Ruby, Sapphire and Emerald have two pages of text while Fire Red and Leaf Green have only one - the second "description" is an empty string. | ||
* '''Pokémon offset''' is a signed 16-bit integer - if the raw value is greater 0x8000, then it is negative, with 0x8000 as -32,767 and 0xFFFF as -1. | * '''Pokémon offset''' is a signed 16-bit integer - if the raw value is greater 0x8000, then it is negative, with 0x8000 as -32,767 and 0xFFFF as -1. | ||
Revision as of 19:39, 30 June 2007
Specs
A Pokédex data structure is a 34-byte piece of data.
Every Pokémon species in the Generation III games has data stored in the game that is used in Pokédex related functions and by certain moves, such as Low Kick.
| Pokédex Data | |
|---|---|
| Padding | byte |
| Name | 12 bytes |
| Height (10-1 m) | 2 bytes |
| Weight (10-1 kg) | 2 bytes |
| Description pointers | 2 times 4 bytes |
| Pokémon scale | 2 bytes |
| Pokémon offset | 2 bytes |
| Trainer scale | 2 bytes |
| Trainer offset | byte |
| Padding | 2 bytes |
Notes
- Name is 12 bytes long and comes in capital letters. 0x00 fills possible empty bytes.
- Height is measured in decimetres (10-1 metres), and is then converted to other units in some games.
- Weight is measured comes in hectogrammes (10-1 kilogrammes), it is then converted to other units in some games.
- Description pointers show to the game where the description for the particular Pokémon is; remember the GBA is little endian and that a ROM file is loaded at an offset of 0x08000000. Ruby, Sapphire and Emerald have two pages of text while Fire Red and Leaf Green have only one - the second "description" is an empty string.
- Pokémon offset is a signed 16-bit integer - if the raw value is greater 0x8000, then it is negative, with 0x8000 as -32,767 and 0xFFFF as -1.
Size compare function
In Generation III, there is a size page on the Pokédex, which uses data from the Pokédex to create a silhouette of the Pokémon standing next to the trainer. The size of both the trainer and Pokémon are determined by this formula:
x = (y × 256/z) pixels
Where y is the sprite size (64 pixels in our case) and z is the appropriate scale in hex and x rounded down is the size of silhouette. The game then resized the sprite in a way similar a computer would do (without anti-aliasing of course).
The offset determines where exactly the silhouette will be placed. For example if Pokémon offset = 10 then the silhouette of the Pokémon will be 10 pixels from the top and 10 pixels from the left. (for some reason, that cannot be exactly simulated outside of the game).
