Use evidence before reordering
- Read every Workshop page for required items, incompatibilities, and explicit order instructions.
- Put shared libraries and frameworks before mods that require them.
- Put an addon or compatibility patch after the parent mods whose files it changes.
- On a server, order the Mod IDs in
Mods; keep every required Workshop item present in the download list. - Restart and reproduce one known conflict on a new save or test world.
- If the trace reports a missing file, wrong Mod ID, or unsupported build, fix that problem instead of reordering.
When order is not the cause
Load order cannot download a missing Workshop item, create a missing dependency, update a Build 41 mod for Build 42, or repair a wrong Mod ID. If moving one entry changes nothing, return to the first console trace and isolate the affected pair on a new save.
Sources
The Indie Stone forum: multiplayer mod load order — Official support explanation of when order matters.
PZwiki Load order — Official-wiki load-order reference.
Community discussion: dependency and patch order — Build 41 example of parent and addon ordering.