Skip to content
ModsPartially verified

Risk of Rain 2 Mods Not Working

Quick Answer

First confirm the game opens normally, then launch the intended r2modman profile with Start modded. Check matching game paths and dependencies before isolating the failing package in a new minimal profile. Back up profiles and saves before changing them.

On this page

When Risk of Rain 2 mods stop working, separate the launch problem from the package problem. Check whether the base game opens, whether you used the intended modded profile, and whether the specific package loads with its dependencies. Preserve your existing profile and saved runs before changing them. These steps cover PC modding; they are not a console installation procedure.

Start with the symptom you can reproduce

SymptomFirst checkContinue with
Game does not openDoes an ordinary unmodded launch work?Manager game and Steam paths
Game opens with no modsCorrect profile and Start moddedLoader and minimal-profile comparison
One UI feature failsExact package name and author changelogLookingGlass or settings checks below
ProperSave has no Load optionHost, players, mode and save locationSaved-run checks below
Only a large profile failsDoes one feature work in a clean profile?Add package groups back deliberately
Only multiplayer failsHost/client/content installation rulesCompare relevant versions and configs

1. Establish a clean comparison

Write down the game update, storefront, manager version and package versions before changing them. Keep a profile export and a copy of important saves. The r2modman README documents profiles, exports, package updates and configuration editing. It also identifies legitimate downloads: Thunderstore, the author’s GitHub releases and its hosted Flatpak builds. Avoid a similarly named repackaging site.

Try the ordinary game launch, then the intended profile through Start modded. If the same failure occurs without the managed profile, do not keep replacing UI packages to solve it. If only the modded launch fails, move to the manager and loader checks. This comparison narrows where to look; reaching the menu does not validate every feature or a multiplayer run.

2. If the game does not launch or opens without mods

The manager’s troubleshooting page distinguishes the Steam application directory from the game directory. Use Steam’s Browse local files and compare the game folder with r2modman’s Locations setting. The Steam folder contains the Steam executable; it is not the game’s executable folder.

For a Windows Steam setup, review custom launch arguments that may override the manager’s launch. Save their previous value before making a diagnostic change. Do not apply a generic “empty launch options” instruction to a Linux/Proton configuration that depends on its own setup.

For a black screen at launch, the same manager guide documents Settings → Debugging → Run preloader fix, followed by Steam validation. Follow that documented workflow after preserving the profile. If the manager version’s controls differ, use its current help page rather than guessing which file to delete.

3. If the loader works but one package does not

Create a new diagnostic profile with the package you need and its declared dependencies. The Risk of Thunder setup instructions document Download with dependencies and Start modded. Our package source table records the 12 curated manifests checked on October 15.

Observe the feature you installed: an item tooltip, a save checkpoint or a survivor in character selection. If that small profile works, restore other additions in groups until the failure reappears, then narrow the group. Keep shared dependencies installed while testing the package that requires them. This isolation sequence is an editorial diagnostic method; it does not identify a culprit without a reproducible result.

For a manual installation, BepInExPack’s README places the inner pack contents beside the game executable, with winhttp.dll next to RiskOfRain2.exe. Ordinary plugins go in BepInEx/plugins; patchers have a distinct folder. Mixing those manually installed files with a managed profile can leave a second active installation outside the manager’s package list. Preserve those files and follow the relevant author instructions when comparing the setups.

4. If LookingGlass loads but a menu feature is broken

The author changelog provides two specific recent checks. Version 1.16.2 fixes missing item tooltips in the Command window. Version 1.16.3 fixes Potential sorting configuration and stops sorting Hallowed Potentials. Check the installed release before treating those symptoms as a failure of the whole loader.

A missing remote buff timer is a different limitation. The LookingGlass README says the base game does not network those timers and points clients to NetworkedTimedBuffs. Installing the latest tooltip fix does not change that requirement.

An absent settings entry can also be package-specific. Risk Of Options exposes controls that mod authors register; it does not automatically create a menu for every BepInEx configuration. Check whether the package actually supports that menu before reinstalling it.

5. If ProperSave cannot resume the run

Check the host’s lobby, player set, game mode and save location. The ProperSave README says only the host needs the mod, the saved lobby must have the same players, and Classic, Eclipse and Simulacrum have separate files. The checkpoint is created at stage start, not at any arbitrary moment before exiting. Death deletes that run’s save.

Cloud settings can change which file you see. Enabling UseCloudStorage does not preserve existing local saves; disabling it does not clear the cloud. Review CloudStorageSubDirectory before assuming the checkpoint vanished. Preserve files before changing the storage mode.

The release notes say 3.1.1 fixes saving when DLC4 is disabled and 3.1.2 fixes minions being dead after loading. Version 3.1.0 removed support for saves older than 3.0.0. Updating cannot be assumed to recover every old save. See the ProperSave page for the current package and declared requirements.

6. If the failure occurs only in co-op or on Linux

For co-op, compare the exact content packages, versions and relevant settings. A host-only save package, a client UI package and a new networked survivor have different requirements. Export the intended profile rather than recreating a long list from package names alone. A successful solo launch does not establish that the group’s content matches.

For Steam Deck/Linux, use the manager’s Linux instructions. Its documented Proton-detection workaround is an empty .forceproton file in the game install root when the manager mistakenly treats a Proton game as native. Apply it to that specific situation; it is not a fix for a broken plugin or an unmatched lobby. The current manager README recommends Linux builds rather than the Windows installer.

Escalate with a useful reproduction

Keep the shortest profile that still fails. Record the game/storefront, package versions, launch method, exact error and the action that triggers it. Include the relevant loader log if the maintainer requests one. Send manager-launch problems to manager support and a reproducible package feature failure to that package’s author. The links above open original projects; this site does not submit a support request for you.

Reviewed October 15, 2026. The package fixes are author statements; the diagnostic sequence has not been verified by launching the game or restoring a save. Return to the mod directory.