A conflict is not an error. It means two enabled mods both provide a file for the same game path, and Penumbra has to pick one.
Reading the conflicts tab
Select a mod and open Conflicts. Each row shows the contested path, the other mod involved, and which one currently wins. Winning is decided by priority: higher wins, and ties are broken by load order, which is not something you want to rely on.
Setting priority
Priority is a plain integer on each mod, default 0. Give the mod you want to win a higher number.
A scheme that stays readable as the list grows:
- 0 — body and base replacements
- 10 — clothing and gear
- 20 — accessories and small overrides
- 100 — temporary fixes you intend to remove
Leaving gaps means you can insert something later without renumbering.
Option groups are better than priority
If two mods conflict because you only want part of each, priority is the wrong tool. Many mods ship option groups — pick the specific parts you want inside each mod and the conflict disappears entirely, because they no longer claim the same paths.
Check the mod’s settings panel before reaching for priority.
Conflicts you should not resolve
Some conflicts are harmless. Two mods providing the same unchanged file conflict on paper and produce identical results either way. The Conflicts tab flags them because it compares paths, not contents.
Fixing those wastes time. Look at whether the result is actually wrong before adjusting anything.