Trainer data structure (Generation II): Difference between revisions

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
mNo edit summary
Line 13: Line 13:
0x15D1: padding, 3 bytes. All 0x00.
0x15D1: padding, 3 bytes. All 0x00.


{{gamestub}}
{{Stub|Game}}
{{data structure}}
{{data structure}}

Revision as of 06:17, 6 September 2009

050Diglett.png This article is incomplete.
Please feel free to edit this article to add missing information and complete it.

0572Minccino.png This article does not yet meet the quality standards of Bulbapedia. Please feel free to edit this article to make it conform to Bulbapedia norms and conventions.

Length: unknown.

Start: 0x15C7?


0x15C7: ID number, 2 bytes. Raw hex.

0x15C9: Name, 8 bytes. Uses special text format (0x80 is A, 0xA0 is a). Terminated with 0x50. If the name is shorter than 7 characters, the end will be padded with 0x00 bytes.

0x15D1: padding, 3 bytes. All 0x00.

Red EN boxart.png This game-related article is a stub. You can help Bulbapedia by expanding it.


Data structure in the Pokémon games
General Character encoding
Generation I Pokémon speciesPokémonPoké MartCharacter encodingSave
Generation II Pokémon speciesPokémonTrainerCharacter encoding (Korean) • Save
Generation III Pokémon species (EvolutionPokédexType chart)
Pokémon (substructures) • MoveContestContest moveItem
Trainer TowerBattle FrontierCharacter encoding (GameCube) • Save
Generation IV Pokémon species (EvolutionLearnsets)
PokémonSaveCharacter encoding (Wii)
Generation V–present Character encoding
Generation VIII Save
TCG GB and GB2 Character encoding