Introduction
Opening R2ModManPlus missing mods after an update and finding your installed mods missing or your profile appearing empty is an alarming experience. Hours of mod configuration and a carefully curated profile setup appearing to vanish after a routine application update understandably causes concern.
The reality is that mod data loss from an r2modmanager update is extremely rare. What appears as missing mods is almost always a profile detection issue, a data directory path mismatch, or a display error that resolves without any actual mod data having been deleted. Understanding what actually happened and working through the correct fix restores your setup in most cases within minutes.
Quick Answer about R2ModManPlus Shows Missing Mods
- Actual mod data deletion from an r2modman update is extremely rare as the update process targets only application files
- Missing mods after an update most commonly indicate a profile detection failure rather than genuine data loss
- R2modman stores mod data in a separate data directory that application updates do not touch or overwrite
- A data directory path mismatch after an update causes r2modman to look for profiles in the wrong location, making existing data appear absent
- Switching to the correct profile in the profile selector resolves missing mod displays caused by r2modman defaulting to a new empty profile after an update
- The data directory at %appdata%\r2modmanPlus-local on Windows almost always contains intact profile data even when r2modman displays nothing
- Cache corruption from an interrupted update can cause the profile display to show incorrect or empty data without affecting underlying mod files
- A profile backup created before updating provides complete recovery capability if genuine data issues are confirmed
- Reinstalling r2modman over an existing installation without deleting the data directory restores correct profile detection in the majority of missing mod cases
What Actually Happens to Mod Data During an R2ModManPlus Update?
The most important fact to establish immediately when mods appear missing after an update is that r2modman’s update mechanism does not target or modify the data directory where mod profiles are stored. The update replaces only the application executable and its supporting files.
Understanding this separation between application files and profile data eliminates the fear of permanent data loss and reframes the problem as a detection or display issue rather than a deletion event.
How R2ModManPlus Separates Application and Profile Storage
R2modman uses two distinct storage locations that serve completely different purposes. The application installation directory contains the program files that make r2modman run. The data directory contains everything the player has configured including mod profiles, installed mod files, BepInEx installations, and profile settings.
These two locations are completely independent. Updating, repairing, or even fully uninstalling the application installation does not affect the data directory.
Application installation directory contents:
- The r2modman executable file
- Overwolf platform files and libraries
- Application resources and interface assets
- No mod files or profile data are stored here
Data directory contents that updates never touch:
- All mod profile folders and their configurations
- Installed mod files downloaded from Thunderstore
- BepInEx installations managed within each profile
- Profile enable and disable states for individual mods
- Custom profile names and organizational structure created by the player
Why Mods Appear Missing After an Update
If the update does not touch profile data, the appearance of missing mods must have another cause. Several specific scenarios produce this symptom without any actual data having been deleted.
Scenarios that cause mods to appear missing without data loss:
- R2modman defaults to a new empty default profile after an update rather than the previously active profile, making the previously configured profile appear absent until manually selected
- A data directory path change in the new r2modmanager version causes the application to look for profiles in a different location than where the existing data is stored
- Cache corruption from an interrupted update causes the profile display to render incorrectly without reflecting the actual state of the data directory
- The update process reset application settings including the remembered active profile, causing r2modman to open on a blank default state
- A Thunderstore connection failure on first launch after updating prevents profile mod data from being verified against the online catalog, causing some mods to appear with unknown status
How to Diagnose Why Mods Are Showing as Missing
Before attempting any fix, confirming whether the mod data actually exists in the data directory eliminates the uncertainty of not knowing whether you are dealing with a display issue or genuine data loss.
This confirmation takes under two minutes and determines the entire troubleshooting path.
Verifying Mod Data Exists in the Data Directory
Navigating directly to the data directory and checking for profile folders confirms whether mod data is present regardless of what r2modmanager’s interface is displaying.
Step by step data directory verification:
- Close r2modman completely before checking the data directory
- On Windows, open the Run dialog by pressing the Windows key plus R
- Type %appdata%\r2modmanPlus-local and press Enter
- Confirm the folder opens and contains subfolders for each game r2modman manages
- Navigate into the RiskOfRain2 subfolder or the relevant game subfolder
- Look for profiles subfolder containing named profile folders matching your previously created profiles
- Open a profile folder and confirm it contains mod files and BepInEx directory structure
- If profile folders are present with mod files inside, the data is intact and the issue is a display or detection problem
- If the data directory is empty or absent, proceed to backup restoration before attempting other fixes
Checking the Active Profile Selection in R2ModManPlus
The profile selector in r2modman determines which profile’s mods are displayed in the interface. After an update r2modman may default to a new empty profile rather than the previously active one, making all previously installed mods appear absent from the interface.
How to check and correct the active profile selection:
- Open r2modman and look at the profile selector at the top of the interface
- Note the name of the currently displayed profile
- Click the profile selector to expand the full list of available profiles
- If your previously configured profiles appear in the list, select the correct one
- Confirm the Installed tab populates with your previously installed mods after switching profiles
- If only a default or unnamed profile appears in the selector with no other options, the profile detection issue requires further investigation
Common Problems and Solutions:
- Problem: Profile folders exist in the data directory but do not appear in the r2modman profile selector Solution: The data directory path r2modman is reading may have changed after the update; open r2modman Settings and verify the configured data directory path matches the location where your profile folders actually exist
- Problem: Profiles appear in the selector but all mods within them show as not installed Solution: The mod files are present but r2modman cannot verify them against Thunderstore; check your internet connection and reopen r2modman to allow a fresh Thunderstore verification
- Problem: The data directory is completely empty after the update Solution: Check whether a secondary data directory exists at an alternative path; r2modman occasionally creates a new data directory if the path configuration changes, leaving the original intact at its original location
- Problem: Profile names appear in the selector but selecting them shows an empty mod list Solution: Clear the r2modman cache through the Settings menu and reopen the application to force a fresh profile read from the data directory
- Problem: Only one profile appears when multiple were previously configured Solution: The update may have reset the active profile memory without affecting the data; check the profiles subfolder in the data directory for all previously created profile folders and verify they are accessible
Step by Step Fixes for Missing Mods After an R2ModManPlus Update
Working through these fixes in sequence addresses the most common causes first before escalating to more involved solutions. Most players resolve the missing mods display within the first two fixes.
Fix One: Switch to the Correct Profile in the Profile Selector
This is the single most common resolution for missing mods after an r2modman update. The update resets the active profile memory causing r2modman to open on a default empty profile rather than the previously configured one.
Step by step profile switching fix:
- Open r2modman and locate the profile selector at the top of the interface
- Click the selector to display all available profiles
- Look for profiles matching the names of your previously configured setups
- Select the correct profile from the list
- Navigate to the Installed tab and confirm mods are listed correctly
- If this resolves the display, set this profile as the default active profile in r2modman settings if that option is available
- Launch the game through Start modded to confirm mods load correctly in game
Fix Two: Correct the Data Directory Path in R2ModManPlus Settings
If the correct profiles do not appear in the profile selector despite existing in the data directory, the data directory path configured in r2modman after the update does not match where the profile data actually lives.
Step by step data directory path correction:
- Open r2modman and navigate to the Settings section
- Look for a data directory or profile storage path setting
- Note the currently configured path and compare it against the actual location of your profile folders confirmed in the verification step
- If the paths differ, update the configured path in r2modman Settings to match the actual data directory location
- Save the settings change and restart r2modman
- Confirm the profile selector now shows your previously configured profiles
- Navigate to the Installed tab within the correct profile and verify mods are listed
Fix Three: Clear Cache and Force Profile Reload
A corrupted cache from an interrupted or abnormal update process can cause r2modman to display incorrect profile and mod information without reflecting the actual state of the data directory. Clearing the cache forces r2modman to rebuild its display from the actual data files.
Step by step cache clearing for profile reload:
- Close r2modman completely
- Navigate to the data directory at %appdata%\r2modmanPlus-local
- Locate and delete the contents of any temp or cache subfolder without deleting the folders themselves
- Also clear Overwolf temporary data at %localappdata%\Overwolf
- Restart your computer before reopening r2modman
- Launch r2modman and allow it to fully reconnect to Thunderstore before checking the profile display
- Navigate to the profile selector and confirm previously configured profiles now appear correctly
Fix Four: Reinstall R2ModManPlus Over Existing Installation
If the previous fixes have not restored correct profile detection, reinstalling r2modman over the existing installation resets the application’s configuration files while preserving all data directory contents including mod profiles.
Step by step reinstall preserving profile data:
- Confirm the data directory at %appdata%\r2modmanPlus-local contains intact profile folders before proceeding
- Download the latest r2modman installer from github.com/ebkr/r2modmanPlus
- Run the installer without uninstalling the existing r2modman installation first
- Allow the installer to overwrite the existing application files
- Launch r2modman after the reinstall completes
- Check the profile selector for previously configured profiles
- If profiles now appear, navigate to each and verify the Installed tab shows correct mod listings
- Launch the game through Start modded to confirm full mod loading functionality is restored
Fix Five: Restore From Profile Backup
If all previous fixes fail to restore profile visibility and the data directory is confirmed empty or corrupted beyond repair, restoring from a pre update backup is the final recovery path.
Step by step backup restoration process:
- Locate the profile backup created before the r2modman update
- Close r2modman completely
- Navigate to the data directory location and rename the existing r2modmanPlus-local folder to r2modmanPlus-local-broken rather than deleting it
- Copy the backed up r2modmanPlus-local folder to the same location
- Launch r2modman and verify the restored profiles appear in the profile selector
- Navigate to the Installed tab within each restored profile and confirm mod listings are correct
- Update any mods that have received new releases since the backup was created before launching the game
Missing Mods Diagnostic and Fix Reference Table
| Symptom | Likely Cause | First Fix | Data Loss Risk |
| Profile selector shows empty default profile | Update reset active profile memory | Switch to correct profile | None |
| Profiles absent from selector despite data existing | Data directory path mismatch | Correct path in Settings | None |
| Profiles visible but mods show not installed | Cache corruption or Thunderstore verification failure | Clear cache and reconnect | None |
| Only one profile visible instead of multiple | Profile detection reading wrong directory | Correct data directory path | None |
| Data directory completely empty | Genuine data loss or wrong directory checked | Check alternative paths then restore backup | Possible if no backup |
| Mods listed but show outdated version warnings | Update changed version verification behavior | Update mods through Installed tab | None |
| Profile appears but BepInEx shows as missing | BepInEx entry lost from profile display | Reinstall BepInEx through Online tab | None |
| All fixes attempted with no resolution | Corrupted profile data requiring restoration | Restore from backup | Resolved by backup |
Frequently Asked Questions
Did the update delete my mods permanently?
Almost certainly not. R2modman updates target only application files and never touch the data directory where mod profiles are stored. Navigate to %appdata%\r2modmanPlus-local to confirm your profile folders and mod files are still present before concluding any data was lost.
Why is only a default profile showing now?
R2modman likely reset its active profile memory during the update, defaulting to a new empty profile on launch. Click the profile selector at the top of the interface to see all available profiles and switch to your previously configured one.
Where is my mod data actually stored?
On Windows, mod profile data is stored at %appdata%\r2modmanPlus-local. This location is separate from the r2modman application installation and is never modified by application updates, repairs, or reinstalls.
Can I recover mods without a backup?
Yes in most cases. If the data directory contains intact profile folders, correcting the data directory path in r2modman Settings or clearing the application cache restores correct profile detection without needing a backup. A backup is only essential when the data directory itself is empty or corrupted.
Why do profiles appear but mods show missing?
This typically indicates a Thunderstore verification failure rather than missing mod files. Check your internet connection and reopen r2modman to allow a fresh connection to Thunderstore. If the issue persists, clear the r2modman cache to force a complete profile reload from the actual data files.
How do I prevent this from happening again?
Create a manual backup of the %appdata%\r2modmanPlus-local folder before every r2modman update. This two minute precaution provides complete recovery capability regardless of what occurs during the update process.
Will reinstalling r2modman delete my profiles?
No. Reinstalling r2modman over an existing installation or performing a clean reinstall after uninstalling does not delete the data directory. Profile data persists through application reinstallation provided the data directory is not manually deleted.
What if the data directory is genuinely empty?
Check whether a secondary data directory exists at an alternative path, as r2modman occasionally creates a new directory if the path configuration changes. If no alternative directory is found and the data is confirmed absent, restore from your most recent profile backup.
Latest Post:
