Mod Conflicts

Mod and plugin conflicts are one of the most common causes of server instability. This guide explains how to identify, diagnose, and resolve them.

• Server crashes on startup with a specific mod mentioned in the error.
• Features from one mod break when another is installed.
• Console shows repeated error messages or warnings from specific plugins.
• Strange behaviour: items disappearing, commands not working, UI glitches.
• Performance degrades after adding a new mod.

The binary search method is the fastest way to find the culprit:

1. Remove half of your mods/plugins.
2. Start the server. Does the problem persist?
3. If yes, the issue is in the remaining half. Remove half of those.
4. If no, the issue is in the half you removed. Add those back and remove the other set.
5. Repeat until you isolate the specific mod causing the problem.

This lets you find the culprit in 4–5 restarts even with 30+ mods, instead of testing each one individually.

• Hook conflicts — two plugins trying to modify the same game behaviour (e.g. two damage modification plugins).
• Version incompatibility — a plugin built for an older game or framework version.
• Missing dependencies — a mod requires a library that isn't installed.
• Load order issues — some mods must load before or after others.
• Resource overlap — two FiveM resources registering the same command or event.

1. Update all mods — many conflicts are fixed in newer versions.
2. Check compatibility lists — mod pages often list known incompatibilities.
3. Adjust load order — for FiveM, reorder ensure lines in server.cfg. For Forge, check mod loading priority.
4. Choose one — if two mods do the same thing, pick the better-maintained one and remove the other.
5. Ask for help — post on the mod's GitHub issues or community forum with your error logs.