Report a bug — what to include

Bug reports are how we find and fix problems we didn't catch in QA. A well-structured report often gets a same-day patch; a vague one ("it doesn't work") sits in the queue while we ask follow-up questions. Use this checklist to file a clean one.

Step 1: confirm it's a bug, not a known issue. Quick check on the status page — if there's an active incident, your symptom is probably part of that and we already know. Check Discord #patch-status for any "Re-resolving" message; if Marvel Rivals just patched, give us 15-30 minutes before reporting overlay glitches.

Step 2: gather your environment. Three lines, ideally pasted into the ticket as a code block.

```
Loader version: w834 (read from the loader's top-right corner)
Windows: 11 23H2 (run winver from the Start menu)
Game: Marvel Rivals on Steam (or Epic, whichever you launch via)
```

Step 3: write the repro steps. A repro is a numbered list of exactly what you did to trigger the bug, written so we can copy them on our test rig. Example:

```
1. Launch the loader, sign in.
2. Click Launch Game on the Steam tier.
3. Wait until I'm in Practice Range as Hawkeye.
4. Press Insert. Menu appears as expected.
5. Open the Hero tab. Toggle Auto-Lock on.
6. Toggle Auto-Lock off.
→ Menu freezes for 3 seconds, then crashes the game.
```

The ➜ arrow marks the moment the bug happens. Steps before are setup; steps after the arrow are the failure description.

Step 4: grab the loader log. Open %APPDATA%\Nimbus\logs\ in File Explorer (paste the path into the address bar). The most recent file is named nimbus-loader-<YYYYMMDD-HHMMSS>.log. Open it in Notepad and redact any line containing `KEY=` — that's your license key in plaintext, and you don't want it sitting in a public ticket.

Step 5: grab a screenshot or short video. A screenshot beats a verbal description for visual bugs (overlay positioning, ESP text mangling, menu artifacts). A 10-30 second screen recording is gold for behavioral bugs (aim assist overshoot, hotkey not firing). Use Windows' built-in Snipping Tool (Win+Shift+S) for stills and Xbox Game Bar (Win+G → Record) for short clips. Upload to Imgur, Streamable, or attach directly to the ticket.

Step 6: open the ticket. Dashboard → Support, New ticket, category Bug. Subject like Bug — <one-line summary>. Paste your environment block, the repro, and link the log + screenshot/video. If the bug is intermittent ("happens about 1 in 5 launches"), say that — it tells us to look for race conditions.

Step 7: track the response. SLA is 24h on bug tickets during business hours; severe bugs (game crash, ban risk, payload not loading at all) jump the queue and get same-hour replies. We post the fix's build version in the ticket reply ("fixed in w835, push live by EOD"), and once the build hits LATEST, the loader auto-updates you on next launch.

What slows this down.

• "It crashed" with no log. We can't tell which subsystem crashed without the log.
• A screenshot of the loader window but no description. We need to know what you expected versus what happened.
• Reporting on Discord DM instead of a ticket. Discord is fine for chat-mode questions, but bug tracking lives on the ticket system so we can search/triage/link to commits.
• Filing as "Install" instead of "Bug" — wrong queue, slower routing.

Thanks for the report regardless — every clean bug ticket sharpens the product for the next thousand customers.