Windows
Best for most users. The setup executable installs the manager; the manager then handles game profiles and mods.
Download setupr2modman-Setup-3.2.19.exe165,156,122 bytes · SHA-512 in the verification table
Platform-specific guidance for Windows, Linux, Steam Deck, and Flatpak, with the exact files and next steps.
Use the release page for individual files or the Thunderstore package for managed distribution. Both routes lead to the same project assets.
Best for most users. The setup executable installs the manager; the manager then handles game profiles and mods.
Download setupr2modman-Setup-3.2.19.exeChoose the portable AppImage or a package for your distribution. Do not run the Windows `.exe`.
AppImage:chmod +x may be required.Use Flatpak for Game Mode, or AppImage in Desktop Mode. Proton games may need an extra path check.
Download Flatpak App ID:io.github.ebkr.r2modmanEach path includes a verification step so you can tell whether the problem is the manager, the game path, or a mod.
chmod +x r2modman-3.2.19.AppImage.--no-sandbox..forceproton file if the manager misdetects the platform.The release metadata includes SHA-512 values for the published files. The values below are the Base64 representation from that metadata.
| Asset | Platform | Size | SHA-512 Base64 |
|---|---|---|---|
r2modman-Setup-3.2.19.exe | Windows | 165,156,122 bytes | ryBCak935X0THtS01TMCEHhI617R/JN39mJuSKrykyuZQXyrHoecjgZE2kV30vXqqrCisxWl4KJuuXuiYqaP+Q== |
r2modman-3.2.19.AppImage | Linux | 200,488,834 bytes | 6aMz/QZaZva3a2KGfCp+1XcxMFV7A+rKRAqYeILqYkmaG9WAmjyq5n3i6scSYmfUnNYdaTWXWYTGWdkpW2vPyQ== |
r2modman_3.2.19_amd64.deb | Linux | 154,752,116 bytes | fu9CbDFV9Pncd7G8iEmWqdf1+fYoJkkSfH85FDgJP3Ot4Tkl6t9EDrWanErpm/7S5E7WtqNi5l7/7FtgC7diOQ== |
r2modman is MIT-licensed, but each third-party mod has its own author, code, permissions, license, and compatibility risk. Keep backups, avoid unknown DLLs, and check your game’s anti-cheat and terms before modding.
Version history is useful when a game or modpack pins a release. Older builds should be tied to a specific compatibility need.
Start here unless the game community identifies a compatibility constraint. Re-check release metadata each time you update.
Open latest releaseThe release archive keeps the version history. Older installers can stop working after game updates, so use them only when a game community documents a compatibility need.
Browse release historyExport a profile code and .r2z file before changing versions. Test in a separate profile and keep the known-good setup.
117 releases are indexed from the project repository. Each button opens the original asset; update metadata and blockmaps are omitted from the quick-download list.