- How do I activate Nimbus on Marvel Rivals the first time?
- Sign in at `getnimbus.net/dashboard`, download `NimbusLoader-latest.exe`, and run it as administrator. The sign-in dialog appears every cold launch — enter the email and password you used at checkout. Once signed in, the launcher opens on the **Marvel** tab. Click **Launch**, the loader stages the payload into your Marvel install, and Steam (or Epic) starts the game. The in-game menu opens on `Insert`.
- My key shows "Invalid license key" — what now?
- The loader returns that string for three different states, only one of which is a real key problem.
**1. Typo / wrong key.** Paste from the Resend delivery email, not Discord — the Resend email has copy-button HTML. Check no leading space.
**2. Expired Day/Week pass.** Day passes are 24h from first launch, not 24h from purchase. The dashboard shows the actual expiry.
**3. Revoked key.** Rare. Happens if a chargeback was filed against the order. Open `#support` in Discord with the order ID and we audit the chain.
The one state this string does NOT mean is "HWID mismatch" — that returns a separate `HWID mismatch` error with a Reset HWID link.
- Why does every launch ask me to sign in even when "Remember me" is on?
- This is intentional, not a bug. Founder policy: every cold launch of `OurLoader.exe` shows the sign-in dialog. There is no silent auto-sign-in. With "Remember me on this device" enabled, both email and password are saved (machine-bound AES-GCM) and pre-filled into the dialog — so all you do is click **Sign in** once. This keeps the loader anti-piracy posture intact (no menu screenshot-able from a stolen session) while keeping the friction at one click.
- Which anti-cheat does Marvel Rivals run, and how does Nimbus handle it?
- Marvel Rivals ships with **NEProtect (NEP)** — NetEase's in-house anti-cheat, plus a kernel driver loaded at game launch via a per-session randomized `NEP<8char>` service name. The Nimbus loader stages a cleaner cascade that wipes NEP's session telemetry, registry keys, and crash-report cache, then drops the payload into Marvel's `libogg_64.dll` slot so the game maps it during the normal launch flow. Once Marvel is up, the in-game menu hooks D3D Present and renders inside the game window. NEProtect runs the whole time — Nimbus does not disable it.
- How quickly do you patch after a Marvel Rivals update?
- Median **14 minutes** from a Marvel Rivals patch going live to a signed Nimbus build available, 90th-percentile under 45 minutes. The pipeline is fully automated: offset resolver picks up the new game build hash within a minute, SDK regenerates against the updated symbols, payload rebuilds, integration test pack runs, and the build signs and publishes. The only manual gate is final changelog review. If you launch an outdated loader against a newer game build, it refuses with "Waiting for compatible build" — you cannot accidentally inject into a stale state.
- I upgraded my CPU / motherboard — Nimbus says HWID mismatch.
- Expected. The HWID is a salted hash of CPU + motherboard + the disk Windows lives on. Change any of those and the fingerprint changes. Self-serve fix: sign in at the dashboard, open your key, click **Reset HWID**. Next launch fingerprints the new rig and invalidates the old binding. A 24-hour cooldown sits between resets — long enough to deter shared-key abuse, short enough for legitimate upgrades. RMA or mid-cooldown emergency, open `#support` with the order ID and we waive it.
- Does swapping my GPU or adding RAM need an HWID reset?
- No. GPU, RAM, secondary disks, monitors, and peripherals do not enter the fingerprint hash. Only CPU, motherboard, and the disk Windows lives on do. A fresh Windows install on the same hardware also stays bound — same fingerprint, just a silent re-auth on next launch.
- What are the system requirements for Nimbus on Marvel Rivals?
- Whatever runs Marvel Rivals runs Nimbus on top of it. Hard requirements:
- **Windows 10 22H2 or Windows 11, x64.** Windows 10 21H2 and earlier are not supported.
- **Steam or Epic** install of Marvel Rivals. Both storefronts auto-detect; Nimbus walks the registered library folders.
- **Administrator** elevation on the loader (UAC prompt at launch).
Overlay overhead is well under 1ms per frame at 1440p on a 4060-class GPU. The loader itself fits in about 20MB of working set. Linux + Proton is not supported and will not be — kernel anti-cheat assumes Windows-native syscalls.
- Steam or Epic — does it matter which I bought Marvel Rivals on?
- No functional difference. Nimbus auto-detects both storefronts by walking the registered library folders. If you own Marvel on Steam and Epic both, the launcher picks whichever it finds first; you can override the install path in **Settings → Game Path** if you want to pin it to one.
- I clicked Launch and the game closed before the menu opened.
- Almost always one of three things:
**1. Anti-virus quarantined the payload mid-stage.** Add the Nimbus install folder and the Marvel Rivals install folder to your AV's real-time-scan exclusions. Defender, Bitdefender, Kaspersky, and Malwarebytes all need the same folder-level exclusion. Then **Launch** again.
**2. Outdated loader against a new game build.** The loader normally auto-updates at boot, but if it failed (network hiccup, AV interception), it shows **Waiting for compatible build**. Close the loader fully and re-open — the bootstrap re-runs.
**3. NEProtect leftover from a previous session.** Reboot once. NEP installs a per-session service that occasionally hangs on; a reboot clears it. Nimbus' cleaner handles this in 95%+ of cases, but a stuck NEP service is the edge case.
- The menu never appears in-game — `Insert` does nothing.
- Three things to check, in order:
**1. Are you actually injected?** Check the loader window — if it shows **Injected, waiting for game** then the payload is staged. If it shows **Idle**, click **Launch** first.
**2. Fullscreen mode.** Borderless and Windowed both work. **Exclusive fullscreen** can block the overlay on some driver versions — switch to Borderless in Marvel's Display settings as a first test.
**3. Conflicting overlay.** Discord overlay, Steam overlay, RivaTuner, MSI Afterburner, and Game Bar can all collide with D3D Present hooks. Disable them one at a time. Discord overlay is the most common offender.
- What does the Marvel Rivals in-game menu actually include?
- Fourteen tabs, 1:1 parity with the canonical OREO payload: **AimBot, TriggerBot, FlickBot, Exploits, Presets, Auto Ability, Hero Logic, Combos, Visual, Overlay, Skin Changer, Miscellaneous, Configs, Settings**. Per-hero logic for the full roster, projectile prediction with quartic gravity intercept for arc weapons (Hawkeye, etc.), per-bone hitbox extender, ESP with team-aware coloring, dual aimbot, and config sync across machines tied to your Nimbus account. Stream-safe magnifier capture is on by default.