Separate manager, loader, dependency, and mod updates so every change has evidence and a rollback path.
The r2modman application, the game, the loader, shared dependency packages, and feature mods are independent layers. “Update r2modman” should not silently become “update everything.” Record the current versions and change one layer at a time so a regression has a bounded cause.
Export the stable profile as a code and .r2z, copy irreplaceable configuration and saves, and keep the exact old installer when compatibility matters. Clone Stable to Lab and perform the update there first. A cache may speed up downloads, but it is not a backup.
Update the manager and confirm it opens. In Lab, update the required loader and launch. Then update shared dependencies in a small batch, launch again, and finally update feature mods. This sequence reveals whether the break occurred in the application, runtime, API layer, or mod behavior.
If a regression appears, undo the most recent package or return to Stable. Do not simultaneously reinstall the game, clear every cache, change Proton, and delete profiles; that removes the evidence needed to find the cause.
After a major game release, community loaders and mods may need time to catch up. If the current profile remains playable and no security or compatibility fix requires immediate action, waiting for documented compatibility can be safer than updating a multiplayer setup on day one.
A normal app update should preserve them, but an export is still the correct precaution before any important change.
Yes. Small batches are strongly preferable when stability and diagnosis matter.
The download center indexes all public releases and links their original assets.
Research note: September 13, 2026 snapshot. Release assets and platform behavior can change; verify important details again before installation.
Recommended path: read this guide → download or create a minimal profile → record the result → expand to the full modpack.