Pokédex data structure (Generation III)

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search

Specs

APokédex data structure is a 36-byte (32-byte for Pokémon Emerald) piece of data.

EveryPokémon species in theGeneration III games has data stored in the game that is used inPokédex related functions and by certain moves, such asLow Kick.

Pokédex Data
Category12 bytes
Height (10-1 m)2 bytes
Weight (10-1 kg)2 bytes
Description pointer #14 bytes (See Notes)
Description pointer #24 bytes (See Notes)
Padding2 Bytes
Pokémon scale2 bytes
Pokémon offset2 bytes
Trainer scale2 bytes
Trainer offset2 bytes
Padding2 Bytes

Notes

  • Category is 12 bytes long and comes in capital letters. 0x00 fills possible empty bytes.
    • InPokémon FireRed and LeafGreen's version 1.0 release, any 0x00 byte was read as a terminator instead of a space, no matter if there were any nonzero bytes afterward. This was fixed in the version 1.1 release and all European-language releases.
  • Height is measured in decimeters (10-1 meters), and is then converted to other units in specific versions of games.
  • Weight is measured comes in hectograms (10-1 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.
    • 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.

Size compare function

InGeneration 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 this case) and z is the appropriate scale in hex and x rounded down is the size of silhouette. The game then resizes the sprite in a way similar a computer would do (without anti-aliasing).

The offset determines where exactly the silhouette will be placed. For example ifPoké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).

Offsets

Ruby: 0x083B1858
Sapphire: 0x083B18B0
Emerald: 0x0856B5B0
FireRed: 0x0844E850
LeafGreen: 0x0844E270

Fingerprint

For Ruby/Sapphire:

cf c8 c5 c8 c9 d1 c8 ff 00 00 00 00 00 00 00 00 59 04 3a 08 a2 04 3a 08 00 00 00 01 00 00 00 01 00 00 00 00  // -cd bf bf be ff 00 00 00 00 00 00 00 07 00 45 00 d5 04 3a 08 24 05 3a 08 00 00 64 01 11 00 00 01 00 00 00 00  // BULBASAURcd bf bf be ff 00 00 00 00 00 00 00 0a 00 82 00 67 05 3a 08 d5 05 3a 08 00 00 4f 01 0d 00 00 01 00 00 00 00  // IVYSAURcd bf bf be ff 00 00 00 00 00 00 00 14 00 e8 03 4a 06 3a 08 c0 06 3a 08 00 00 00 01 00 00 84 01 06 00 00 00  // VENUSAURc6 c3 d4 bb cc be ff 00 00 00 00 00 06 00 55 00 01 07 3a 08 73 07 3a 08 00 00 bc 01 12 00 00 01 00 00 00 00  // CHARMANDERc0 c6 bb c7 bf ff 00 00 00 00 00 00 0b 00 be 00 be 07 3a 08 26 08 3a 08 00 00 2e 01 09 00 00 01 00 00 00 00  // CHARMELEONc0 c6 bb c7 bf ff 00 00 00 00 00 00 11 00 89 03 8c 08 3a 08 f0 08 3a 08 00 00 00 01 01 00 2e 01 03 00 00 00  // CHARIZARD...

Related articles

EntriesPokédex entryPokédex entry recyclingForeign Pokédex entry
Numbering
systems
National Pokédex (list)

Regional Pokédexes:
KantoNewJohto • Hoenn (Gen III ·Gen VI) •Sinnoh • Unova (BW ·B2W2)
Central KalosCoastal KalosMountain Kalos • Alola (SM ·USUM)
GalarIsle of ArmorCrown TundraHisuiPaldeaKitakamiBlueberryLumioseHyperspace
Unown ModeUnown Research NotesMega Evolution

Similar toolsColosseum/XD:Strategy MemoMasters:Dex (list of sync pairs)
Ranger series:Regional Browser (Fiore ·Almia ·Oblivia ·No Browser ·Every Browser)
Conquest:Gallery (list) •Duel:Library numberPokéPark series:Pad number
New Snap:Photodex (list) •Sleep:Sleep Style DexTrozei series:Pokémon List (Shuffle list number)
TCG:DPBP numberGoogle Maps:Pokémon Challenge
ModelsRotom Pokédex (Pokémon the Series ·Adventures) •Rotom Phone (Old Roto)
Data structurePokédex data structure (Generation III)Pokédex flags
DevicesGen I:Pokémon PokédexGen II:Deluxe PokédexGen III:Cyber Pokédex
Gen IV:Pokémon Diamond and Pearl Electronic Talking PokédexGen V:Electronic Pokédex
AppsGen V:Pokédex 3D (Pro) •Pokédex for iOS
In other gamesSide series:Stadium seriesHOME
Spin-offs:Pinball series
In the TCGPokédexNew PokédexPokéDex HANDY909
Pokédex HANDY910isRotom DexRotom Dex Poké Finder Mode
Data structure in thePokémon games
GeneralCharacter encoding
Generation IPokémon speciesPokémonPoké MartCharacter encoding (Stadium) •Save
Generation IIPokémon speciesPokémonTrainerCharacter encoding (StadiumKorean) •Save
Generation IIIPokémon species (EvolutionPokédexType chart)
Pokémon (substructures) •MoveContestContest moveItem
Trainer TowerBattle FrontierCharacter encoding (GameCube) •Save
Generation IVPokémon species (EvolutionLearnsets)
PokémonSaveCharacter encoding (Wii)
Generation V–presentCharacter encoding
Generation VIIISave
TCG GB andGB2Character encoding
This data structure article is part ofProject Games, aBulbapedia project that aims to write comprehensive articles on thePokémon games.