Troubleshooting
Game already running
Why the loader refuses to arm when Marvel Rivals is already open, and the right order.
Why we refuse
Attaching mid-session races the anti-cheat initialization. The anti-cheat seals the game's module list shortly after the game starts; mapping a new DLL after that point puts a brand-new module entry in a sealed list, which is exactly the pattern external scanners look for.
We refuse, deliberately, to keep your account healthy.
The right order
- Close Marvel Rivals if it's open. The launcher counts — close
MarvelRivals_Launcher.exeas well. - Click Launch Nimbus.
- Wait for "Waiting for Marvel Rivals…".
- Now start the game from Steam or the Epic Games Store — whichever copy you own. The loader auto-detects both.
Force-attach (experts)
Launch Nimbus.bat --force-attach
This bypasses the pre-flight check. We do not support tickets that come from runs with this flag set. The flag exists for our own debugging.