Difference between revisions of "Pikmin 2 save file"

From Pikmin Technical Knowledge Base
Jump to: navigation, search
m (fixed typo)
Line 38: Line 38:
 
| <code>0x58D</code> || 13 length 1 byte array
 
| <code>0x58D</code> || 13 length 1 byte array
 
| Same as above, only for Exploration Kit treasures including The Key.
 
| Same as above, only for Exploration Kit treasures including The Key.
 +
|-
 +
| <code>0x834</code> || 4 bytes
 +
| Actual Poko count the game registers, differing from what is displayed on the file select screen
 
|}
 
|}
  

Revision as of 16:26, 17 November 2018

Data about the Pikmin 2 save file format. The following info was taken from the European version of Pikmin 2 based on a .gci save taken from Dolphin.


To do: Figure out how to decrypt save files for the NPC version

To do: Check if this info applies to the JP version of Pikmin 2 on GC

The save file contains save data for each of the 3 save slot used in-game. The data of such a save slot starts with the 8 byte magic word string PlVa0003 and is 0xC000 bytes (49152 bytes in decimal) long. Directly after the string follows a byte which has the slot number of the save (0x00 for first slot, 0x01 for second, 0x02 for third). The last 4 bytes of the slot data contain the checksum calculated for the preceding slot data. The checksum is detailed in this section.

Addresses

Addresses of interest relative to the start of the save slot (i.e. the start of the magic word string):

Address Size Description
0x14 4 bytes Integer representing the day count as shown on the file select screen (might not be permanent, i.e. overwritten when you end a day normally.)
0x2C 4 bytes Integer representing the Poko count as shown on the file select screen.
0x30 4 bytes Integer representing the treasure count as shown on the file select screen. Usually the same as the amount of treasures as accessed on the Area Select Screen.
0x3C 4 bytes Integer representing the time (in minutes) played on the save file as shown on the file select screen.
0x164 array of 4 bytes and 1 byte separators, unsure of length[unsure] Appears to be 4 byte enemy data of Pikmin lost to said enemy and amount of enemies of that species killed, followed by a 1 byte separator[unsure].

To do: Figure this out

0x3ED 2 bytes Bitmask for Exploration Kit items and their activity. The least significant bit represents the EK item with an internal ID of 0 When the bit is set to 1, the item is active. This activity does not reflect the treasure being collected.
0x3F1 21 length 4 byte array Pikmin types that fall from the sky during entering and exiting a cave. Editing this value on a save file that is on the area select screen will result in the Pikmin falling from the sky upon entering an area. The Pikmin types are organized into groups of three, with the first integer representing a leaf Pikmin, the second a bud Pikmin, and the third a flower Pikmin. The Pikmin types in the array are ordered Blue, Red, Yellow, Purple, White, Bulbmin, and an unused PikPik carrot.
0x4D0 188 length 1 byte array 1 byte each represents the treasure as accessed on the area select screen. Treasures appear to follow their internal IDs for order. These are all the treasures not part of the Exploration Kit (nor The Key). Non-zero values mean collected.

To do: find if there is a difference between the value being 0x2 or the more common 0x6

0x58D 13 length 1 byte array Same as above, only for Exploration Kit treasures including The Key.
0x834 4 bytes Actual Poko count the game registers, differing from what is displayed on the file select screen

Checksum

The checksum of a save slot is calculated according to this method.

This Python script (requires Python >3.4) assists with calculating the checksum for the data in a save slot. Not recalculating and fixing the checksum results in the game detecting the modified save slot as being corrupted (but if you have any unmodified save slots, those will still work fine).

Very careful editing might allow you to fool the corruption detection without having to recalculate the value: Due to the checksum being an additive one, if you increase one value by 1 and decrease a different value by 1, the checksum should still remain valid.[unsure]