Skip to content

Game guides

Reading log.txt in Farming Simulator 25: finding why a mod was rejected or crashed, and what to send the author

· 3 min read · ModsDrop

Massey Ferguson 4000 Series – 225 hp Large Tractor
Pictured: Massey Ferguson 4000 Series – 225 hp Large Tractor, from the ModsDrop library.

Farming Simulator 25 writes a plain-text log every time it runs, and it is unusually talkative: every mod it loads, every one it rejects and why, every script error with the file and line. For anyone who installs mods manually it is the single most useful file on the disk, and it is one search away from answering most “the mod does not work” questions. Here is where it is and how to read it.

Where it is

Documents\My Games\FarmingSimulator2025\log.txt. It is overwritten at every start, so if the game crashed and you restarted it to get here, the crash is gone; copy the log before you restart next time. Opening it in Notepad is fine; a text editor with search (Notepad++, VS Code) is better because the file runs to thousands of lines.

Structure

Lines start with a timestamp and a level: Info, Warning or Error. The first few hundred lines describe your system and settings. Then the mod loading section: one block per mod, with its file name, its name from the description file, its version, and any complaint. Then the savegame load, then gameplay messages until you quit.

The searches that matter

  1. Search for “Error”. Read the first ones after the mod section starts; later errors are often consequences of the first.
  2. Search for the mod’s zip name. Every mod the game saw is mentioned, accepted or rejected. If the name is absent, the game never saw the file: wrong folder, or a name it refused to list.
  3. Search for “unsupported”. “Mod name contains unsupported characters” is the message behind most invisible mods.
  4. Search for “descVersion”. A mod whose description file declares an old or wrong version is reported here; FS22 mods dropped into FS25 end up in this line.
  5. Search for “LUA call stack” or “callstack”. A script mod failed; the lines above name the mod’s file and the function. Since patches 1.24 and 1.25, loadstring appearing here means the mod used a function the game has disabled.
  6. Search for “Missing” and “Can’t load resource”. A mod references a texture, model or sound it does not contain, or that the base game renamed. Cosmetic if it is one texture; a missing .i3d means the whole vehicle will not appear.
  7. Search for “conflict” and “dependency”. The same information the mod selection screen gave, with the exact mod names involved.

Common lines, translated

From log to fix

Rejected for its name: rename the zip without spaces and brackets. Rejected for version: it is an FS22 mod or an abandoned FS25 one; only the author can fix it. Lua errors: look for an update newer than 29 September 2026; if there is none, the mod is broken until there is. Missing resources: re-download and compare sizes; if the second copy is the same, the mod is incomplete as published. Conflicts and dependencies: as the conflicts guide describes.

Sending a log to an author

Copy the lines about their mod and ten lines around the first error, with your game version and the mod’s version. Not the whole file: it includes your system details and runs to megabytes, and the author needs five lines of it. Say whether the problem survives with every other mod unticked; that single fact halves the author’s work.

Dedicated servers

A dedicated server writes its own log in its own profile folder, reachable from the server’s web interface. The same messages appear there; a mod rejected on the server is rejected for the same reasons as on a PC.

More Farming Simulator 25 →

← All news