Title Database: Difference between revisions
Finally some clarification |
mNo edit summary |
||
| Line 21: | Line 21: | ||
* [[Extdata#SD Extdata|ExtdataID low]] (if the title uses ExtData) | * [[Extdata#SD Extdata|ExtdataID low]] (if the title uses ExtData) | ||
* Whether or not a [[NCCH#CFA|Electronic Manual]] is used | * Whether or not a [[NCCH#CFA|Electronic Manual]] is used | ||
* Whether or not [[Savegames|Savedata]] is used | |||
It is important to note the database doesn't contain a hash of the [[Title Data Structure|.cmd]]. So if a user has more than one valid set of [[Title Data Structure|application data]] for a given .cmd Content ID they can be manually interchanged without issue. Though renaming a .cmd file to match the Content ID which the title.db is expecting will result in an error, as the CTR for the per-console encryption layer changes depending on the file path, and the MAC of the .cmd is probably generated with the .cmd Content ID in mind. | It is important to note the database doesn't contain a hash of the [[Title Data Structure|.cmd]]. So if a user has more than one valid set of [[Title Data Structure|application data]] for a given .cmd Content ID they can be manually interchanged without issue. Though renaming a .cmd file to match the Content ID which the title.db is expecting will result in an error, as the CTR for the per-console encryption layer changes depending on the file path, and the MAC of the .cmd is probably generated with the .cmd Content ID in mind. | ||