7 min read Advanced Updated: Agrar Chaoten Team

Short answer

How do I find out which mod is crashing my server?

Check the log first — an error with 'LUA call stack' often names the mod directly. Otherwise use the halving method: keep halving your mods until you've found the culprit.

Finding mod conflicts — overview

Server won't start, crashes while loading, vehicles disappear or a feature suddenly stops working? In most cases the culprit is a faulty mod or a conflict between two mods. With the right method you can track down the offender systematically — even with 50+ mods.

Always do this first: Look at the server log. If there's an Error with a "LUA call stack" and a mod name, you've often already found the offender — no further searching needed.

Typical symptoms

  • Server hangs while loading or crashes right away.
  • The log fills up with the same error over and over.
  • Objects or vehicles are missing after loading the savegame.
  • A feature (e.g. a production) no longer responds.
  • Problems only start after a game update — then several mods are usually outdated.

Method 1: Check the log first

Before you try anything, read the log. Search for Error and LUA call stack. The path /mods/FS25_XXXX/ names the offending mod directly. In many cases that saves you the entire search.

Method 2: Halving (binary search)

If the log isn't conclusive, you can find the mod by systematically halving — even with a huge mod list it only takes a few steps:

1

Test with an empty mods folder

Move all mods out of the folder via FTP and start the server. If it runs cleanly, a mod is definitely to blame.

2

Put half back

Upload half of the mods back and restart. If the error occurs, it's in this half. If not, it's in the other.

3

Keep halving

Split the suspect half again and repeat. With 64 mods you'll find the culprit in just 6 rounds.

4

Conflict between two mods?

If each mod works on its own but not together, you have a conflict. Then the only option is to replace one of the two or switch to an alternative.

Back up your savegame: Back up your save via FTP before removing mods. If a mod whose objects are stored in the savegame is missing, those objects get removed on load.

Common causes of conflicts

  • Outdated mods after an update: The most common cause. Bring all mods up to the current version.
  • Duplicate mods: The same mod in two versions in the folder — only ever keep one version.
  • Map + mod incompatibility: Some maps expect certain mods or clash with script mods.
  • "Stolen"/repackaged mods: Wrongly named or tampered mods are a classic source of errors — only use mods from trustworthy sources.

How to prevent conflicts

Test new mods one at a time: Don't push new mods onto the live server all at once. Test them individually (locally or on a test server) before they go into production.

Document your mod list: Keep a list of your mods including versions. After an update you'll see at a glance what needs updating.

Frequently asked questions (FAQ)

Frequently asked questions

How do I find out which mod is crashing my server?
Check the log first — an error with 'LUA call stack' often names the mod directly. Otherwise use the halving method: keep halving your mods until you've found the culprit.
What is the halving method?
A binary search: start with an empty mod folder, put half the mods back, test, and keep halving the suspicious half. With 64 mods, 6 rounds are enough.
Why do problems often appear after an update?
After an FS25 update, several mods are usually outdated. That's the most common cause of conflicts — bring all mods up to the latest version.
Do I lose my save when removing mods?
Objects from missing mods are removed from the savegame on load. So always back up your save via FTP before removing mods.

Questions about this guide?

Stuck on a step? Get in touch – we're happy to help.

Discord Ticket Contact form E-Mail

Last updated: 2026-06-21 · Written by the Agrar Chaoten team