Please disclose if any significant portion of your mod was created using AI tools by adding the 'AI Generated' category. Failing to do so may result in the mod being removed from Thunderstore.
Known Issues & Fixes
Updated 5 days agoKnown Issues & Fixes
The short list of problems people actually hit, and how to solve them. For anything not here, open an issue.
Quick table
| Problem | Fix |
|---|---|
| Game won't launch | Fresh profile, verify game files in Steam, update GPU drivers, relaunch through the manager. See below. |
| Can't see lobbies / can't join | Everyone needs the same modpack version and should launch from the same profile. |
| Voice cuts out after landing | Known engine limitation. See the Voice Chat Issues page for what actually helps. |
| Low FPS / freezes | See Performance & FPS. SSD + closing background apps help most. |
| Download stuck at 100% | Wait 1-5 minutes, the pack is unpacking. Don't restart immediately. |
| Crashes after adding/removing a mod | The pack is tested as-is. Reinstall on a clean profile without changes. |
Game won't launch
- Make sure you installed on a fresh profile, not over an old one.
- In Steam, verify the integrity of Lethal Company's files.
- Update your GPU drivers.
- Launch again through the mod manager, not from Steam directly.
If it still fails, grab your BepInEx/LogOutput.log from the profile folder and attach it to a GitHub issue.
Can't see lobbies or connection issues
- All players need the exact same modpack version.
- Everyone should launch through the same mod manager profile.
- A single mismatched mod or version will hide the lobby.
Voice chat cutting out
This is the most reported issue, and it comes from the game's built-in voice system, not the pack. It has its own page with the full explanation and the fixes that reduce it: Voice Chat Issues.
Crashes or desyncs after editing the pack
Adding or removing individual mods can cause crashes, desyncs or version mismatches with other players. The pack is built and tested as one set. If you've edited it, reinstall a clean copy on a new profile before reporting a bug.
Reporting a bug well
A good report gets fixed faster. Please include:
- How many players, and who was hosting.
- What you were doing when it happened.
- Your specs (CPU, RAM, SSD or HDD).
- Your
BepInEx/LogOutput.logif you can grab it.
