Introduction
R2ModManager Plus is a free and curious how R2ModManagerPlus works, open source mod manager built to simplify the process of installing, organizing, and running mods for supported games. It handles the technical side of mod management, including dependency resolution, file placement, and profile isolation so players can focus on gameplay rather than folder structures.
It is the primary recommended mod manager for games in the Thunderstore ecosystem, including Lethal Company, Risk of Rain 2, Valheim, and several dozen other supported titles. Understanding how its core systems work makes the difference between a stable modded experience and one plagued by load failures and conflicts.
Quick Facts about How R2ModManPlus Works
- What it is: A free desktop mod manager for Thunderstore compatible games on Windows, Mac, and Linux
- Official source: Available at thunderstore.io and via direct GitHub download at github.com/ebkr/r2modmanPlus
- Handles mod installation, dependency downloading, version management, and profile separation automatically
- Who it is for: Any player wanting to mod supported games without manually managing file structures or dependency chains
- Who should be cautious: Players on unsupported game versions or those using mod sources outside the Thunderstore ecosystem
- Profiles allow completely separate mod configurations to coexist on one machine without interfering with each other
- Dependencies are resolved and downloaded automatically when a mod requiring them is installed
- Mods installed through R2ModMan Plus do not alter the base game files in the installation directory
- Critical note: Always launch the game through R2ModMan Plus rather than directly through Steam to ensure mods load correctly
- Key insight: R2ModMan Plus separates mod files from the base game directory entirely, making uninstalling all mods as simple as launching the game without the manager
What R2ModMan Plus Is and How It Differs from Manual Modding
Manual modding requires players to locate correct file paths, download the right versions, place files in exact directory positions, and manually track which mods depend on which other mods. A single misplaced file or missed dependency causes the entire mod setup to fail silently or crash on launch.
R2ModMan Plus replaces every one of those manual steps with an automated system that handles file management, dependency tracking, and version control behind the scenes.
The Core Architecture Behind R2ModMan Plus
R2ModMan Plus operates by maintaining its own dedicated directory for each game it manages, completely separate from the game’s Steam installation folder. Mods are downloaded and stored within this managed directory rather than injected directly into the game files.
When the game is launched through R2ModManager Plus, the manager temporarily bridges its mod directory with the game’s expected file paths, making mods visible to the game without permanently altering the base installation.
This architecture produces two significant advantages. The base game files remain completely untouched at all times, meaning verifying game files through Steam always restores a clean state. And removing all mods requires nothing more than launching the game outside of R2ModMan Plus.
How R2ModMan Plus Compares to Manual Installation
Players who have modded games manually before will recognize the friction that R2ModMan Plus eliminates.
Key differences between the two approaches:
- File placement: Manual requires exact directory knowledge. R2ModMan Plus handles placement automatically based on each mod’s package structure
- Dependency tracking: Manual requires identifying and downloading each dependency individually. R2ModMan Plus resolves and installs the full dependency chain from a single mod install click
- Version management: Manual requires tracking versions in file names. R2ModMan Plus maintains version records and flags outdated mods with update notifications
- Conflict detection: Manual has no conflict detection. R2ModMan Plus identifies known incompatibilities during installation
- Uninstallation: Manual requires locating and deleting individual files. R2ModMan Plus removes mods cleanly with one click without risking deletion of shared files used by other mods
What Mods, Dependencies, and Profiles Mean in R2ModMan Plus
Three concepts form the foundation of how R2ModMan Plus organizes and manages modded game setups. Understanding each one clarifies why the manager behaves the way it does and how to use it most effectively.
These are not interchangeable terms. Each refers to a distinct layer of the mod management system with its own rules and behaviors.
How Mods Work Within R2ModMan Plus
In R2ModMan Plus, a mod is any package downloaded from the Thunderstore repository for a supported game. Each mod package contains the mod files themselves, a manifest file declaring the mod’s name and version, and a dependency string listing any other packages the mod requires to function.
When a mod is installed through R2ModMan Plus, the manager reads the manifest, downloads the correct files, places them in the managed directory for that game, and records the installation in the profile’s mod list.
Mods can be individually enabled or disabled within a profile without uninstalling them. A disabled mod remains downloaded and stored but is excluded from the game’s load sequence when launched through the manager. This allows players to toggle mods on and off between sessions without re downloading files each time.
Mods installed through R2ModMan Plus should never be manually moved or deleted from the managed directory using a file browser. Manual file changes bypass the manager’s tracking system and produce orphaned records that cause inconsistent behavior.
How Dependency Resolution Works
Dependencies are other mods or frameworks that a mod requires to function. The most common example in the Thunderstore ecosystem is BepInEx, the modding framework that most game mods are built on top of. Nearly every mod for games like Lethal Company lists BepInEx as a dependency.
When a mod with dependencies is installed through R2ModMan Plus, the manager performs the following sequence automatically:
- Reads the dependency string in the mod’s manifest file
- Checks whether each listed dependency is already installed in the active profile
- Downloads and installs any missing dependencies from Thunderstore
- Checks those dependencies for their own dependencies and repeats the process recursively
- Confirms all required packages are present before completing the installation
This recursive resolution means installing a single mod can trigger the automatic installation of several supporting packages without any additional input from the player. The full dependency tree is handled in one operation.
Dependencies are never automatically removed when the mod that required them is uninstalled. This is intentional behavior designed to prevent removing a package that another installed mod also depends on. Unused dependencies can be identified and cleaned up manually through the manager’s interface.
How Profiles Isolate Mod Configurations
Profiles are R2ModMan Plus’s most powerful organizational feature. Each profile is a completely independent mod environment with its own mod list, enabled states, configuration files, and settings.
Switching between profiles changes the entire mod setup that launches with the game without affecting any other profile’s contents.
Practical uses for multiple profiles include:
- Vanilla profile: An empty profile with no mods for clean unmodded gameplay or troubleshooting
- Stable profile: A tested and confirmed working mod list for regular play sessions
- Testing profile: An isolated environment for trying new or experimental mods without risking the stable setup
- Multiplayer profile: A specific mod list matching the requirements of a particular server or friend group
- Content type profiles: Separate profiles for different mod categories such as cosmetic only versus gameplay overhaul setups
Profiles do not share mod files between them by default. A mod installed in one profile must be installed separately in another profile to be active there. This isolation is intentional and prevents one profile’s changes from destabilizing another.
How to Use R2ModMan Plus Effectively Day to Day
Understanding the architecture and core concepts is the foundation, but effective daily use of R2ModMan Plus depends on a consistent workflow that keeps profiles stable and mod lists organized.
The most common source of mod setup instability is an inconsistent workflow rather than broken mods or software bugs.
The Standard Mod Installation Workflow
Follow this sequence every time a new mod is added to a profile to maintain stability and avoid dependency conflicts.
Standard installation steps:
- Open R2ModMan Plus and confirm the correct game is selected from the game selector
- Confirm the correct profile is active before making any changes
- Navigate to the Online tab to browse Thunderstore mods for the selected game
- Use the search function to locate the desired mod by name or keyword
- Click the mod listing to review its description, version history, and dependency list before installing
- Click Download and allow R2ModMan Plus to resolve and install all dependencies automatically
- Review the list of newly installed packages including dependencies to confirm expected results
- Launch the game through R2ModMan Plus using the Start Modded button to test the new mod
Never install mods directly from a mod author’s personal website or file sharing service into the R2ModMan Plus managed directory. Externally sourced files bypass dependency tracking and version management, producing a partially tracked setup that is difficult to troubleshoot.
Managing Profiles for Different Use Cases
| Profile Type | Mods Included | Primary Use |
| Vanilla | None | Clean gameplay and bug reporting |
| Stable | Tested working mod list | Regular daily play |
| Testing | Experimental or new mods | Evaluating new content safely |
| Multiplayer | Server required mods only | Joining specific modded servers |
| Overhaul | Large gameplay changing mods | Extended dedicated playthroughs |
| Cosmetic | Visual and audio mods only | Vanilla gameplay with aesthetic changes |
Creating a new profile before attempting significant mod list changes preserves the current working state. If the new configuration produces problems, the original profile remains intact and accessible without any recovery steps required.
Common Problems and Solutions:
- Game crashes on launch through R2ModManager Plus Disable all mods and re enable them one at a time to identify the problem mod, then check its Thunderstore page for known issues or required configuration steps
- Mods not loading despite being installed and enabled Confirm the game is being launched through R2ModMan Plus and not directly through Steam. Direct Steam launch bypasses the mod bridging system entirely
- Dependency listed as missing despite being installed The installed dependency version may not satisfy the requiring mod’s minimum version requirement. Update the dependency through the manager’s update interface
- Profile disappeared after an R2ModMan Plus update Profiles are stored in R2ModMan Plus’s own data directory. Check the manager’s data folder for profile subfolders and restore through the profile import function if the folder structure is intact
- Mod configuration changes not saving between sessions Configuration files for mods are stored within the profile directory. Confirm changes are being saved within the game session and that the correct profile is active on relaunch
Exporting, Sharing, and Importing Profiles
R2ModMan Plus includes a profile export system that packages the complete mod list, version data, and configuration into a shareable file or code. This is the standard method for sharing a specific mod setup with another player or transferring a working configuration between machines.
Profile sharing is widely used by multiplayer communities where all players need an identical mod list to connect to the same server without version mismatches causing join failures.
Exporting a Profile for Sharing or Backup
To export a profile, navigate to the Profile section within R2ModMan Plus and select the export option. R2ModMan Plus generates either a shareable code string or a downloadable file depending on the export format selected.
The export contains the complete record of installed mods and their versions but does not include mod files themselves. The recipient must import the profile code into their own R2ModMan Plus installation, which then downloads all listed mods and dependencies fresh from Thunderstore.
This approach keeps export files small and ensures recipients always receive the current Thunderstore hosted version of each listed mod matching the specified version numbers.
Importing a Profile from Another Player
Importing a shared profile requires the profile code or export file provided by the sharing player. Navigate to the Profile section in R2ModMan Plus, select Import, and paste the code or locate the export file.
R2ModMan Plus reads the mod list from the import data, resolves the full dependency tree, and downloads all required packages automatically. The imported profile appears as a new independent profile in the manager without affecting any existing profiles.
Confirm game and version compatibility before importing a profile shared by another player. Profiles built for a specific game version or mod framework version may produce errors if the recipient’s game client is on a different patch level.
Frequently Asked Questions
Does r2modman modify base game files in Steam directory?
No. R2ModMan Plus maintains its own separate managed directory for each game. Base game files in the Steam directory remain completely untouched. Verifying game files through Steam always restores a clean unmodded state regardless of what is installed in R2ModMan Plus.
Why launch the game through r2modman instead of Steam?
R2ModMan Plus bridges its managed mod directory with the game’s expected file paths at launch time. Launching through Steam bypasses this bridge entirely, meaning the game runs without any mods regardless of what is installed in the manager.
Can the same mod be installed in multiple profiles simultaneously?
Yes. Each profile maintains its own independent mod list and file copies. The same mod can be installed in as many profiles as needed without conflicts between them. Disk space is the only practical limitation as files are not shared between profiles.
What happens to dependencies when a mod is uninstalled?
Dependencies remain installed after the requiring mod is removed. R2ModMan Plus does not automatically remove shared packages to avoid breaking other mods that may also depend on them. Unused dependencies can be identified and removed manually through the manager interface.
Is R2ModMan Plus safe to use and free of malware?
R2ModMan Plus is fully open source and hosted at github.com/ebkr/r2modmanPlus. Its code is publicly visible and reviewed by the community. Download only from the official GitHub repository or thunderstore.io to ensure file integrity. Third party download sites should be avoided regardless of claimed legitimacy.
Can R2ModMan Plus be used for games not listed in its game selector?
R2ModMan Plus supports games listed in its official game catalog tied to the Thunderstore ecosystem. Games outside this catalog are not officially supported. Attempting to use the manager for unsupported games is not recommended and may produce unpredictable file management behavior.
How do I completely remove all mods without uninstalling R2ModMan Plus?
Launch the game directly through Steam rather than through R2ModMan Plus. This bypasses the mod bridging system and runs the game in a completely unmodded state. Alternatively, switch to an empty vanilla profile within R2ModMan Plus and launch from there to maintain the managed environment while playing without mods.
What should I do if R2ModMan Plus itself fails to open or crashes on startup?
Check the R2ModMan Plus GitHub issues page at github.com/ebkr/r2modmanPlus for reports matching your operating system and symptoms. Common startup failures on Windows relate to missing runtime dependencies such as specific Visual C++ redistributable versions. The GitHub releases page includes installation notes addressing known startup requirements by operating system.
Latest Post:
