Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] - Risk of Rain 2 does not start with mods due to BepInEx launch method (Linux). #927

Open
elekius opened this issue Dec 24, 2022 · 2 comments
Labels
bug Minor issue

Comments

@elekius
Copy link

elekius commented Dec 24, 2022

Describe the bug
Game fails to start with mods, instead instantly closes.

To Reproduce
Steps to reproduce the behavior:

  1. Create a profile for Risk of Rain 2.
  2. Install BepInEx.
  3. Launch Game modded.

Expected behavior
Game starts with all installed and enabled Mods.

Additional context
This bug occurs because r2modman tries to inject BepInEx via the method used for unix-native games, which in the case of Risk of Rain 2, is not applicable. r2modman thinks the game is native even though it's using Proton.
r2modman's checks for proton by reading the game's manifest file and looking for the line platform_override_source and checking, if it has the value windows. If it does, it uses Proton, if not then it assumes it is a native application.
Risk of Rain 2's manifest file, does not contain this line, which leads to r2modman defaulting to the injection method used for unix-native games, which fails.
This issue has been reported by other users as well. I was able to reproduce this issue on three different machines and two different virtual machines. However, not all users encounter this issue.

@elekius elekius added the bug Minor issue label Dec 24, 2022
@jj-code-00
Copy link

Current work around I have found is don't add the launch arguments to ror2 and use https://thunderstore.io/package/Foldex/r2mod_cli/ and run it once letting it install bepinexpack, R2API, and HookGenPatcher. Then just use r2modman normally and everything should work. Might need to check updates every once in a while with r2cli too.

@ardittristan
Copy link

Above issue describes the location of the manual compatibility tool settings. Potentially being able to be used as a secondary proton check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Minor issue
Projects
None yet
Development

No branches or pull requests

3 participants