How to Update R2ModManPlus Without Breaking Mods

Introduction

Updating r2modmanager is a routine part of maintaining a healthy Risk of Rain 2 modding setup. The application receives regular updates that improve compatibility, fix bugs, and add new features. However, updating any tool that manages mod files raises a legitimate question about whether the update process itself can disrupt an existing working mod configuration.

The good news is that r2modmanager is designed with mod safety in mind. Its update process does not overwrite or delete mod profile data in the vast majority of cases. Understanding exactly how updates work and what precautions to take beforehand eliminates any uncertainty about keeping your mod setup intact through an application update.

Quick Facts about How to Update R2ModManPlus

• R2modman stores mod profiles separately from the application itself meaning application updates do not delete installed mods
• Profile data is stored in a dedicated data directory that the r2modman update process does not touch
• Backing up your profile data before updating adds a safety layer that takes under two minutes to complete
• R2modman updates are distributed through the GitHub releases page and through an in app update notification system
• The in app auto update is the safest and recommended update method for most players
• Mod files themselves do not update automatically when r2modman updates; mod updates are a separate process within the application
• After updating r2modman, always verify your profiles and installed mods are intact before launching the game
• Corrupted application updates are rare but resolved through a clean reinstall that preserves profile data if backed up
• Players on Windows, macOS, and Linux each have slightly different update experiences due to operating system packaging differences

What Happens to Your Mods When R2ModManPlus Updates?

Understanding the architecture of how r2modman stores data is the foundation for understanding why updates are generally safe for existing mod configurations. The application and its managed data live in separate locations on your system by design.

This separation means updating the r2modman application binary is effectively independent from the mod profiles and files it manages.

How R2ModManPlus Separates Application and Profile Data

R2modman stores its application files in a standard program installation directory. On Windows this is typically within the Program Files directory or the user’s AppData\Local folder depending on the installation type chosen during setup.

Mod profile data, including all installed mod files, profile configurations, and BepInEx directory structures, is stored in a completely separate data directory. On Windows this is typically located in the user’s AppData\Roaming folder under an r2modman subfolder.

Why this separation matters for update safety:

• Application updates replace only the files in the installation directory
• The data directory containing mod profiles is never targeted by the application update process
• A clean reinstall of r2modman, even if the application is fully uninstalled first, does not delete profile data stored in the data directory
• Profile data persists across r2modman version changes without requiring any action from the player
• This architecture means a failed or corrupted application update can be resolved without any risk to installed mods

What the R2ModManPlus Update Process Actually Changes

When r2modman updates, it replaces the application executable and its supporting files with the new version. Interface improvements, bug fixes, and new features are all contained within these application files.

No mod files, profile configurations, BepInEx installations, or saved settings stored in the data directory are modified during a standard application update.

Files changed during an r2modman application update:

• The main r2modman executable file
• Supporting application libraries and resources bundled with the application
• Application configuration files related to the program itself rather than mod profiles
• Cached Thunderstore data may be refreshed to reflect the current mod catalog structure

Files not changed during an r2modman application update:

• All mod files installed within any profile
• Profile configuration and enabled or disabled mod states
• BepInEx installations managed within each profile
• Custom profile names and organization created by the player
• Any manually added files placed within profile directories

How to Safely Back Up Your R2ModManager Plus Profiles Before Updating

While the r2modman update process is designed to preserve profile data, creating a manual backup before any application update is a straightforward precaution that eliminates all risk of data loss in the unlikely event something goes wrong.

This process takes under two minutes and provides complete recovery capability if a backup is ever needed.

Locating the R2ModManPlus Data Directory

The data directory location varies by operating system. Knowing the exact path on your system is the first step in creating a manual backup of your profile data.

Data directory locations by operating system:

• Windows: Navigate to C:\Users\YourUsername\AppData\Roaming\r2modmanPlus-local or access it by typing %appdata%\r2modmanPlus-local in the Windows Run dialog
• macOS: Navigate to ~/Library/Application Support/r2modmanPlus-local through Finder with hidden folders visible
• Linux: Navigate to ~/.config/r2modmanPlus-local in your file manager with hidden directories shown
• Steam Deck: Access through the file manager at /home/deck/.config/r2modmanPlus-local in desktop mode

Within the data directory you will find subfolders for each game r2modman manages, with Risk of Rain 2 data stored under a RiskOfRain2 subfolder containing all profile directories.

Creating a Manual Profile Backup

With the data directory located, creating a backup is a simple copy operation that duplicates the entire r2modmanPlus-local folder to a safe secondary location.

Step by step backup process before updating r2modman:

• Close r2modman completely before beginning the backup process
• Navigate to the data directory using the path appropriate for your operating system
• Right click the r2modmanPlus-local folder and select Copy
• Navigate to a backup location such as a separate drive, a cloud storage folder, or an external storage device
• Paste the copied folder into the backup location
• Confirm the copy completed successfully by verifying the backup folder contains the same subfolders as the original
• Label the backup with the current date and r2modman version number for future reference
• Proceed with the r2modman application update only after confirming the backup is complete

Additional backup considerations for comprehensive protection:

• Store backups in a location separate from your primary drive to protect against drive failure
• Cloud storage services such as Google Drive or OneDrive provide automatic offsite backup when the data directory is copied there
• Repeat this backup process before every r2modman update as a standard practice rather than only when something seems uncertain
• Retain at least two previous backups rather than overwriting the single most recent one

Common Problems and Solutions:

• Problem: The AppData folder is not visible when navigating in Windows Explorer Solution: Enable hidden items in Windows Explorer by opening the View menu and checking the Hidden items option; AppData is a hidden folder by default on Windows
• Problem: The backup copy process fails partway through due to a file permission error Solution: Close r2modman and any running instances of Risk of Rain 2 before attempting the backup; open files cannot be copied correctly while in use
• Problem: The data directory cannot be located at the expected path on your system Solution: Open r2modman, navigate to Settings, and look for a data directory or profile location option that shows the exact path r2modman is using on your specific installation
• Problem: The backup folder is too large to fit in the intended backup location Solution: Mod files within profiles can accumulate significant size over time; free up space in the backup location or use a larger capacity storage option before proceeding
• Problem: After restoring a backup the profiles appear but mods are listed as not installed Solution: The backup may have been taken at a point where the data directory structure was incomplete; use the backup as a profile configuration reference and reinstall mod files through r2modman’s Online tab

How to Update R2ModManager Plus Using Each Available Method

R2modman provides two update paths: the in app automatic update notification and manual download from the GitHub releases page. Each method is appropriate in different situations and both preserve profile data when performed correctly.

Updating Through the In App Notification System

The in app update is the simplest and most recommended update method for the majority of players. When a new r2modman version is released, the application displays an update notification on launch that guides you through the update process automatically.

This method handles the download, replacement of application files, and relaunch sequence without requiring manual file management.

Step by step in app update process:

• Launch r2modman as normal and wait for the application to fully load
• If an update is available, a notification will appear either on the main screen or as a banner at the top of the interface
• Read the update notification to note what changes the new version introduces
• Click the Update or Download update button presented in the notification
• R2modman will download the new version and prompt you to allow the update to be applied
• Allow the application to close and relaunch as part of the update sequence
• Wait for r2modman to reopen with the updated version active
• Navigate to your mod profiles and confirm all profiles and installed mods are listed correctly
• Check that the version number displayed in r2modman’s settings or about section reflects the new version
• Launch Risk of Rain 2 in modded mode and confirm mods load correctly before beginning a play session

Updating R2ModManPlus Manually Through GitHub

Manual updating is appropriate when the in app notification is not appearing despite a known new release being available, or when you prefer direct control over the update file being applied to your system.

The GitHub releases page at github.com/ebkr/r2modmanPlus is the authoritative source for all official r2modman releases.

Step by step manual update process:

• Ensure your profile backup is complete before proceeding with the manual update
• Navigate to github.com/ebkr/r2modmanPlus and click the Releases section
• Identify the latest release at the top of the releases list and confirm it is newer than your currently installed version
• Download the installer file appropriate for your operating system from the release assets
• Close r2modman completely before running the new installer
• Run the downloaded installer and follow the on screen prompts to complete the update
• The installer will replace the existing application files with the new version
• Launch r2modman after installation completes and verify it opens to the correct version
• Navigate to your profiles and confirm all mod data is intact before launching the game
• Cross reference the downloaded file checksum against the value listed on the GitHub release page if you want to verify file integrity before installing

Handling a Failed or Corrupted R2ModManPlus Update

In rare cases an update may fail partway through or produce a corrupted installation that prevents r2modman from launching correctly. This situation is recoverable without any loss of mod profile data provided your backup is in place.

Step by step recovery from a failed r2modman update:

• Attempt to launch r2modman and note the specific error message or behavior that indicates the corruption
• Fully uninstall r2modman through your operating system’s standard application removal process
• Confirm the data directory at the AppData or equivalent path is still intact after uninstalling
• Do not delete the data directory during or after uninstalling; the uninstaller targets only application files
• Download the latest r2modman installer from github.com/ebkr/r2modmanPlus
• Run the fresh installer to perform a clean installation of r2modman
• Launch the newly installed r2modman and verify it detects your existing profile data automatically
• If profile data is not detected automatically, copy the backed up data directory to the expected location
• Confirm all profiles and installed mods are visible before launching the game

Updating Mods After Updating R2ModManPlus

An r2modman application update does not automatically update the mods installed within your profiles. Mod updates are a separate process performed within the application after the r2modman update itself is complete.

After updating r2modman it is good practice to check for available mod updates, particularly if the r2modman update was prompted by a new Risk of Rain 2 game patch that may have also triggered updates in compatible mods.

How to check for and apply mod updates after an r2modman update:

• Open r2modman and navigate to the active profile you want to update mods within
• Go to the Installed tab and look for update indicators next to individual mods
• Alternatively use the Update all option if available to apply all pending mod updates simultaneously
• Review which mods are being updated before confirming to avoid unintentionally updating a mod you had pinned to a specific version
• After applying mod updates, launch Risk of Rain 2 in modded mode and verify all mods load correctly
• Check the BepInEx log if any mods fail to load after updating, as update conflicts occasionally appear in the log before they produce visible in game errors

R2ModManPlus Update Safety Reference Table

Update Scenario	Profile Data Risk	Recommended Action	Recovery If Needed
In app automatic update	Very low	Proceed after backing up profiles	Restore backup to data directory
Manual GitHub installer update	Very low	Back up first, close r2modman before installing	Restore backup to data directory
Failed update corrupting application	None to profiles	Clean reinstall of application only	Fresh install detects existing data
Clean uninstall and reinstall	None if data directory preserved	Confirm data directory intact before uninstalling	Copy backup to data directory location
Update on shared or multi user system	Low	Back up per user data directories separately	Restore individual user backups
Update followed by mod updates	Low	Update mods separately after confirming r2modman update success	Revert individual mod versions through Installed tab

Frequently Asked Questions

Latest Post:

• R2ModManPlus Theme Customization (UI & Layout)
• How Auto‑Update Plugins & Mod Sync Works
• How to Create Your First Mod Pack With R2ModManPlus
• How to Use R2ModManPlus Profiles for Different Game Modes
• How to Disable/Enable Mods Quickly With R2ModManPlus