Talk:Save data structure (Generation III): Difference between revisions

no edit summary
(Created page with "Adding 0x0498 to the Trainer section's address you'll get into the battle trainer (e-Reader trainer) section. The first 2 bytes are used for the sprite which will also determ...")
 
No edit summary
Line 1: Line 1:
Adding 0x0498 to the Trainer section's address you'll get into the battle trainer (e-Reader trainer) section.  
Adding 0x0498 to the Trainer section's address you'll get into the battle trainer (e-Reader trainer) section.  
The first 2 bytes are used for the sprite which will also determine how the trainer looks like ingame. Afterwards, after you leave out 2 bytes (i don't know what they do, they are not set for me), the name will follow, using up to 12 bytes while it has to be terminated by FF. Now the values used for the dialogue, the Pokémon, their moves and their names, including items they carry are saved afterwards. At 0x0550 the checksum of the subsection (4-bytes long) is being saved (you can get it by simply following the instruction for the checksum and leaving the last two steps out). Maybe someone can help me getting a clearer structure and add it to the wiki page after we're finished investigating.
The first 2 bytes are used for the sprite which will also determine how the trainer looks like ingame. Afterwards, after you leave out 2 bytes (i don't know what they do, they are not set for me), the name will follow, using up to 12 bytes while it has to be terminated by FF. Now the values used for the dialogue, the Pokémon, their moves and their names, including items they carry are saved afterwards. At 0x0550 the checksum of the subsection (4-bytes long) is being saved (you can get it by simply following the instruction for the checksum and leaving the last two steps out). Maybe someone can help me getting a clearer structure and add it to the wiki page after we're finished investigating.
[[User:Fighter19|Fighter19]] ([[User talk:Fighter19|talk]]) 22:11, 27 February 2014 (UTC)
2

edits