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

  1. Close Marvel Rivals if it's open. The launcher counts — close MarvelRivals_Launcher.exe as well.
  2. Click Launch Nimbus.
  3. Wait for "Waiting for Marvel Rivals…".
  4. 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.