← Back to GuidesFixMyGame Home
Lethal Company

Lethal Company BepInEx LogOutput Fix

If Lethal Company crashes or your mods fail to load, the most useful file is usually BepInEx/LogOutput.log. This guide helps you find the correct log and avoid uploading files that only list the modpack, like manifest.json.

Quick answer

Launch Lethal Company until the issue happens, then open the newest BepInEx/LogOutput.log file. Use that file in FixMyGame instead of manifest.json, profile files, or dependency lists.

What LogOutput.log is

LogOutput.log is the main BepInEx runtime log. It records what plugins loaded, which dependencies were missing, which errors happened during startup, and whether a mod failed while Lethal Company was opening.

Common signs in the log

BepInEx
LogOutput.log
FileNotFoundException
Could not load file or assembly
Missing dependency
Plugin failed to load
Network prefab hash mismatch
LC_API, BepInExPack, LateCompany, or MoreCompany

How to get the right log

1
Open your Lethal Company modded profile or launcher.
2
Launch the game and recreate the crash, failed load, or multiplayer issue.
3
Close the game after the issue happens.
4
Open the Lethal Company game folder or mod manager profile folder.
5
Open the BepInEx folder.
6
Open LogOutput.log.
7
Use that newest LogOutput.log file in FixMyGame.

Do not upload manifest.json

A manifest.json file usually lists the modpack name, version, and dependency list. That can be useful for seeing what the modpack contains, but it usually does not show the actual crash or plugin failure.

manifest.json lists dependencies, but it is not the runtime crash log.
profile files may show what should be installed, not what actually failed.
LogOutput.log shows what BepInEx tried to load during the real session.
If FixMyGame says manifest uploaded, run the game and use LogOutput.log instead.

Common Lethal Company mod issues

A required dependency is missing or outdated.
BepInExPack is missing, broken, or installed in the wrong place.
LC_API or another library is required by a mod.
Multiplayer players do not have the same modpack/profile.
A mod was built for a different Lethal Company version.
A plugin failed while BepInEx was loading the game.

Do not do this yet

Do not delete random plugins before checking the first BepInEx error.
Do not upload manifest.json if FixMyGame asks for the crash log.
Do not assume multiplayer issues are fixed if only your profile changed.
Do not mix old and new dependency versions without retesting.

FixMyGame tip

If FixMyGame says the file is a manifest or dependency list, run Lethal Company again, recreate the issue, and use the newest BepInEx/LogOutput.log created after that session.

Related Guides

Fresh Log vs Old Log

Learn why the newest log matters when diagnosing a modded game crash.

How to Read a Crash Log

Learn how to find the real error inside a long crash log.

Missing Dependencies

Learn what it means when a mod needs another dependency before it can load.

Mod Conflicts

Learn how two mods can interfere with each other and cause crashes.