Mod not working? 8 most common causes and solutions

The vast majority of mod problems have several recurring causes. Check them one by one before reporting the error to the author.

1. Mod for another version of the game

The FS22 mod will not work in FS25 and vice versa. Check the game designation on the mod's website - the file name usually starts with FS25_ or FS22_.

2. Incorrect file name

The archive name can only contain letters, numbers and underscores and cannot begin with a number. File FS25_Traktor (1).zip will be skipped - rename it to FS25_Traktor.zip.

3. Archive within the archive

If after opening the .zip file you see another .zip file or folder inside instead of the modDesc.xml file, the game will not find the mod. Unpack the internal archives and move them to the mods folder.

4. The mod is not enabled in the save

Each save has its own list of active mods. Load a save and select the mod on the mod selection screen.

5. A required mod is missing

Some mods need different ones - e.g. a map requires an object package and a machine requires an additional script. Read the mod description and install the required add-ons.

6. Two versions of the same mod

Old and new versions of the same mod saved under different names may conflict with each other. Leave only the newest one in the folder.

7. Outdated game

New mods are sometimes prepared for the latest game update. Install the latest patch in Steam, Epic Games or the GIANTS launcher.

8. Conflict with another mod

If the problem occurred after installing several mods at once, disable them and enable them one at a time. This is the quickest way to find the mod that causes the error.

Check the log.txt file

The game saves the runtime in file log.txt in folder Dokumenty\My Games\FarmingSimulator2025 (for FS22 - FarmingSimulator2022). Open it in Notepad and search for Error or the name of the mod.