Please remember to follow the manual of style and code of conduct at all times.
Check BNN and Bulbanews for up-to-date Pokémon news and discuss it on the forums or in our IRC channel #bulbagarden on irc.systemnet.info.

Difference between revisions of "Pokédex data structure in Generation III"

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to: navigation, search
m
(Specs)
Line 1: Line 1:
 
==Specs==
 
==Specs==
   
A '''Pokédex data structure''' is a 37-byte piece of data.
+
A '''Pokédex data structure''' is a 34-byte piece of data.
   
 
Every [[Pokémon|Pokémon species]] in the [[Generation III]] games has a Pokédex data stored in the game that is used in Pokédex related functions and also by some moves like Low Kick.
 
Every [[Pokémon|Pokémon species]] in the [[Generation III]] games has a Pokédex data stored in the game that is used in Pokédex related functions and also by some moves like Low Kick.
Line 8: Line 8:
 
|-
 
|-
 
! colspan="2" style="text-align: center; background: #ccf;" | '''Pokédex Data'''
 
! colspan="2" style="text-align: center; background: #ccf;" | '''Pokédex Data'''
|-
 
| Effect || byte
 
 
|-
 
|-
 
| Padding || byte
 
| Padding || byte

Revision as of 22:10, 13 June 2005

Specs

A Pokédex data structure is a 34-byte piece of data.

Every Pokémon species in the Generation III games has a Pokédex data stored in the game that is used in Pokédex related functions and also by some moves like Low Kick.

Pokédex Data
Padding byte
Name 12 bytes
Height (10-1 m) 2 bytes
Weight (10-1 kg) 2 bytes
Description pointer start 4 bytes
Description pointer end 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.</li>
  • Description pointers show to the game where the description for the particular Pokémon is; remember the GBA is little endian. The MSB byte is always set to 0x08 (8), so this matches a BRANCH instruction (B) in assembly. For example, if the location is 0x123456, it will appear here as 0x08123456 (56 34 12 08).
  • 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 0xFF as -1.

Size compare function

In the Generation III, there's 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).