Mod Loader Internals¶
Note
This applies to mod loader version >=1.1.0.
Main Process¶
The internal mod loader process is documented here.
- When launching, the mod loader will immediately remove any
.diffpack files present in the game'sdatadirectory..diff.pacfiles essentially extend the base content with extra/modded contents. Cleaning it first means starting from a fresh state. - Every mod loaded by Reloaded-II which has a
FFXVIfolder will be picked up by the loader and keep track of every file (and accordingly translate them to the proper pack according to this list).- Support for folders named after packs is still supported (pre-1.1.0 behavior).
- Nex tables (
.nxd) changes from original to modded will be specifically recorded to allow more mods to be compatible if they edit the same table. - When mod files conflict, the last loaded one has priority.
- The mod loader will inject its own edited files for the main menu mod information (if enabled).
- Once Reloaded-II has alerted the mod loader that all mods have been loaded, the mod loader will merge all nex changes, and every other files provided for each pack by mods. The mod loader will begin to build each pack with FF16Tools and save them as
.diff.pacfiles in the game'sdatafolder.
Which means, file mods will persist when booting without Reloaded-II. However, Reloaded-II can also consist of code-based mods, so it is always recommended to boot through it.