Nimbusfor Overwatch 2
Built for Battle.net's BattlEye — read-only sidecar overlay, no anti-cheat triggers.
Hero-aware aim, ability cooldown ESP, and an inject pattern tuned for OW2's BattlEye user-mode AC — gameplay support designed around how Blizzard's anti-cheat actually fingerprints.
- Hero-aware aim — different math for hitscan vs projectile heroes
- Cooldown + range ESP — call rotations, don't guess them
- BattlEye-aware deployment via FSR DLL path — looks like a Blizzard module
All sales final. License keys are HWID-bound. Reset from your dashboard on rig upgrades.
- Patch turnaround: minutes, not hoursLast rebuild —. Resolver v2 re-signs on every Marvel Rivals patch.
- HWID-bound, non-transferableAll sales are final. HWID resets handled via the in-dashboard self-service flow.
See it in-game
The Nimbus overlay binds to your insert key once the OW2 main menu loads.
BattlEye sidecar — how it stays quiet
User-mode ACOverwatch 2 ships with BattlEye, a user-mode anti-cheat that fingerprints loaded modules and scans process memory. Nimbus is engineered as a read-only sidecar overlay — it does not write to OW2's memory and does not install hooks BattlEye scans for.
- Read-only by design: the overlay reads game state for ESP + aim math and renders to its own surface. No writes to game memory, no injected functions, no AC triggers.
- How we deploy: Nimbus rides into OW2 via the AMD FSR DLL path (
amd_fidelityfx_dx12.dll). It's a render module Blizzard ships and the game itself loads — to BattlEye it looks like a legitimate Blizzard module. - What you need to enable: AMD FSR in OW2 Graphics settings (Render Scale → FSR, or Dynamic Render Scale → AMD FSR). Without FSR the inject path doesn't exist.
- Streamer-safe surface: the menu draws to a non-display-cloned compositor target. Capture pipelines see your clean game, not the overlay — unless you choose otherwise.
BattlEye bans for OW2 are issued in waves, not instantly. We rebuild within minutes of every patch to stay ahead of signature drift. Use a dedicated Battle.net account if your main matters to you — Blizzard account bans propagate across the platform.
Your launch flow doesn't change
Battle.net launches Overwatch 2 the same way it always has. Nimbus stages itself before the game loads — the only step you add is hitting Launch in the loader first.
Battle.net itself is never modified. No registry edits, no service installs, no replacement of Battle.net.exe.
Pick your tier
Every tier ships the full feature set — start at $8/day, scale to longer durations.
Will I get banned?
Honest answer: no overlay is zero-risk on a live anti-cheat title. What you can verify is how we behave around detection events.
Every confirmed detection is published to the public status page within one hour — including root cause and fix ETA — even when it’s bad for sales. Median patch turnaround across the last six months is minutes from a Marvel Rivals patch going live to a signed Nimbus build available.
The two failure modes we see most: running Nimbus alongside a second cheat, or using an EAC-disable tool. Don’t do either.
Full breakdown: FAQ › detection events.
- Pay with BitcoinBTC, 1 confirmation
- Pay with LitecoinLTC, instant
- 256-bit SSLAll checkout over TLS 1.3
- PCI DSS via SellAuthCard data never touches our servers
- HWID-locked keysOne key, one PC. Reset anytime.
- No silent auto-renewSubscriptions never recharge without consent
Also on Nimbus
Same loader. Same Discord. Different game, different math.