Introduction
R2ModManPlus compatibility inherits its game support foundation from the base R2ModMan tool and the broader Thunderstore mod repository ecosystem. However, compatibility in R2ModMan Plus extends beyond simply listing supported titles.
It encompasses how the tool handles game version changes, mod API dependencies, and the framework layers that sit between the game client and the installed mods themselves.
Understanding this compatibility structure prevents failed mod installations, broken game launches, and hours of troubleshooting caused by mismatched versions between the game, the mod framework, and the mods themselves.
Quick Facts R2ModManPlus Supported Game Versions
- R2ModMan Plus supports all games available through the Thunderstore mod repository ecosystem including Risk of Rain 2, Lethal Company, Valheim, Dyson Sphere Program, and Sunkenland
- Game version compatibility depends on three layers: the game client version, the mod framework version such as BepInEx, and the individual mod’s declared compatibility
- BepInEx is the primary mod API framework used across the majority of Thunderstore-supported games and must match the target game version to function correctly
- R2ModMan Plus displays compatibility warnings for mods flagged as untested or broken against the current game version
- Mod API compatibility is not guaranteed across major game updates and mods require developer updates to restore compatibility after significant patches
- R2ModMan Plus profiles allow version-locked configurations that preserve a known working mod setup independently of game updates
- MelonLoader is used as an alternative mod framework for specific games such as Among Us and Boneworks where BepInEx is not the standard
- Manual game path configuration is required when games are installed outside default Steam library locations
- Always verify framework version compatibility before installing a large mod list to avoid cascading dependency failures
What Games R2ModMan Plus Supports and How Compatibility Is Determined
R2ModMan Plus draws its supported game list directly from the Thunderstore platform. Any game with an active Thunderstore mod community and a published mod repository is accessible through R2ModMan Plus provided the correct version of the tool is installed.
Game support is not static. New titles are added to Thunderstore regularly, and R2ModMan Plus updates incorporate those additions as they are verified and integrated.
The Thunderstore Game Library and Version Alignment
Thunderstore maintains a curated list of games with active mod ecosystems. R2ModManager Plus connects to this list at launch and displays all available games for profile creation and mod management.
The connection between R2ModMan Plus and Thunderstore means that game support in the tool reflects what Thunderstore currently hosts rather than a fixed internal list.
Games with confirmed and active R2ModMan Plus support include:
- Risk of Rain 2 primary supported title with the most extensive mod library
- Lethal Company rapidly growing mod ecosystem with strong BepInEx framework support
- Valheim large mod library with both BepInEx and Nexus-adjacent mods
- Dyson Sphere Program active community with framework-dependent mod support
- Sunkenland newer addition with growing Thunderstore presence
- Deep Rock Galactic active mod community with verified R2ModMan Plus compatibility
- GTFO supported through Thunderstore with MelonLoader framework dependency
- Boneworks and Bonelab MelonLoader framework games with distinct compatibility requirements
Game version alignment means the installed game client version must be compatible with the mod framework version installed through R2ModMan Plus.
When a game updates on Steam or another platform:
- The game client version increments
- Existing mod frameworks may no longer inject correctly into the updated client
- Individual mods built against the previous API may throw errors or fail silently
- R2ModMan Plus flags outdated framework versions when it detects a version mismatch between the installed framework and the current game build
How R2ModMan Plus Detects and Reports Compatibility Issues
R2ModMan Plus uses several detection mechanisms to identify compatibility problems before they cause in-game failures.
The primary detection method is comparing the installed mod framework version against the game’s current build identifier.
Compatibility detection mechanisms in R2ModMan Plus:
- Framework version comparison against the current game executable build
- Thunderstore metadata flags indicating mods marked as deprecated or broken
- Dependency tree validation that checks whether all required dependency versions are mutually compatible
- User-reported compatibility notes surfaced from Thunderstore mod pages within the manager interface
When a compatibility issue is detected, R2ModManager Plus displays a warning at the profile level or next to the specific mod or framework version causing the conflict.
These warnings do not block installation or game launch by default. They are informational indicators that give the player the context needed to make an informed decision before proceeding.
How Mod API Frameworks Work Within R2ModMan Plus
Mod API frameworks are the technical bridge between the game client and the mods installed through R2ModManager Plus. Without a correctly installed and version-matched framework, mods cannot load regardless of how they are configured in the manager.
Understanding which framework a specific game uses and how R2ModMan Plus manages that framework is essential for maintaining a stable mod setup across game updates.
BepInEx: The Primary Framework and Version Management
BepInEx is the most widely used mod framework across Thunderstore-supported games. It functions as a plugin loader that injects into the game process at launch and loads all compatible mods from the designated plugins folder.
R2ModMan Plus installs BepInEx automatically as a dependency when the first mod requiring it is added to a profile.
BepInEx version considerations in R2ModMan Plus:
- BepInEx 5 is used for most Unity Mono games including Risk of Rain 2 and Valheim
- BepInEx 6 is required for Unity IL2CPP games and newer titles moving to that runtime
- Installing the wrong BepInEx version for the game’s Unity runtime causes a silent launch failure
- R2ModMan Plus selects the correct BepInEx version automatically in most cases based on the game’s declared framework requirement on Thunderstore
When a game updates its Unity version or switches runtimes, the required BepInEx version may change. This is one of the most common sources of complete mod failure following a major game patch.
Signs that BepInEx is mismatched after a game update:
- Game launches and closes immediately with no error displayed
- Mods do not load despite appearing correctly installed in R2ModManager Plus
- BepInEx log file shows framework initialization errors at the top of the log output
- No BepInEx console window appears at launch when it previously did
MelonLoader and Alternative Framework Compatibility
MelonLoader serves as the mod framework for games that do not support BepInEx injection. These are primarily IL2CPP Unity games where BepInEx 5 cannot function and where the game developer or modding community has standardized on MelonLoader instead.
R2ModMan Plus handles MelonLoader installation and management through the same profile system used for BepInEx games.
Games using MelonLoader through R2ModMan Plus include:
- Boneworks and Bonelab
- Among Us
- GTFO in some mod configurations
- Specific titles where the Thunderstore community has standardized on MelonLoader over BepInEx alternatives
MelonLoader has its own versioning considerations separate from BepInEx. A MelonLoader version built for an older game build may fail to inject into an updated game executable in the same way BepInEx version mismatches cause failures.
Common Problems and Solutions:
- BepInEx not injecting after game update update BepInEx to the latest version through R2ModMan Plus by checking for framework updates in the installed mod list within the affected profile
- MelonLoader failing to launch with the game confirm the MelonLoader version matches the current game build; check the MelonLoader GitHub for game-specific version compatibility notes
- Mods loading but immediately crashing the game a specific mod is incompatible with the current game version; disable mods one at a time starting with recently updated ones to isolate the cause
- R2ModMan Plus not showing framework update options manually refresh the Thunderstore mod cache through settings and check whether the framework has a new release available
- Dependency version conflicts between mods check each mod’s declared dependency version against the installed framework version; conflicting dependency declarations require manual version pinning or waiting for mod updates
Managing Compatibility Across Game Updates and Mod Versions
Game updates are the primary source of compatibility disruption in any mod ecosystem. R2ModMan Plus provides tools to manage the transition period between a game update releasing and the mod community catching up with compatible releases.
Knowing how to use these tools correctly reduces downtime and prevents the frustration of a broken mod setup immediately after a game patch.
Profile Locking and Version Pinning Strategies
Profile locking in R2ModManager Plus allows a complete mod configuration to be preserved in a known working state. When a game updates and breaks compatibility, the locked profile retains the previous framework and mod versions without being affected by automatic updates.
How to implement a stability-focused profile strategy:
- Create two separate profiles for each heavily modded game
- Designate one profile as the stable locked configuration and one as the active update-testing profile
- Disable automatic updates on the stable profile to prevent mod or framework updates from disrupting a working setup
- Test new game updates and mod compatibility changes on the active profile before migrating confirmed stable configurations to the locked profile
Version pinning for individual mods allows specific mods to remain at a fixed version while other mods in the same profile update normally.
This is particularly useful for framework mods and core dependency packages where a version change can affect the entire mod list rather than a single mod.
Monitoring Thunderstore for Compatibility Updates
After a game patch, the Thunderstore community typically responds within hours to days with framework and mod updates. R2ModMan Plus surfaces this update activity directly within the manager interface.
Post-patch compatibility monitoring workflow:
- After a game update, open R2ModMan Plus before launching the game
- Check the installed mod list for update indicators on framework packages first
- Update BepInEx or MelonLoader before updating individual mods to ensure the framework layer is stable before loading dependent mods
- Review update changelogs within R2ModMan Plus before applying updates to identify any breaking changes noted by mod developers
- Launch the game through R2ModMan Plus after framework updates and test stability before applying individual mod updates in batches
Batch updating all mods immediately after a game patch without reviewing changelogs is the most common cause of new instability following what should be a routine update cycle.
Update individual mods in small groups rather than all at once to make it easier to identify which specific update introduced a new problem if instability appears after the update cycle.
Frequently Asked Questions
How do I find the right BepInEx version for my game?
R2ModMan Plus selects the correct BepInEx version automatically based on the game’s framework declaration on Thunderstore in most cases. If you need to verify manually, check the game’s Thunderstore page or community wiki for the declared framework requirement. BepInEx 5 covers most Unity Mono games while BepInEx 6 is required for IL2CPP runtime games.
Why do my mods stop working after every game update?
Game updates frequently change the game executable or Unity runtime in ways that break mod framework injection. After each update, the framework such as BepInEx or MelonLoader requires an update to match the new game build before any mods can load. Updating the framework first through R2ModMan Plus before relaunching the game resolves this in the majority of post-update failures.
Can R2ModMan Plus prevent a game from auto-updating and breaking my mods?
R2ModMan Plus itself cannot prevent game updates delivered through Steam or other platforms. To prevent unwanted updates, use Steam’s update settings for the specific game and set it to only update when launched. Launching the game exclusively through R2ModMan Plus rather than Steam directly helps manage when updates are applied.
What is the difference between deprecated and incompatible mods?
A deprecated mod has been officially marked by its developer as no longer maintained or replaced by a newer version. An incompatible mod functions but does not work correctly with the current game or framework version. Deprecated mods should be replaced with their stated successors. Incompatible mods may recover compatibility when the developer releases an update.
How do I find the BepInEx log file to diagnose framework errors?
The BepInEx log file is located at [GameInstallDirectory]/BepInEx/LogOutput.log. This file records all framework initialization events, mod loading attempts, and errors at launch. Opening this file after a failed mod launch is the most reliable first step for diagnosing framework-level compatibility problems.
Does R2ModMan Plus support games purchased outside of Steam?
R2ModMan Plus supports manual game path configuration for games installed outside Steam or in non-default library locations. Navigate to the game settings within R2ModMan Plus and specify the correct installation directory manually. Games from Epic Games Store, GOG, or standalone launchers can be configured this way provided the game has Thunderstore mod support.
Can I share a working mod profile with other players using R2ModMan Plus?
Yes. R2ModMan Plus supports profile export as a shareable code or file that other players can import directly. This transfers the complete mod list and version configuration to another installation. The receiving player must have R2ModMan Plus installed and the same game to import and use the shared profile correctly.
Mods broken after patch but no updates available. What to do?
If no updates are available yet, the mod community has not yet released patch-compatible versions. The practical options are to wait for developer updates, revert the game to a previous version using Steam’s beta branch settings if available, or use R2ModMan Plus’s rollback feature to restore previously working mod versions while waiting for updated releases.
Latest Post:
- R2ModManPlus compatibility Game Versions & Mod API Compatibility
- Is R2ModManPlus Safe? Security, Trusted Downloads & Anti‑Cheat
- How R2ModManPlus Works: Mods, Dependencies & Profiles Explained
- R2ModManPlus Features Overview Themes, Updates & Compatibility
- What Is R2ModManPlus? Complete Mod Manager Guide for Risk of Rain 2
