- How do I activate Nimbus on Overwatch 2 the first time?
- Sign in to your Nimbus dashboard, download `NimbusLoader-latest.exe`, and run it as administrator. The sign-in dialog appears on every cold launch — enter the email and password you used at checkout. In the launcher, click the **Overwatch** tab. Nimbus runs a Battle.net preflight (verifies the client is installed and logged in), then **Launch** stages the payload, hands off to Battle.net, and the game starts. The in-game menu opens on `Insert` once you are in the main menu of OW2.
- Does my Nimbus key work on both Marvel Rivals and Overwatch 2?
- Yes — Day, Week, Month, and Lifetime tiers all include every supported game on the same key. There are no per-game upgrades or paywalled tabs. The launcher's tab strip exposes whichever titles your tier covers; for the public release, that is Marvel Rivals, Overwatch 2, and the Valorant loader-only launch path.
- Which anti-cheat does Overwatch 2 use, and how does Nimbus stage around it?
- Overwatch 2 ships with **BattlEye** plus Blizzard's own Warden-class integrity scanning bundled into the Battle.net launch. Nimbus runs a BattlEye-aware preflight on the Overwatch tab: it confirms the BattlEye service is in a known-good state, runs the cleaner cascade against stale BE telemetry, and stages the payload before Battle.net spawns the game process. BattlEye stays running the entire match — Nimbus does not disable it.
- How fast do you patch after a Blizzard / Overwatch update?
- Same automated pipeline as Marvel: offset resolver, SDK regen, integration tests, sign, publish. OW2 typically lands a hair slower than Marvel because Blizzard ships engine-level changes more often than NetEase does, and the SDK regen has more surface to revalidate. Realistic expectation: under an hour from patch live to signed build for normal patches; longer for an engine bump. If you launch an outdated loader after a patch, it refuses with "Waiting for compatible build" rather than injecting into a stale state.
- Does the Overwatch tab use a separate HWID lock?
- No — one HWID binding per Nimbus key, shared across every game tab on that key. If you reset HWID for a hardware swap, the new fingerprint applies to Marvel, Overwatch, and any other supported title in a single bind. The 24-hour cooldown between resets is global, not per-game.
- What are the system requirements for Nimbus on Overwatch 2?
- Whatever runs Overwatch 2 runs Nimbus on top of it. Hard requirements:
- **Windows 10 22H2 or Windows 11, x64.** Earlier Windows 10 builds are unsupported.
- **Battle.net desktop client** installed and logged in to the same account that owns OW2.
- **Administrator** elevation on the loader.
Nimbus targets DX11 and DX12 render paths on OW2. Vulkan is not used by retail OW2. Overlay overhead at 1440p / 240Hz is well under the game's frame budget on a 4070-class GPU.
- Do I need the Battle.net desktop client running before I launch?
- It does not need to be running, but it does need to be installed and signed in at least once on this machine. The Nimbus Overwatch tab calls into the Battle.net protocol handler to start the game; if the client is missing or signed out, the preflight surfaces a **Battle.net required** prompt with a link to install/sign in. Once that is cleared, **Launch** works on subsequent cold boots even when the client is closed — Battle.net auto-opens on game-launch protocol.
- Launch sits on "Waiting for Battle.net handshake" and never starts the game.
- Three things, in order:
**1. Battle.net signed out.** Open Battle.net manually, sign in, leave it running, click **Launch** again. The handshake completes immediately if the client is foreground-authenticated.
**2. Battle.net update pending.** If the client itself has an update queued, the protocol handler hangs until it finishes. Let it update and retry.
**3. AV intercepting the staging step.** Add the Nimbus install folder and the Overwatch install folder (`C:\Program Files (x86)\Overwatch\` by default) to your AV's real-time exclusions, then retry.
- The menu opens but inputs (mouse, keyboard) bleed through to the game.
- Almost always a fullscreen-mode issue. Open OW2 **Settings → Video → Display Mode** and switch to **Borderless Windowed**. Exclusive Fullscreen on OW2 occasionally fails to release input capture to the overlay layer; Borderless is the supported configuration. Bound `Insert` to a key that conflicts with an OW2 keybind? Change the Nimbus menu hotkey in **Settings → Hotkeys** — `Insert` is the default but is freely rebindable.
- What does the Overwatch 2 in-game menu include?
- Same menu architecture as Marvel Rivals: **AimBot**, **TriggerBot**, **Visual**, **Overlay**, plus hero-aware logic that respects OW2 roles (tank / damage / support) and per-hero ability sets. ESP with team-aware coloring, BattlEye-safe spectator handling, and config sync across machines. **Skin Changer is NOT shipped on OW2 by design** — Blizzard validates cosmetic state server-side and any client-side swap is trivially flagged. Anyone selling an OW2 skin changer is selling a ban.
- Does Nimbus work in Competitive / Ranked on Overwatch 2?
- Mechanically, yes — the menu and aim logic are mode-agnostic, the game does not distinguish loaded code by playlist. **Editorially**, we tune the defaults around plausibility specifically so they survive competitive scrutiny. Aggressive settings exist; using them in ranked is your call. Stream-safe magnifier mode is on by default — viewer reports during a stream are still the single most common path to a manual review, regardless of game.