- What do I actually get when I activate Nimbus on the Valorant tab?
- Loader-managed launch path only. The Valorant tab in `OurLoader.exe` runs a Vanguard preflight, stages a clean environment (cleaner cascade, spoofer, fingerprint state), and then hands off to Riot's launcher to start Valorant through official channels. **There is no in-game Nimbus menu in Valorant.** No overlay, no aimbot tab, no ESP. If you bought Nimbus expecting an in-game menu on Valorant, open `#support` in Discord and we will walk it through — but the loader-only scope is intentional and announced on the product page.
- Do I activate Valorant with the same Nimbus key as Marvel?
- Yes. One Nimbus key covers every supported title on your tier — Marvel Rivals, Overwatch 2, and the Valorant loader-only launch path are all on the same key. No per-game upgrades. The HWID binding is shared across tabs.
- Why is there no in-game Nimbus menu for Valorant?
- **Vanguard** is a ring-0 (kernel-mode) anti-cheat that loads at Windows boot and runs continuous integrity checks against process memory, drivers, and signed-binary state. The engineering cost of a survivable in-game overlay against Vanguard is, today, economically unrealistic for the price tier we sell at — and any shortcut we could take would ship customers a ban risk we are not willing to attach to the Nimbus brand. We support Valorant at the **loader layer** instead: clean staging, spoofer, environment prep, and a handoff to Riot's launcher. If we ever ship an in-game module for Valorant, it will be announced explicitly. Until then: loader-only.
- Does running the Nimbus loader for Valorant trip Vanguard?
- The loader does not inject code into the Valorant process and does not touch the Vanguard driver. The staging it does run is pre-launch — cleaner cascade, spoofer, environment prep — and finishes before Riot Client / Valorant spawn. That said: Vanguard is opaque and Riot updates it on its own schedule, and **no Vanguard-adjacent tool is risk-free**. We do not publish "safe" claims for the Valorant tab; we publish what the loader does, full stop. If a Vanguard signature ever flags a Nimbus loader artifact, we post it to the status page within an hour and ship a fix as a normal build.
- Does the Valorant tab share the same HWID lock as Marvel and Overwatch?
- Yes — one HWID binding per Nimbus key, shared across every tab. Reset HWID once after a hardware swap and the new fingerprint applies to all supported titles. The 24-hour reset cooldown is global, not per-tab.
- What are the system requirements for the Nimbus Valorant tab?
- Identical to the rest of Nimbus:
- **Windows 10 22H2 or Windows 11, x64.**
- **Riot Client** installed (it ships alongside Valorant; nothing extra to install).
- **Administrator** elevation on `OurLoader.exe`.
- **Vanguard service** present and in a known-good state (the loader's preflight verifies this).
Nimbus' loader-side overhead at idle is negligible — under 20MB working set, no driver, no service.
- Do I need to reboot before launching Valorant through Nimbus?
- Sometimes. Vanguard installs itself as a boot-start driver, which means certain Vanguard state changes — first install, an update, a service restart — only fully apply after a reboot. If the Nimbus preflight reports `Vanguard reboot required`, reboot once and re-launch. Vanguard prompts the same way when launched directly through Riot. This is a Vanguard behavior, not a Nimbus one.
- The Valorant tab shows "Vanguard preflight failed" — what does that mean?
- The Nimbus loader checks four things before it lets you click **Launch** on the Valorant tab: (1) Vanguard service is installed, (2) the service is in a Running state, (3) the Vanguard driver is loaded, (4) Riot Client is installed at a known path. If any one of those is false, the preflight fails with the specific check name appended. Most common causes:
**1. Vanguard uninstalled** — reinstall by launching Valorant directly through Riot Client once, accept the Vanguard prompt, reboot.
**2. Vanguard service stopped** — `services.msc` → find **vgc** → set Startup Type to **Automatic**, Start the service.
**3. Riot Client moved or not installed** — install Riot Client from `playvalorant.com`.
- Riot Client opens but Valorant never actually launches.
- This is a Riot Client state issue, not a Nimbus one — but the fix is the same regardless of how you launched.
**1. Sign in to Riot Client manually**, then quit Valorant fully (system tray), then click **Launch** in Nimbus again.
**2. Riot Client update pending** — let the client update fully and retry.
**3. Region mismatch** — if you recently swapped Riot regions, the client sometimes hangs on first relaunch. Open Riot Client manually once, confirm the region, then retry through Nimbus.
- What does the Valorant tab actually do for me, then?
- The loader-only Valorant tab gives you a one-click clean-launch workflow:
- **Cleaner cascade** wipes session telemetry and crash-report directories that survive between launches.
- **Spoofer** sets a fresh environment fingerprint pre-launch (HWID-adjacent values: Machine GUID, HwProfile, etc.).
- **Vanguard preflight** catches the four most common Vanguard failure modes before you commit to a launch.
- **Riot Client handoff** so the game starts through Riot's official path, not a sideloaded process.
What it does NOT do: no in-game overlay, no aim assistance, no ESP, no skin swap, no settings menu inside Valorant. Loader-only means loader-only.
- Will Nimbus ever ship a full in-game menu for Valorant?
- Tracked, not promised. The decision is purely about whether we can build an overlay against Vanguard that meets the survivability bar we hold the rest of the product to, at the price tier we sell at. That bar moves with Vanguard's driver-level posture; we re-evaluate it every quarter. When and if we ship one, it will be announced explicitly with a build version pinned to the announcement — never as a quiet flip. Until then, do not buy Nimbus for an in-game Valorant menu; it does not exist.