Skip to main content
Overwatch 2 hero art
Beta — closed cohort
Overwatch 2

Nimbus for Overwatch 2 (Beta)

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.

44 hero hooksBattlEye-safe sidecarSendInput pipeline
BattlEye advisory

Read this before you launch.

Overwatch 2 ships with BattlEye + a Blizzard-side ban pipeline that hits both the game account and the Battle.net parent. The beta is closed cohort, requires a Battle.net pre-flight check, and the loader will not launch the game until you acknowledge that:

  • Account bans are a real outcome — all sales are final.
  • BattlEye signature waves can break the build mid-patch.
  • Battle.net parent-account flags propagate to all Blizzard games.
  • You will launch through Battle.net after pre-flight passes.

The in-loader ack is wiped on Sign Out and re-prompted on every fresh device.

Why Nimbus 1

BattlEye-aware launch chain — pre-flight, never silent.

Why Nimbus 2

Humanizer-first defaults — ranked-safe at install.

Why Nimbus 3

Closed-cohort feedback loop — fixes ship to you direct.

What ships in the beta

The Overwatch build mirrors the Marvel feature shape where it transfers; Overwatch-specific work covers BattlEye probing, the Battle.net handshake, per-hero ability tracking, and the out-of-process input pipeline.

Aimbot — SendInput, ranked-tuned

Mouse delta is delivered via the Windows SendInput pipeline, the same path your hardware drivers use. No kernel mouse hooks, no synthetic raw-input replay.

  • Per-hero recoil tables — hitscan tuned (Soldier, Cassidy, Sojourn, Ashe)
  • Humanizer FOV + smoothing curves (Bezier easing, not linear lerp)
  • Target priority — low-HP, line-of-sight, crosshair distance, role weight
  • Hold / toggle / flick modes per hero, persisted per profile

BattlEye-safe sidecar architecture

Nimbus does not inject a DLL into overwatch.exe. The aim logic runs in a separate process, reads game state through validated screen + memory probes, and writes input via the OS layer.

  • Zero in-process hooks on the Overwatch binary
  • Out-of-process state read — no protected handle requests
  • Battle.net pre-flight detects launcher posture before the game spawns
  • Loader stages, customer launches from Battle.net — same posture as Marvel

Transparent overlay — borderless DX-aware

Glow indicators, ability cooldown arcs, and target boxes render in a click-through topmost window. Streamer-mode hides it from OBS/Discord captures via WDA_EXCLUDEFROMCAPTURE.

  • DXGI swap-chain detection — no Present hook on the game
  • Per-hero ability tracker (Ana sleep, Zen discord, Suzu cleanse, Widow grapple)
  • Spectator-aware visibility — auto-dim when killcam is active
  • Capture-safe by default — invisible to OBS, Discord, NVIDIA ShadowPlay

48 hero hooks — every role covered

Each hero in the live roster has an ability-state hook so cooldown UI, projectile prediction, and humanizer profiles know which kit you are on without you toggling.

  • 13 Tank kits — barrier states, charge windows, dive-cancel timing
  • 19 Damage kits — recoil/spread tables + projectile arc per weapon
  • 12 Support kits — heal-target lock, ult-charge readout, Suzu/Immortality timing
  • Auto-rebind on hero swap — no per-hero config dance

Hero coverage

44 kits hooked at launch. New heroes get an ability-tracker patch within the same release window we ship to Marvel — typically inside 72 hours.

Roster tracked weekly
Tank
13
  • D.Va
  • Doomfist
  • Hazard
  • Junker Queen
  • Mauga
  • Orisa
  • Ramattra
  • Reinhardt
  • Roadhog
  • Sigma
  • Winston
  • Wrecking Ball
  • Zarya
Damage
19
  • Ashe
  • Bastion
  • Cassidy
  • Echo
  • Freja
  • Genji
  • Hanzo
  • Junkrat
  • Mei
  • Pharah
  • Reaper
  • Sojourn
  • Soldier: 76
  • Sombra
  • Symmetra
  • Torbjörn
  • Tracer
  • Venture
  • Widowmaker
Support
12
  • Ana
  • Baptiste
  • Brigitte
  • Illari
  • Juno
  • Kiriko
  • Lifeweaver
  • Lúcio
  • Mercy
  • Moira
  • Wuyang
  • Zenyatta

Screenshots

Captures from the closed cohort drop here once members approve them. No staged or AI-generated mockups.

Cohort review pending
Screenshot coming
In-game overlay — Ana sleep tracker
Screenshot coming
Sidecar process tree (Task Manager)
Screenshot coming
Battle.net pre-flight gate

Beta pricing — preview

Checkout opens when beta does

Indicative tiers. Final pricing locks when the beta cohort opens to public sign-ups. All sales final.

Day
$6
24-hour window

Single comp session, no commitment.

Week
$18
7 days

Push a placement set or warm into ranked.

Best cohort fit
Month
$36
30 days

Full season of BattlEye-aware play.

Lifetime
$150
Forever

One key, every Overwatch patch.

  • Pay with Bitcoin
    BTC, 1 confirmation
  • Pay with Litecoin
    LTC, instant
  • 256-bit SSL
    All checkout over TLS 1.3
  • PCI DSS via SellAuth
    Card data never touches our servers
  • HWID-locked keys
    One key, one PC. Reset anytime.
  • No silent auto-renew
    Subscriptions never recharge without consent

FAQ

The questions Discord asks most. If yours is not here, ask in #support — answers usually land within the hour.

Is the cohort really closed?

Yes. Beta access is gated through Discord — verified members get invites first. The /signin and /dashboard routes will not mint an Overwatch key until your account is on the cohort allow-list.

Why a sidecar instead of an in-process overlay?

BattlEye actively scans the Overwatch process address space and module list. A sidecar process with zero injected modules and zero protected-handle requests on overwatch.exe gives BattlEye nothing to flag. The trade-off is no Present hook — we render in a separate transparent window.

How does the aimbot move the mouse?

Through Windows SendInput, the same API your gaming mouse driver uses. We do not patch raw-input, we do not register kernel-level mouse callbacks, and we do not bypass anti-cheat input filters. Input rate is humanizer-shaped per hero.

What happens when BattlEye updates?

You lose a session, not a key. We push a loader update through the same GitHub Releases channel as the Marvel build — your existing license picks it up on next launch. Discord #status posts patch ETAs.

Will it work on a smurf / new account?

Yes, but the founder-side recommendation is the same as Valorant — keep the cohort build on the account you are willing to lose. Battle.net flags propagate to all Blizzard titles.

Can I stream with it on?

Yes. The overlay window is created with WDA_EXCLUDEFROMCAPTURE, so OBS, Discord screenshare, NVIDIA ShadowPlay, and Win+G all see a clean game window. Verify on your own setup before going live.

Do you support console crossplay lobbies?

Detection only — the loader runs on PC. If you queue with crossplay enabled, the overlay still renders against the PC client; behaviour against console teammates and opponents is unchanged.

How do replacement keys work?

If a BattlEye wave or a HWID change locks you out, post in #support with your order ID and HWID. A team member resets or reissues. All sales are final, but session continuity is on us.

Join the cohort in Discord

The closed beta runs out of Discord. Verified members get invites first, see BattlEye status before anyone else, and can ping a maintainer directly when a patch lands.

  • Live #status channel — BattlEye + Battle.net posture
  • #support — replacement keys + HWID resets
  • #patches — release notes pinned per build
  • #cohort-only — the OW2 closed channel after invite

Want in on the closed beta?

Cohort invites go out in Discord — verified members first. Acknowledgement of the BattlEye advisory is required.