Log Doctor

A mod will not load, the game crashes, or something is missing? The game writes every problem it meets into a file called log.txt. Paste it here and Log Doctor groups the error lines, says what each kind usually means, and names the mods involved.

Your log is read by a script on this page, in your browser. It is not sent to our server and nothing is stored.

Your log.txt

Choose log.txt

Where to find log.txt

Windows: Documents\My Games\FarmingSimulator2025\log.txt. If your Documents folder is synced with OneDrive, it may live under OneDrive\Documents instead.
Mac: ~/Library/Application Support/FarmingSimulator2025/log.txt. The Mac App Store version may keep it somewhere else; if you cannot find it there, search for log.txt inside the FarmingSimulator2025 folder.
Copy it before you start the game again. The game overwrites log.txt each time it starts, so reproduce the problem, close the game, then copy the file.

What it can and cannot do

It reads what the log says. It recognises the common kinds of error line: missing dependencies, file names the game rejects, outdated mods, files and nodes that cannot be found, undefined brands and Lua script errors. Everything else is listed under other errors or warnings, with the original text.
The explanations are the usual causes, not a diagnosis. A script error can start in a different mod from the one named in the file path, so the mods named most often are good first suspects rather than proof.
A few warnings are normal. Many working mod setups still write some warnings. Errors matter more than warnings.
The usual method still applies: update the mods named, make sure everything they need is installed, and if you cannot tell which mod is responsible, switch mods off in halves and start the game again.

For the longer walk-through, read When a Mod Won't Load or Crashes the Game.

Looking for a replacement? Try searching the catalog or the Spec Finder.