Canonical resource path: Difference between revisions
Jump to navigation
Jump to search
imported>BravelyPeculiar No edit summary |
imported>BravelyPeculiar No edit summary |
||
| Line 1: | Line 1: | ||
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 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 00:28, 7 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.
However, if the file is inside a 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.