Pokémon DP Save File Structure - Revision history

UniqueGeek: Redirect

2017-10-14T22:12:00Z

Redirect

UniqueGeek at 00:25, 3 February 2017

2017-02-03T00:25:11Z

← Older revision		Revision as of 00:25, 3 February 2017
Line 449:		Line 449:
	[[Category:Game Mechanics]]		[[Category:Game Mechanics]]
	[[Category:Technical References]]		[[Category:Technical References]]
			[[Category:Save Data]]
			[[Category:Gen 4]]

Nerketur: changed links from word_(computing) to point to the actual page Word_(computer_architecture) instead of the disambiguation page.

2015-01-21T11:16:45Z

changed links from word_(computing) to point to the actual page Word_(computer_architecture) instead of the disambiguation page.

← Older revision		Revision as of 11:16, 21 January 2015
Line 89:		Line 89:
	===Trainer Name - 0x64===		===Trainer Name - 0x64===
	*8 unsigned 16bit integers.		*8 unsigned 16bit integers.
	*Each {{wplink\|~~word_~~(~~computing~~)\|word}} represents a character in the game's [[Pokémon NDS Character Table\|character table]].		*Each {{wplink\|Word_(computer_architecture)\|word}} represents a character in the game's [[Pokémon NDS Character Table\|character table]].

	===Trainer ID - 0x74===		===Trainer ID - 0x74===
Line 278:		Line 278:
	===Rival's Name - 0x25A8===		===Rival's Name - 0x25A8===
	*8 unsigned 16bit integers.		*8 unsigned 16bit integers.
	*Each {{wplink\|~~word_~~(~~computing~~)\|word}} represents a character in the game's [[Pokémon NDS Character Table\|character table]].		*Each {{wplink\|Word_(computer_architecture)\|word}} represents a character in the game's [[Pokémon NDS Character Table\|character table]].

	===Map X Coordinate - 0x25FA===		===Map X Coordinate - 0x25FA===

CuleX: Added to category technical references

2010-04-29T13:40:59Z

Added to category technical references

← Older revision		Revision as of 13:40, 29 April 2010
Line 448:		Line 448:
	[[Category:Structures]]		[[Category:Structures]]
	[[Category:Game Mechanics]]		[[Category:Game Mechanics]]
			[[Category:Technical References]]

CuleX: Added lotto flag and number location

2010-04-29T13:28:58Z

Added lotto flag and number location

← Older revision		Revision as of 13:28, 29 April 2010
Line 211:		Line 211:
	===Starter Pokémon - 0xDFC===		===Starter Pokémon - 0xDFC===
	The [[Nationaldex\|Pokédex]] number of the starter chosen.		The [[Nationaldex\|Pokédex]] number of the starter chosen.
			*Unsigned 16bit integer.

			===Lotto number - 0xE14===
	*Unsigned 16bit integer.		*Unsigned 16bit integer.

	===Fly Locations - 0x1112===		===Fly Locations - 0x1112===
	*9byte bit field		*9byte bit field

			===Has obtained lotto prize - 0x1131===
			*1 if obtained, 0 if not yet obtained

	===Pokétch Enabled (?) - 0x114C===		===Pokétch Enabled (?) - 0x114C===

Codemonkey85: /* Map ID Number - 0x1238 */

2009-08-15T15:02:55Z

Map ID Number - 0x1238

← Older revision		Revision as of 15:02, 15 August 2009
Line 256:		Line 256:

	===Map ID Number - 0x1238===		===Map ID Number - 0x1238===
			{{main\|List of Maps}}
	*Unsigned 16bit integer.		*Unsigned 16bit integer.

Codemonkey85 at 14:58, 15 August 2009

2009-08-15T14:58:06Z

← Older revision		Revision as of 14:58, 15 August 2009
Line 168:		Line 168:

	===General Items - 0x624===		===General Items - 0x624===
			{{main\|Other items}}
	The items in the Trainer's general Items bag pocket.		The items in the Trainer's general Items bag pocket.
	*165 blocks of 4 byte structures (two bytes for [[item index]], two bytes for quantity)		*165 blocks of 4 byte structures (two bytes for [[item index]], two bytes for quantity)

	===Key Items - 0x8B8===		===Key Items - 0x8B8===
			{{main\|Key items}}
	The items in the Trainer's Key Items bag pocket.		The items in the Trainer's Key Items bag pocket.
	*50 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).		*50 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).

	===TMs & HMs - 0x980===		===TMs & HMs - 0x980===
			{{main\|TMs and HMs}}
	The items in the Trainer's TMs & HMs bag pocket.		The items in the Trainer's TMs & HMs bag pocket.
	*100 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).		*100 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).
Line 181:		Line 184:

	===Mail - 0xB10===		===Mail - 0xB10===
			{{main\|Mail}}
	The items in the Trainer's Mail bag pocket.		The items in the Trainer's Mail bag pocket.
	*12 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).		*12 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).

	===Medicine - 0xB40===		===Medicine - 0xB40===
			{{main\|Medicine}}
	The items in the Trainer's Medicine bag pocket.		The items in the Trainer's Medicine bag pocket.
	*40 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).		*40 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).

	===Berries - 0xBE0===		===Berries - 0xBE0===
			{{main\|Berries}}
	The items in the Trainer's Berries bag pocket.		The items in the Trainer's Berries bag pocket.
	*64 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).		*64 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).
Line 194:		Line 200:

	===Balls - 0xCE0===		===Balls - 0xCE0===
			{{main\|Pokéballs}}
	The items in the Trainer's Balls bag pocket.		The items in the Trainer's Balls bag pocket.
	*15 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).		*15 blocks of 4 byte structures (two bytes for item index, two bytes for quantity).

	===Battle Items - 0xD1C===		===Battle Items - 0xD1C===
			{{main\|Battle items}}
	The items in the Trainer's Battle Items bag pocket.		The items in the Trainer's Battle Items bag pocket.
	*56 (?) blocks of 4 byte structures (two bytes for item index, two bytes for quantity).		*56 (?) blocks of 4 byte structures (two bytes for item index, two bytes for quantity).

	===Starter Pokémon - 0xDFC===		===Starter Pokémon - 0xDFC===
	The [[Pokédex]] number of the starter chosen.		The [[Nationaldex\|Pokédex]] number of the starter chosen.
	*Unsigned 16bit integer.		*Unsigned 16bit integer.

Codemonkey85: /* Loading/Saving A Save File */

2009-07-18T16:29:08Z

Loading/Saving A Save File

← Older revision		Revision as of 16:29, 18 July 2009
Line 69:		Line 69:
	== Loading/Saving A Save File ==		== Loading/Saving A Save File ==

	When ~~the~~ game ~~loads~~ the ~~save file~~, ~~it first compares the save index number~~ of ~~each small block. If the small block with~~ the ~~highest~~ save ~~index number has a correct checksum, then the game checks~~ to ~~see which big block has a matching ID number~~. ~~If both big blocks have~~ the ~~same ID number as the small block~~, ~~then the big block with~~ the ~~highest save index number~~ is ~~chosen. If~~ the ~~big block chosen by~~ the save file ~~has a correct checksum, then the game loads successfully~~. ~~If the checksum~~ is ~~incorrect in either the small or big block, the game reverts~~ to ~~the other block pair. If either of their checksums are incorrect, then no data is loaded, and~~ a ~~new game must be started~~.		When one starts a new game for the very first time, every byte of the save file is set to 0xFF. The first time the game is saved, the "current" info is written to the second half of the save file. This is important to note when loading a save.

	When the game ~~saves data~~, the save ~~index number~~ is ~~incremented + 1 from~~ the ~~current~~ save ~~index number~~, and the ~~backup small~~ block is ~~overwritten with~~ the new ~~data~~.		When the game loads a save file, it first compares the small block save count of both general blocks. If the general block with the highest save count has a correct checksum, then the game moves on to check the storage blocks. The storage block with the highest storage block save count is chosen first, and if its general block save count matches the currently chosen general block (and has a correct checksum), the file is successfully loaded. If both storage blocks have the same storage block save count, then the storage block with a higher general block save count is chosen instead, and the if the checksum is correct, the file is successfully loaded. If the checksum was incorrect for either block, the game falls on the other pair of general and storage blocks; if the checksums are correct in both, the game reports a save file corruption error, and that is the data loaded. If the checksum in either block is incorrect, the game reports a save file corruption error, and the save file is not loaded. A new game must be started at that point.

	If nothing in the ~~big~~ block has changed, then the ~~save ID number in both blocks is retained~~. However, if changes have been made to the ~~big~~ block, then the backup ~~big~~ block is overwritten with the new data, and ~~a new save ID number is generated~~, ~~which is then written to~~ the ~~new small~~ block. This is the reason why the game varies on how long it takes to save.		When the game saves data, the general block save count is incremented + 1. If nothing in the storage block has changed, then no changes are made to the storage block and no further changes are made to the general block. However, if changes have been made to the storage block, then the storage block save count is incremented by 1 in both the storage block and general block footers. At this point, the backup general block is overwritten with the new general block data, and (if changes were made to the storage block), the backup storage block is also overwritten. This is the reason why the game varies on how long it takes to save.

	Thus, either ~~small~~ block can be linked with either ~~big~~ block, and the current pair is identified using the footer information.		Thus, either general block can be linked with either storage block, and the current pair is identified using the footer information.

	==Small block offsets==		==Small block offsets==

Codemonkey85: /* Block Footers */

2009-07-18T16:12:40Z

Block Footers

← Older revision		Revision as of 16:12, 18 July 2009
Line 21:		Line 21:
	\|- style="background: #eee;" align="center"		\|- style="background: #eee;" align="center"
	\| 0x00 - 0x03		\| 0x00 - 0x03
	\| Save ~~ID number~~		\| Storage Block Save Count
	\|- style="background: #eee;" align="center"		\|- style="background: #eee;" align="center"
	\| 0x04 - 0x07		\| 0x04 - 0x07
	\| Save ~~index number~~		\| General Block Save Count
	\|- style="background: #eee;" align="center"		\|- style="background: #eee;" align="center"
	\| 0x08 - 0x0B		\| 0x08 - 0x0B

Codemonkey85 at 23:37, 10 June 2009

2009-06-10T23:37:23Z

← Older revision		Revision as of 23:37, 10 June 2009
Line 387:		Line 387:
	*Unsigned 16bit integer		*Unsigned 16bit integer
	*Max value = 9999 (0x270F)		*Max value = 9999 (0x270F)

			===Capsules in PC - 0x6050===
			*12 blocks of 24 bytes structures.

	===Battle Points - 0x65F8===		===Battle Points - 0x65F8===
	*Unsigned 16bit integer		*Unsigned 16bit integer
	*Max value = 9999 (0x270F)		*Max value = 9999 (0x270F)

	~~===Capsules in PC - 0x6050===~~
	*12 blocks of 24 bytes structures.

	===Safari Zone Pokémon - 0x72D0===		===Safari Zone Pokémon - 0x72D0===