How to install Thunderstore mods with r2modman

Understand the three layers first

r2modman manages profiles, packages, configuration, and the modded launch. Thunderstore provides package metadata, versions, README content, and dependency relationships. The game-specific loader—often BepInEx or another community tool—loads plugins at runtime. A successful download at one layer does not prove the next layer is working.

Choose the correct game and create a profile

Select the exact game community before installing anything. Create a new profile for the intended modpack instead of changing a known-good setup. Verify Settings → Locations against Steam’s Browse local files result, especially if you use multiple Steam libraries, Proton, or an external drive.

Install in a diagnostic order

Start with the community-required loader or core pack, then frameworks and shared libraries, and only then the feature mod. The Online page can install required dependencies, but you should still review their names and versions in Installed. Launch after each small batch instead of installing dozens of packages at once.

• Loader first: proves the game can enter the modded runtime.
• Dependencies second: proves shared APIs load without errors.
• Feature mod last: gives you one visible behavior to verify.

Prove that the mod actually loaded

Use Start modded, not the normal Steam or vanilla entry point. Look for the loader console/log, a package message, or the mod’s documented in-game behavior. “Installed” only confirms that r2modman placed the package in the profile; it does not prove the game accepted the loader or plugin.

Update, disable, and roll back safely

Export the profile before major changes. If a mod fails, disable that package in Installed and launch again; if necessary, reproduce with only the loader and target mod. Record the game, loader, and mod versions so a working state can be rebuilt instead of relying on memory.