Introduction
Losing a carefully built mod configuration is one of the most frustrating experiences in PC modding. Whether caused by a game update, an accidental profile deletion, a failed R2ModManager Plus update, or a system reset, the result is the same: hours of setup work disappear and the path to restoring it is not immediately obvious.
The good news is that lost mod configurations are recoverable in most scenarios. R2ModManager Plus stores profile data in predictable locations, and understanding where that data lives and how it is structured makes the difference between a full recovery and starting from scratch.
Quick Facts about How to Restore Lost Mod Configurations
- R2ModMan Plus stores all profile data in a dedicated data directory separate from the game installation folder
- Profile data includes the mod list, installed mod versions, configuration files, and framework settings for each profile
- The most common cause of lost configurations is a data directory path change that leaves existing profiles inaccessible rather than actually deleted
- Deleted profiles can sometimes be recovered from system-level recycle bin or backup tools if caught early enough
- Profile export codes generated before the loss allow complete profile reconstruction including mod versions without manual reinstallation
- R2ModMan Plus does not automatically back up profiles, making manual or scheduled backups the only protection against permanent configuration loss
- Game update-related configuration loss is usually a display issue caused by profile corruption rather than actual file deletion
- Mod configuration files stored within BepInEx config folders are separate from R2ModMan Plus profile data and require independent backup and restoration
- Restoring a profile on a new system requires both the profile export and a fresh R2ModMan Plus installation on the destination machine
What Gets Lost and Where Mod Configuration Data Is Stored
Before attempting any recovery, understanding exactly what was lost and where that data was stored determines which recovery method is most likely to succeed.
Not all mod configuration loss is equal. Losing a profile list is different from losing mod configuration files. Losing a single profile is different from losing all profiles simultaneously.
The R2ModMan Plus Data Directory Structure
R2ModMan Plus stores all user-generated data in a central data directory chosen during initial setup. Every profile, mod installation, and configuration file created within R2ModMan Plus lives within this directory.
The default data directory location by operating system:
- Windows: %appdata%\r2modmanPlus-local\ or the custom path selected during first launch
- Linux: ~/.config/r2modmanPlus-local/ or the AppImage-equivalent user config path
- Custom paths specified during initial setup override these defaults entirely
Within the data directory, the structure is organized by game and then by profile.
Data directory internal structure:
- [DataDirectory]\[GameName]\profiles\[ProfileName]\ contains the profile’s mod list and installed files
- [DataDirectory]\[GameName]\profiles\[ProfileName]\BepInEx\config\ contains individual mod configuration files
- [DataDirectory]\[GameName]\profiles\[ProfileName]\mods.yml is the file R2ModMan Plus reads to reconstruct the profile’s mod list
- [DataDirectory]\[GameName]\profiles\[ProfileName]\exports\ contains any previously generated export codes or files
Knowing this structure allows direct file-level recovery even when R2ModMan Plus itself cannot display the profiles correctly.
Types of Configuration Loss and Their Recovery Prospects
Different types of configuration loss have different recovery prospects. Identifying which type applies to your situation before starting recovery prevents wasted effort on approaches that cannot work for your specific case.
Type one: Profile not visible in R2ModMan Plus but files still present
This is the most recoverable scenario. The profile data exists on disk but R2ModManager Plus is not reading it correctly.
Common causes include a changed data directory path, a corrupted profile index file, or an R2ModMan Plus update that altered how profiles are detected.
Type two: Profile files deleted but recycle bin not emptied
Recoverable if the recycle bin still contains the deleted files. Restoration requires moving the files back to their original location in the data directory structure.
Type three: Profile files deleted and recycle bin emptied
Partially recoverable using file recovery software if the drive has not been heavily written to since deletion. Recovery success depends on time elapsed and drive activity since the deletion occurred.
Type four: Data directory on a reformatted or failed drive
Recoverable only if a backup exists or if drive recovery tools can reconstruct the file system. Without a backup, this scenario requires rebuilding the configuration manually.
Type five: Configuration loss due to R2ModMan Plus data directory path change
Highly recoverable. The original data directory still exists at its previous location. Pointing R2ModManager Plus back to the original path restores all profiles immediately.
How to Recover Profiles Using R2ModMan Plus Built-In Tools
R2ModMan Plus includes several built-in mechanisms for profile recovery and reconstruction. These tools should be the first recovery approach before resorting to manual file restoration or third party recovery software.
Checking and Correcting the Data Directory Path
The single most common cause of apparently lost profiles is a data directory path mismatch. If R2ModMan Plus was updated, reinstalled, or launched on a new system without the original data directory path being specified, it creates a new empty data directory while the original profile data remains untouched at the previous path.
Steps to check and correct the data directory path:
- Launch R2ModMan Plus and navigate to the Settings section from the main screen
- Locate the data directory or storage location setting within the settings panel
- Note the currently configured path and compare it to the known location of your original data directory
- If the paths differ, click the change or browse button next to the data directory setting
- Navigate to the original data directory location and select it
- Confirm the path change and restart R2ModMan Plus
- Check whether the previously missing profiles now appear in the profile list for each game
This single step recovers all profiles in the majority of apparent configuration loss scenarios without requiring any file manipulation or reinstallation.
Importing Profiles From Export Codes
If a profile was previously exported from R2ModMan Plus before the loss occurred, that export code or file contains the complete mod list and version information needed to reconstruct the profile.
How to import a profile from an export code:
- Open R2ModMan Plus and navigate to the profile management screen for the affected game
- Look for the Import or Import from Code option within the profile management interface
- Enter the export code if the profile was exported as a shareable text code
- Alternatively, select the export file if the profile was exported as a downloadable file
- Confirm the import and allow R2ModMan Plus to reconstruct the mod list
- R2ModMan Plus will download and reinstall each mod at the correct version specified in the export
- Verify the reconstructed profile matches the original by reviewing the installed mod list after import completes
Export code imports reconstruct the mod list and versions but do not restore individual mod configuration files stored within the BepInEx config folder. Those must be restored separately from a backup if available.
Common Problems and Solutions:
- Profiles visible in file explorer but not in R2ModMan Plus the data directory path in settings does not match the location where the profile files exist; correct the path as described above
- Import from code fails partway through one or more mods in the export are no longer available on Thunderstore; the import will complete with available mods and list unavailable ones separately
- Profile appears after path correction but shows no installed mods the mods.yml file within the profile folder may be corrupted; attempt a manual restoration of this file from a backup or rebuild the mod list manually
- Data directory change option not visible in settings some R2ModMan Plus versions place this setting under an advanced settings section; look for a Change Data Folder or Storage options subsection
- Restored profile launches game without mods loading mod configuration files in the BepInEx config folder may not have been restored alongside the profile list; check the config folder for missing files
Manual File-Level Profile Recovery
When R2ModMan Plus built-in tools cannot resolve the configuration loss, direct file-level recovery provides an alternative path. This approach requires navigating the data directory structure manually and restoring or reconstructing the files R2ModMan Plus needs to recognize and load a profile.
Restoring Profile Files From Backup or Recycle Bin
If the profile files were deleted recently and the system recycle bin has not been emptied, recovery is straightforward.
Recycle bin recovery steps:
- Open the system recycle bin
- Search for files or folders matching the profile name or the game name associated with the lost profile
- Select all relevant files and folders belonging to the profile
- Right-click and select Restore to return them to their original location in the data directory
- Launch R2ModMan Plus and verify the restored profiles appear in the profile list
For backup-based recovery, the process depends on what backup tool was used and what it captured.
Backup recovery steps:
- Open your backup tool and navigate to the backup snapshot containing the R2ModMan Plus data directory
- Locate the profile folder within the backup at the path matching the data directory structure
- Restore the entire profile folder to its original location in the current data directory
- If restoring to a different system, place the restored folder in the equivalent data directory path for that system
- Launch R2ModMan Plus and confirm the profile appears and loads correctly
Rebuilding a Lost Profile Manually
When no backup exists, and file recovery is not possible, rebuilding the configuration manually is the last resort. This process is time consuming but systematic.
Steps for manual profile reconstruction:
- Create a new profile in R2ModMan Plus for the affected game
- Review any notes, screenshots, or memory of which mods were in the original configuration
- Use the Thunderstore mod browser within R2ModMan Plus to locate and reinstall each mod
- Pay attention to version numbers if specific older versions were used in the original setup
- Reinstall mod configuration settings within each mod’s config file manually based on notes or memory
- Test the reconstructed setup incrementally by adding mods in small groups and testing between additions
Taking screenshots of the installed mod list and exporting a profile code after completing a reconstruction prevents the same loss from occurring again in the future.
Preventing Future Configuration Loss
Recovery is always harder than prevention. Implementing a simple backup routine after restoring a lost configuration is the most important step that follows any recovery effort.
Practical prevention steps:
- Export a profile code from R2ModMan Plus after every significant mod list change and store it in a text file in a cloud-synced location
- Schedule regular copies of the R2ModManager Plus data directory to an external drive or cloud backup service
- After any R2ModMan Plus update, verify the data directory path has not changed before making any profile modifications
- Keep a plain text document listing the mods in each profile with their version numbers as a fallback reference
- Enable operating system file history on the drive containing the R2ModMan Plus data directory so previous versions of profile files are accessible through the system’s built-in version history tool
The time investment in setting up these prevention measures is minimal compared to the time required to rebuild a complex mod configuration from scratch after an unexpected loss event.
Frequently Asked Questions
Where exactly does R2ModManPlus store profile data on Windows?
R2ModMan Plus stores profile data in the data directory specified during initial setup. The default location on Windows is typically within %appdata%\r2modmanPlus-local\. Navigate to this path in File Explorer by typing it directly into the address bar. Each game has its own subfolder within this directory containing individual profile folders.
Can I recover a deleted profile without a backup?
Possibly. If the recycle bin has not been emptied since the deletion, restore the profile folder from there. If the recycle bin has been emptied, file recovery software such as Recuva on Windows may recover the deleted files if the drive has not been heavily written to since the deletion. Recovery success decreases significantly with time and drive activity after the deletion event.
Will reinstalling R2ModManPlus delete my profiles?
No. Reinstalling R2ModMan Plus does not affect the data directory or its contents. Profile data is stored separately from the application installation. After reinstalling, verify the data directory path in settings points to the same location as before the reinstallation to ensure existing profiles are visible.
How do I back up my R2ModManPlus profiles properly?
Copy the entire R2ModMan Plus data directory to an external drive or cloud storage location. On Windows this is typically the r2modmanPlus-local folder within AppData.
Additionally, export a profile code from R2ModMan Plus for each active profile and store those codes in a text file. Profile codes provide a lightweight backup of the mod list and versions without requiring the full data directory to be preserved.
What is a profile export code and how does it help with recovery?
A profile export code is a shareable text string generated by R2ModMan Plus that encodes the complete mod list and version information for a profile. Importing this code into R2ModMan Plus on any system reconstructs the profile by downloading and installing each mod at the specified version.
Export codes do not capture mod configuration file settings, only the list of which mods are installed and at which versions.
Mods show as not installed after fixing data directory path?
The profile list file was restored but the actual mod installation files may not have been included in the recovery. R2ModMan Plus may need to reinstall the mods even though the profile list is intact. Use the install all or update all function within the profile to trigger R2ModMan Plus to download and reinstall the listed mods without requiring manual selection of each one.
Can I transfer my mod profiles to a new computer using R2ModManPlus?
Yes. Export a profile code from each profile on the original system. Install R2ModMan Plus on the new system. Import each profile code through the profile management screen. R2ModMan Plus will download and install all mods at the correct versions on the new system.
Mod configuration files must be transferred manually by copying the BepInEx config folder from the original system’s profile directory to the equivalent location on the new system.
How do I prevent R2ModManPlus from losing my data directory path after updates?
After each R2ModMan Plus update, open the settings panel and verify the data directory path before making any changes to profiles. If the path has changed, correct it immediately. Using a data directory path outside of AppData, such as a dedicated folder on a secondary drive, reduces the likelihood of the path being disrupted by application updates or system changes that affect the default AppData directory.
Latest Post:
