Save Files - Revision history

Savage13: Add weather save file information

2024-06-20T10:38:00Z

Add weather save file information

← Older revision		Revision as of 10:38, 20 June 2024
Line 171:		Line 171:
	\|EffectLevel		\|EffectLevel
	\|}		\|}
	<references />		Weather data with [[WorldMgr#Weather types\|type data]] are found in <code>climateWeather</code> : int32_array, <code>climateWeather2</code>: int32_array and <code>climateWeather3</code> : int32_array. These values contain the weather for the next three in-game days. Arrays are 20 values in length map directly to climate values of each [[Map area]]. Each int32 value contains 6 packed [[WorldMgr#Weather types\|WorldMgr]] weather types that each are 4 bits long (nibble, 0x0-0xF). These weather types identify are for each 4 hour long period during the day.<references />
	[[Category:File_formats]]		[[Category:File_formats]]

Ginger: /* .sav Folder Format */ Data type clarifications, various formatting fixes

2024-06-19T22:12:21Z

.sav Folder Format: Data type clarifications, various formatting fixes

← Older revision		Revision as of 22:12, 19 June 2024
Line 29:		Line 29:

	===Options===		===Options===
	<code>option.sav</code> contains the settings set in the options menu (inverted camera, stick sensitivity etc.). The exact data stored here corresponds to the game flags defined in <code>Pack/Bootup.pack/GameData/savedataformat.ssarc/saveformat_*.bgsvdata</code>, where the <code>file_list</code> array's zero-index dictionary contains the <code>file_name</code> "option.sav"		<code>option.sav</code> contains the settings set in the options menu (inverted camera, stick sensitivity etc.). The exact data stored here corresponds to the game flags defined in <code>Pack/Bootup.pack//GameData/savedataformat.ssarc///saveformat_*.bgsvdata</code>, where the <code>file_list</code> array's zero-index dictionary contains the <code>file_name</code> "option.sav"

	===Album===		===Album===
Line 40:		Line 40:
	Each save state contains 3 files:		Each save state contains 3 files:
	* caption.jpg A screenshot taken at the time of saving.		* caption.jpg A screenshot taken at the time of saving.
	* caption.sav Contains a small amount of data for each save that is displayed in the save select screen (e.g. time and location). The exact data stored here corresponds to the game flags defined in <code>Pack/Bootup.pack/GameData/savedataformat.ssarc/saveformat_*.bgsvdata</code>, where the <code>file_list</code> array's zero-index dictionary contains the <code>file_name</code> "caption.sav"		* caption.sav Contains a small amount of data for each save that is displayed in the save select screen (e.g. time and location). The exact data stored here corresponds to the game flags defined in <code>Pack/Bootup.pack//GameData/savedataformat.ssarc///saveformat_*.bgsvdata</code>, where the <code>file_list</code> array's zero-index dictionary contains the <code>file_name</code> "caption.sav"
	* game_data.sav The data for each save state. The exact data stored here corresponds to the game flags defined in <code>Pack/Bootup.pack/GameData/savedataformat.ssarc/saveformat_*.bgsvdata</code>, where the <code>file_list</code> array's zero-index dictionary contains the <code>file_name</code> "game_data.sav"		* game_data.sav The data for each save state. The exact data stored here corresponds to the game flags defined in <code>Pack/Bootup.pack//GameData/savedataformat.ssarc///saveformat_*.bgsvdata</code>, where the <code>file_list</code> array's zero-index dictionary contains the <code>file_name</code> "game_data.sav"

	==.sav Folder Format==		==.sav Folder Format==
Line 99:		Line 99:
	\|}		\|}

	In <code>Pack/Bootup.pack/GameData/savedataformat.ssarc/saveformat_.bgsvdata</code>, the game stores a mapping for each ID to the corresponding entry name. This name is then further defined in one of the files in <code>Pack/Bootup.pack/GameData/gamedata.ssarc/</code>, depending on its data type.		In <code>Pack/Bootup.pack//GameData/savedataformat.ssarc///saveformat_.bgsvdata</code>, the game stores a mapping for each ID to the corresponding entry name. This name is then further defined in one of the files in <code>Pack/Bootup.pack//GameData/gamedata.ssarc//</code>, depending on its data type.

	Strings are stored with the maximum possible number of characters (e.q. 256 characters for strings defined in string256_data_0.bgdata) and are broken up into 4-byte parts. These are then stored in sequential chunks with the ID repeating for each chunk.		Strings are stored with the maximum possible number of characters (e.q. 256 characters for strings defined in string256_data_0.bgdata) and are broken up into 4-byte parts. These are then stored in sequential chunks with the ID repeating for each chunk.
Line 105:		Line 105:
	For arrays the data is also stored in sequential chunks, each with an identical ID. The horse names for example will take up 96 chunk with the ID 0x7B74E117 in the save file, 6 names with 16 chunks (= 64 characters) for each name.		For arrays the data is also stored in sequential chunks, each with an identical ID. The horse names for example will take up 96 chunk with the ID 0x7B74E117 in the save file, 6 names with 16 chunks (= 64 characters) for each name.

	Data types for <code>value</code> include bool, int32, float32, string, string64, string256, vector2f, vector3f, vector4, bool_array, int32_array, float32_array, string64_array, string256_array, vector2f_array, and vector3f_array.		Data types for <code>value</code> include bool, int32, float32, string, string64, string256, vector2f, vector3f, vector4, bool_array, int32_array, float32_array, string64_array, string256_array, vector2f_array, and vector3f_array. Value types are read as, and therefore must correspond to, the type defined in the <code>Pack/Bootup.pack//GameData/gamedata.ssarc/*</code> in the key of the main byml dictionary where the <code>id</code> is found. (Note that, in the vanilla game, this also corresponds to the name of the file, itself, but this relationship is not strict and therefore may not be the case for files added by mods.)

	Inventory items are stored in <code>PorchItem</code> with a maximum of 420 internal string identifiers, e.g. <code>Weapon_Sword_023.</code>Associated arrays of <code>PorchEquip</code>: boolean and <code>PorchItem_Value1~~: int32~~</code> store if the item is equipped and its current durability * 100 or item count. Swords, Bows and Shields also store their modifier key in <code>PorchSword_FlagSp~~: in32~~</code> and modifier value <code>PorchSword_ValueSp~~: int32~~</code>. Similar Flag and Value exist for the Bows and Shields. <code>FlagSp</code> modifiers can take any or all of the following values.		Inventory items are stored in <code>PorchItem</code> with a maximum of 420 internal string identifiers, e.g. <code>Weapon_Sword_023</code>. Associated arrays of <code>PorchEquip</code>: boolean and <code>PorchItem_Value1</code>: int32 store if the item is equipped and its current durability * 100 or item count. Swords, Bows and Shields also store their modifier key in <code>PorchSword_FlagSp</code>: uint32 and modifier value <code>PorchSword_ValueSp</code>: int32. Similar Flag and Value exist for the Bows and Shields. <code>FlagSp</code> modifiers can take any or all of the following values.
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+
Line 140:		Line 140:
	\|0x80000000		\|0x80000000
	\|}		\|}
	Associated data with Cooked Items are held in <code>CookEffect0~~: vector2f~~</code>, <code>CookEffect1~~: vector2f,~~</code> and <code>StaminaRecover~~: vector2f~~</code> arrays. Values within these arrays are		Associated data with Cooked Items are held in <code>CookEffect0</code>: vector2f, <code>CookEffect1</code>: vector2f, and <code>StaminaRecover</code>: vector2f arrays. Values within these arrays are
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+

Ginger: Spelling/punctuation. (Yay pedantry)

2024-06-19T22:02:39Z

Spelling/punctuation. (Yay pedantry)

← Older revision		Revision as of 22:02, 19 June 2024
Line 44:		Line 44:

	==.sav Folder Format==		==.sav Folder Format==
	All data in these files is stored as little endian on Switch and as big endian ~~ion~~ Wii U.		All data in these files is stored as little endian on Switch and as big endian on Wii U.

	A save file (with the exception of files in the tracker folder) starts with the following header:		A save file (with the exception of files in the tracker folder) starts with the following header:
Line 99:		Line 99:
	\|}		\|}

	In <code>Pack/Bootup.pack/GameData/savedataformat.ssarc/saveformat_.bgsvdata</code> the game stores a mapping for each ID to the corresponding entry name. This name is then further defined in one of the files in <code>Pack/Bootup.pack/GameData/gamedata.ssarc/</code>, depending on its data type.		In <code>Pack/Bootup.pack/GameData/savedataformat.ssarc/saveformat_.bgsvdata</code>, the game stores a mapping for each ID to the corresponding entry name. This name is then further defined in one of the files in <code>Pack/Bootup.pack/GameData/gamedata.ssarc/</code>, depending on its data type.

	Strings are stored with the maximum possible number of characters (e.q. 256 characters for strings defined in string256_data_0.bgdata) and are broken up into 4-byte parts. These are then stored in sequential chunks with the ID repeating for each chunk.		Strings are stored with the maximum possible number of characters (e.q. 256 characters for strings defined in string256_data_0.bgdata) and are broken up into 4-byte parts. These are then stored in sequential chunks with the ID repeating for each chunk.

Ginger: /* Folder Structure */ Clarify location of save file content definitions

2024-06-19T22:02:02Z

Folder Structure: Clarify location of save file content definitions

← Older revision		Revision as of 22:02, 19 June 2024
Line 29:		Line 29:

	===Options===		===Options===
	<code>option.sav</code> contains the settings set in the options menu (inverted camera, stick sensitivity etc.).		<code>option.sav</code> contains the settings set in the options menu (inverted camera, stick sensitivity etc.). The exact data stored here corresponds to the game flags defined in <code>Pack/Bootup.pack/GameData/savedataformat.ssarc/saveformat_*.bgsvdata</code>, where the <code>file_list</code> array's zero-index dictionary contains the <code>file_name</code> "option.sav"

	===Album===		===Album===
Line 40:		Line 40:
	Each save state contains 3 files:		Each save state contains 3 files:
	* caption.jpg A screenshot taken at the time of saving.		* caption.jpg A screenshot taken at the time of saving.
	* caption.sav Contains a small amount of data for each save that is displayed in the save select screen (e.g. time and location).		* caption.sav Contains a small amount of data for each save that is displayed in the save select screen (e.g. time and location). The exact data stored here corresponds to the game flags defined in <code>Pack/Bootup.pack/GameData/savedataformat.ssarc/saveformat_*.bgsvdata</code>, where the <code>file_list</code> array's zero-index dictionary contains the <code>file_name</code> "caption.sav"
	* game_data.sav The data for each save state.		* game_data.sav The data for each save state. The exact data stored here corresponds to the game flags defined in <code>Pack/Bootup.pack/GameData/savedataformat.ssarc/saveformat_*.bgsvdata</code>, where the <code>file_list</code> array's zero-index dictionary contains the <code>file_name</code> "game_data.sav"

	==.sav Folder Format==		==.sav Folder Format==

Savage13: Add description of Save data and Inventory data

2024-06-19T21:23:35Z

Add description of Save data and Inventory data

@@ Line 94: / Line 94: @@
 !Offset !! Size !! Description
 |-
-| 0x00 || 4 || '''id''': ID of the data being stored
+| 0x00 || 4 || '''id''': ID of the data being stored, crc32 of the internal key
 |-
 |0x04 || 4 || '''value'''
@@ Line 105: / Line 105: @@
 For arrays the data is also stored in sequential chunks, each with an identical ID. The horse names for example will take up 96 chunk with the ID 0x7B74E117 in the save file, 6 names with 16 chunks (= 64 characters) for each name.
 <references />
 [[Category:File_formats]]

Kyto: Created page with " BotW can store up to 9 save states per profile, 6 for normal mode (1 manual save and 5 autosaves) and 2 for master mode (1 manual save and 1 autosave).
2022-07-03T09:16:19Z

Created page with "<onlyinclude> BotW can store up to 9 save states per profile, 6 for normal mode (1 manual save and 5 autosaves) and 2 for master mode (1 manual save and 1 autosave). </onlyinc..."

New page
<onlyinclude>
BotW can store up to 9 save states per profile, 6 for normal mode (1 manual save and 5 autosaves) and 2 for master mode (1 manual save and 1 autosave).
</onlyinclude>

==Folder Structure==
The content of the save folder is structured as following:

0
caption.jpg
caption.sav
game_data.sav
1
...
album
pict_000.jpg
pict_001.jpg
...
pict_book
Animal_Cassowary_A.jpg
Weapon_Sword_008.jpg
...
tracker
trackblock00.sav
trackblock01.sav
...
option.sav

The numbered folders each represent one save state.

===Options===
<code>option.sav</code> contains the settings set in the options menu (inverted camera, stick sensitivity etc.).

===Album===
The album folder contains one JPG file for each entry in the in-game album, numbered in the order they were taken.

===Hyrule Compendium===
Each JPG file in the <code>pict_book</code> folder corresponds to one entry in the Hyrule Compendium. The name of each file is the internal name of the given item, weapon or animal. Do note that the compendium is not directly tied to a specific save state, meaning the images are shared between all saves.

===Save State===
Each save state contains 3 files:
* caption.jpg A screenshot taken at the time of saving.
* caption.sav Contains a small amount of data for each save that is displayed in the save select screen (e.g. time and location).
* game_data.sav The data for each save state.

==.sav Folder Format==
All data in these files is stored as little endian on Switch and as big endian ion Wii U.

A save file (with the exception of files in the tracker folder) starts with the following header:
{| class="wikitable"
!Offset !! Size !! Description
|-
| 0x00 || 4 || '''version''': Version of the game that created the save file.
|-
|0x04 || 4 || '''marker''': Always 0xFFFFFFFF.
|-
|0x08 || 4 || '''unknown''': Always 0x1.
|}

Versions:

{| class="wikitable"
! Game version !! Save version
|-
| 1.0.0 || 0x24E2
|-
| 1.1.0 || 0x24EE
|-
| 1.1.1 ||
|-
| 1.1.2 ||
|-
| 1.2.0 || 0x2588
|-
| 1.3.0 || 0x29C0
|-
| 1.3.1 || 0x2A46
|-
| 1.3.3 || 0x3EF8
|-
| 1.3.4 || 0x3EF9
|-
| 1.4.0 || 0x471A
|-
| 1.4.1 || 0x471A
|-
| 1.5.0 || 0x471B
|-
| 1.6.0 || 0x471E
|}

The data after the header is comprised of 8-byte chunks:

{| class="wikitable"
!Offset !! Size !! Description
|-
| 0x00 || 4 || '''id''': ID of the data being stored
|-
|0x04 || 4 || '''value'''
|}

In <code>Pack/Bootup.pack/GameData/savedataformat.ssarc/saveformat_.bgsvdata</code> the game stores a mapping for each ID to the corresponding entry name. This name is then further defined in one of the files in <code>Pack/Bootup.pack/GameData/gamedata.ssarc/</code>, depending on its data type.

Strings are stored with the maximum possible number of characters (e.q. 256 characters for strings defined in string256_data_0.bgdata) and are broken up into 4-byte parts. These are then stored in sequential chunks with the ID repeating for each chunk.

For arrays the data is also stored in sequential chunks, each with an identical ID. The horse names for example will take up 96 chunk with the ID 0x7B74E117 in the save file, 6 names with 16 chunks (= 64 characters) for each name.

<references />
[[Category:File_formats]]