01Confirm the Lethal Company community and game build
Start from the game’s own Thunderstore community, not a package with a similar name from another game. Read the loader requirement, target game version, dependencies, and recent package activity. r2modman support is a distribution and profile workflow; it does not guarantee that every package remains compatible after a Lethal Company update.
02Create a known-good baseline
Make a clean profile and verify Settings → Locations against Steam’s Browse local files result. Install only the community-required loader or core pack, then use Start modded. A loader-only success proves more than importing a large pack and hoping the final screen identifies the problem.
03Separate client-side and lobby-wide changes
Lethal Company packages range from UI conveniences to content and lobby changes. Read whether the host, every client, or only the installing player needs the mod. Keep a small shared profile for the group and a separate experimental profile for local visual or interface tests.
04Troubleshoot mismatched lobbies
Confirm everyone uses the same game build, loader, required dependencies, package versions, and relevant configs. If connection or startup fails, reduce the host and one client to the same minimal profile, then restore packages in matching batches.
05Update without sacrificing the playable profile
Clone the working profile before updating the loader or several mods. Test the clone, preserve the old versions, and move changes into the stable profile only after the same launch and gameplay checks pass. Record manual files that a profile export cannot reproduce.
06Respect compatibility and multiplayer boundaries
A mod can be technically loadable and still be disallowed by a server, anti-cheat system, tournament, or game policy. For multiplayer, align required client and server packages and exact versions. Treat mod README files and server rules as primary operational documentation.
✦ Frequently asked questions
Clear answers before you change anything
Do all Lethal Company players need r2modman?
Not necessarily for every client-only package, but a shared r2modman profile is an efficient way to align required mods and versions.
Why can one player not join the lobby?
Compare the game build, required package list, versions, configs, and manually installed files on that client.
Should I use one profile for every group?
Separate profiles are safer when groups use different packs or versions.
Research note: September 13, 2026 snapshot. Game support and compatibility remain community-specific.
Recommended path: read this guide → download or create a minimal profile → record the result → expand to the full modpack.