Canonical resource path: Difference between revisions
Jump to navigation
Jump to search
"nested SARCs" -> "all nested SARCs" (example: bactorpacks in TitleBG or Bootup)
imported>BravelyPeculiar (stubbed) |
imported>Leoetlino ("nested SARCs" -> "all nested SARCs" (example: bactorpacks in TitleBG or Bootup)) |
||
| Line 3: | Line 3: | ||
Breath of the Wild uses '''canonical resource paths''' to define the locations of its content files. These paths generally treat the content directory as the root directory of the path. | Breath of the Wild uses '''canonical resource paths''' to define the locations of its content files. These paths generally treat the content directory as the root directory of the path. | ||
However, if the file is inside a [[SARC|SARC archive]], then that archive is treated as the path's root. This does not apply to nested SARCs (e.g. content/Pack/Bootup.pack/GameData/gamedata.ssarc) — files inside these archives do not have a canonical resource path. | However, if the file is inside a [[SARC|SARC archive]], then that archive is treated as the path's root. This does not apply to all nested SARCs (e.g. content/Pack/Bootup.pack/GameData/gamedata.ssarc) — files inside these archives do not have a canonical resource path. | ||
If a file is [[Yaz0]]-encoded, and as such has an "s" prefixed to its extension, that "s" is '''excluded''' from the canonical resource path. | If a file is [[Yaz0]]-encoded, and as such has an "s" prefixed to its extension, that "s" is '''excluded''' from the canonical resource path. | ||