Trainer data structure (Generation II): Difference between revisions

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to navigationJump to search
(BAD HTML tags. Use CSS instead. Also, cleaned up the article.)
Line 5: Line 5:


{|style="text-align: left; margin: auto; border: 1px solid #88a; background: #f8f8ff; padding: 0.5em; border-collapse: collapse; float: right; width: 250px; padding-left:5px;" cellspacing="1" cellpadding="2"
{|style="text-align: left; margin: auto; border: 1px solid #88a; background: #f8f8ff; padding: 0.5em; border-collapse: collapse; float: right; width: 250px; padding-left:5px;" cellspacing="1" cellpadding="2"
! style="text-align: center; background: #ccf;" | Name
! style="text-align: center; background: #{{johto color}};" | Name
! style="text-align: center; background: #ccf;" | Length
! style="text-align: center; background: #{{johto color}};" | Length
|-
|-
| Name
| Name

Revision as of 12:55, 5 September 2010

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.

NPC trainer data

Name Length
Name 2-8 bytes
Name string 1-7 bytes
Terminator 1 byte
Custom move marker 1 byte
Pokémon 2-36 bytes
Level 1 byte
Species 1 byte
Moveset 4 bytes
Terminator 1 byte

The in-game trainer data is remarkably compressed.

Name

This is a string going anywhere from 2 to 8 bytes, containing the trainer's name and ending in a 0x50 terminator. The rival's name is represented by a single byte - 0xe6.

Custom move marker

This is one byte marking whether the Pokémon in the party have custom moves or not. If not, it is set to 0 - if so, it is set to 1.

Pokémon

Depending on whether the custom move marker was set or not, each Pokémon's data is either 2 or 6 bytes long. If the move marker was set to 0, the Pokémon's data simply contains the Pokémon's level and species, in that order. Otherwise, it contains the full moveset after the level and species - 1 byte per move.

Terminator

This is a single byte (0xff) which tells the processor to stop reading data.

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 (Pokémon evolutionPokédexType chart)
Pokémon (substructures) • MoveContestContest moveItem
Trainer TowerBattle FrontierCharacter encodingSave
Generation IV Pokémon species (Pokémon evolutionLearnsets)
PokémonSaveCharacter encoding
Generation V–present Character encoding
TCG GB and GB2 Character encoding