Canonical resource path: Difference between revisions
Jump to navigation
Jump to search
imported>Leoetlino (→Special cases: update link_to_article usage) |
imported>Leoetlino m (→Special cases) |
||
| Line 3: | Line 3: | ||
== Special cases == | == Special cases == | ||
{{Link to article|link=Resource system#Special_cases}} | {{Link to article|link=Resource system#Special_cases}} | ||
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 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. | ||
Revision as of 12:55, 9 September 2018
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.
Special cases
Full article: Resource system
If the file is inside a 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.
Some add-on content files have Aoc/0010/ prepended to their canonical path.