Load order and conflicts

Enfusion resolves modded classes in load order: the last mod to extend a class wins. That single rule explains almost every conflict you will encounter.

The ordering rule

• 01Frameworks first — Community Framework and anything else that publishes a settings bus.
• 02Wrapping systems second — Sentinel validates RPCs for everything after it, so it must precede the mods it protects.
• 03Content next — weapons, vehicles, clothing, terrains.
• 04Governing systems last — anything that hooks a base class to modify other mods, such as Salvage Motorworks or Raid Window.

Genuine conflicts

Two mods conflict irreconcilably only when both replace the same base behaviour rather than extend it. In this catalogue that applies to exactly one combination: Bastion Fortifications and DayZ Expansion's base building both own the placement path.

Diagnosing

Bisect. Halve the mod list, confirm which half reproduces, and repeat. It takes four restarts to isolate a conflict in a sixteen-mod list, which is faster than reading logs.

grep -iE "cannot|error|conflict|duplicate" profiles/*.RPT | sort -u