Savegames - Revision history

Shchmue: /* Extra data */ prior save struct link fix pointed to wrong struct

2020-04-28T19:03:27Z

Extra data: prior save struct link fix pointed to wrong struct

← Older revision		Revision as of 23:03, 28 April 2020
Line 435:		Line 435:
	\| 0x00		\| 0x00
	\| 0x40		\| 0x40
	\| [[Filesystem_services#~~SaveDataCreationInfo~~\|~~SaveDataCreationInfo~~]]		\| [[Filesystem_services#SaveDataAttribute\|SaveDataAttribute]]
	\|-		\|-
	\| 0x40		\| 0x40

2019-11-20T16:42:40Z

Extra data: fix save struct link

← Older revision		Revision as of 19:42, 20 November 2019
Line 435:		Line 435:
	\| 0x00		\| 0x00
	\| 0x40		\| 0x40
	\| [[Filesystem_services#~~Save_Struct~~\|~~Save Struct~~]]		\| [[Filesystem_services#SaveDataCreationInfo\|SaveDataCreationInfo]]
	\|-		\|-
	\| 0x40		\| 0x40

2019-04-02T19:41:42Z

AES CMAC header

← Older revision		Revision as of 23:41, 2 April 2019
Line 67:		Line 67:

	== AES CMAC header ==		== AES CMAC header ==

			This is internally referred to as MasterHeaderMac.

	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-

2019-04-02T19:36:50Z

File allocation table

← Older revision		Revision as of 23:36, 2 April 2019
Line 661:		Line 661:

	FAT entry 0 is reserved for the list of free blocks. Because of this, the FAT entry for block n is found at FAT index n+1. The indexes stored in FAT entries refer the index of the next/previous FAT entry in the chain, not the index of the next/previous block.		FAT entry 0 is reserved for the list of free blocks. Because of this, the FAT entry for block n is found at FAT index n+1. The indexes stored in FAT entries refer the index of the next/previous FAT entry in the chain, not the index of the next/previous block.

			The FAT header is internally called AllocationTableControlArea. The FAT itself is called AllocationTableMeta. The actual save FS data is called AllocationTableData.

	=== File allocation table header ===		=== File allocation table header ===

2019-04-01T19:09:25Z

File allocation table

← Older revision		Revision as of 23:09, 1 April 2019
Line 658:		Line 658:
	== File allocation table ==		== File allocation table ==

	The savedata FS uses ~~a fairly basic~~ allocation table to keep track of block allocation. ~~The~~ FAT contains doubly-linked lists of the blocks allocated to each file. Each entry in the FAT is 8 bytes in size.		The savedata FS uses an allocation table to keep track of block allocation. This FAT contains doubly-linked lists of the blocks allocated to each file. Each entry in the FAT is 8 bytes in size.

	FAT entry 0 is reserved for the list of free blocks. Because of this, the FAT entry for block n is found at FAT index n+1. The indexes stored in FAT entries refer the index of the next/previous FAT entry in the chain, not the index of the next/previous block.		FAT entry 0 is reserved for the list of free blocks. Because of this, the FAT entry for block n is found at FAT index n+1. The indexes stored in FAT entries refer the index of the next/previous FAT entry in the chain, not the index of the next/previous block.

2019-04-01T19:08:45Z

@@ Line 705: / Line 705: @@
 | 4
 | File table block index
 |-
 |}

2019-04-01T01:16:48Z

← Older revision		Revision as of 05:16, 1 April 2019
Line 656:		Line 656:
	\|}		\|}

	== File allocation table header ==		== File allocation table ==

			The savedata FS uses a fairly basic allocation table to keep track of block allocation. The FAT contains doubly-linked lists of the blocks allocated to each file. Each entry in the FAT is 8 bytes in size.

			FAT entry 0 is reserved for the list of free blocks. Because of this, the FAT entry for block n is found at FAT index n+1. The indexes stored in FAT entries refer the index of the next/previous FAT entry in the chain, not the index of the next/previous block.

			=== File allocation table header ===

	{\| class="wikitable"		{\| class="wikitable"

2019-03-31T19:49:23Z

2019-03-31T01:05:43Z

Core file system

2018-11-13T01:47:51Z

← Older revision		Revision as of 04:47, 13 November 2018
Line 6:		Line 6:

	There are 2 headers stored at 0x0 and 0x4000, presumably for commit and rollback purposes.		There are 2 headers stored at 0x0 and 0x4000, presumably for commit and rollback purposes.

			Decimal versions are separated as Major, Minor, Micro, and Bugfix with each using one byte. e.g. version 3.4.5.6 would be 0x03040506.

	{\| class="wikitable"		{\| class="wikitable"
Line 98:		Line 100:
	\| 0x004		\| 0x004
	\| 4		\| 4
	\| Version (~~Upper 2 bytes~~ must be ~~0x0004~~)		\| Version (Major version must be 4 or 5. Only system version 5.0.0+ can read version 5 save files)
	\|-		\|-
	\| 0x008		\| 0x008
Line 307:		Line 309:
	\| 0x04		\| 0x04
	\| 4		\| 4
	\| Version (~~Upper~~ 2 ~~bytes must be 0x0002~~)		\| Version (0.2.x.x)
	\|-		\|-
	\| 0x08		\| 0x08
Line 370:		Line 372:
	\| 0x04		\| 0x04
	\| 4		\| 4
	\| Version (Must be ~~0x10000~~ or ~~less~~)		\| Version (Must be 0.0.x.x or 0.1.0.0)
	\|-		\|-
	\| 0x08		\| 0x08
Line 404:		Line 406:
	\| 0x00		\| 0x00
	\| 4		\| 4
	\| Version (Must be 0 or 1)		\| Version (Stored as a normal 32-bit integer. Must be 0 or 1)
	\|-		\|-
	\| 0x04		\| 0x04
Line 495:		Line 497:
	\| 0x04		\| 0x04
	\| 4		\| 4
	\| Version (Must be ~~0x10000~~ or ~~less~~)		\| Version (Must be 0.0.x.x or 0.1.x.x)
	\|-		\|-
	\| 0x08		\| 0x08
Line 580:		Line 582:
	\| 0x04		\| 0x04
	\| 4		\| 4
	\| Version (~~Upper 2 bytes must be 0x0001~~)		\| Version (0.1.x.x)
	\|-		\|-
	\| 0x08		\| 0x08
Line 638:		Line 640:
	\| 0x04		\| 0x04
	\| 4		\| 4
	\| Version (~~Upper 2 bytes must be 0x0006~~)		\| Version (0.6.x.x)
	\|-		\|-
	\| 0x08		\| 0x08