Load Order
How does load order work in Cyberpunk?
Summary
Written by manavortex Published on Nov 22, 2023
This page will explain to you what Load Order is and how it works, then tell you how to influence it.
TL;DR
You're not supposed to manage load order conflicts outside of .archive mods and REDmods. If you ever feel the need to do that, a modder fucked up. An exception to this are Tweak mods, as the tweakDB is also a database of static values, conflicts can happen (e.g. two mods both edit the weapon stats of the Masamune).
For REDmods, see Conflicts and Load Order
For .archive mods, use Fuzzo's Archive Conflict Checker Tool (Nexus link).
There currently is no tool to check tweak conflicts
What is Load Order?
Unless two mods are changing the same file, you don't need to bother about this at all. Unfortunately, the moment you're using frameworks or anything body modding related, you will run into this scenario.
In Cyberpunk, conflicts inside .archive mods are one per-file basis, whatever mod modifies a file first will win – unlike e.g. Skyrim, where esps may overwrite each other.
Example
There are two mods that change boob size (and both mods modify the same file, e.g. a rig or mesh):
Since i_know_nothing_about_back_problems will load first, the conflicting file inside realistic_boobs_DDDDDDDDD_cup does nothing.
How are mods ordered?
The game loads mods in the following order (higher wins):
1. Legacy mods
All .archive files in Cyberpunk 2077/archive/pc/mod in alphabetical order (see below).
Note: If a file called
modlist.txtis found insidearchive/pc/modthen the game will load archives according to the order inside that file. The file may contain archive names, one mod archive name in each line. Example:
This means the game will load modb before moda, even though the filenames are not in alphabetical order. This allows for conflict management without renaming the physical files.
2. REDmods
Anything in Cyberpunk 2077/mods. All REDmod archives are loaded strictly after all archive files found inside /archive/pc/mod.
Load order: ASCII sort
The game reads mods in ASCII-alphabetical order (REDmods by folder name, .archive files by archive file name).
This is ASCII ordering:
Example
| Mod name | Pos | why |
|---|---|---|
MyMod.archive | 2 | M comes before m |
myMod.archive | 3 | |
!myMod.archive | 1 | ! comes before A |
How to use this?
You can re-name your folders and .archive files following the rules under Load order: ASCII sort to influence in which order the game will load your mods, or you can use Fuzzo's Archive Conflict Checker Tool (Nexus link).
Prefixing your archive file names with non-alphanumeric characters works fine in case of Cyberpunk, but is a terrible habit that might break file paths in other games or operating systems.
You will forget the warning above and re-learn this the hard way.
More Examples
If you are creating a compatibility mod (something that modifies the files of another installed mod), then yours needs to load first.
For example, if you want to do a custom recolour of the mod _ArchiveXL_Netrunner_Variants.archive, then your Wolvenkit project could be named _00_ArchiveXL_Netrunner_Variants, or _ArchiveXL_Netrunner_00_Recolour.
Last updated
