How to Report a Bug
Quick answer: 4 channels for bug reports: (1) in-game form (/game/feedback.html — fastest path to dev queue), (2) Discord #bug-reports (community triage), (3) GitHub issues (if open), (4) email (last resort). Always include: steps to reproduce, expected vs actual behavior, screenshot, browser + version.
The 4 Steps
Use the in-game form
Go to /game/feedback.html while logged in. The form auto-fills your character ID, race, level, browser, and client version, so you don't have to type any of that out manually. This is the fastest path into the dev queue — every submission is timestamped and tagged with your account data, which means duplicate reports are easy to merge and genuine one-off bugs don't get lost in the noise. Expect a response within 7 days for most reports; game-breaking issues (crashes on core systems like combat, the Auction House, or login) are typically triaged same-day.
Discord #bug-reports
The community Discord's #bug-reports channel is staffed by volunteer moderators who triage incoming reports before anything reaches the dev team. Posting here first is useful when you're not sure if what you saw is actually a bug — other players in the channel can confirm whether they've hit the same issue, which turns a single "this seems off" report into a verified, reproducible bug with multiple witnesses. Moderators forward confirmed issues to the formal dev queue, so Discord and the in-game form work together rather than being competing channels.
Always include reproduction steps
"It crashed" is not a bug report — it gives the dev team nothing to act on. A usable report looks like: "Step 1: equip the Crimson Set. Step 2: enter the PvP Arena. Step 3: cast Blood Drain. Result: client crashes to a blank screen." Include your character's race, class/subclass, and current level too, since some bugs are race- or subclass-specific — a Blood Mage's Blood Ritual interacting badly with a specific armor set won't reproduce on a Werewolf Berserker, for example. If the bug involves combat, note whether you were in PvE, PvP, a dungeon, or a raid boss fight, since each combat context runs slightly different code paths.
Screenshot or video
A short screen recording is worth more than a screenshot, because it captures the exact sequence of clicks and menu states leading up to the bug — timing-sensitive issues (a skill firing during a cooldown window, an Auction House listing that double-charges the tax) are nearly impossible to diagnose from a single still frame. If you can open your browser's developer console (F12) and capture any red error text alongside your screenshot or recording, that speeds up triage significantly, since it often points directly to the failing script rather than leaving the dev team to guess from symptoms alone.
What counts as a good severity flag
Not every bug needs the same urgency. When you file through the in-game form, flag severity honestly: Critical means the client crashes, an account is locked out, or gold/items are being lost or duplicated. Major means a core system misbehaves but the game is still playable — a skill dealing the wrong damage, a dungeon boss not dropping loot, an Auction House listing that won't cancel. Minor covers visual glitches, typos in item descriptions, or UI elements that are misaligned but don't block play. Accurate severity flags help the dev team triage a Critical gold-duplication exploit ahead of a cosmetic typo, which keeps the whole reporting pipeline fast for everyone.
Before you report: check known issues
Balance patches occasionally introduce short-lived side effects that are already known and being tracked — check the patch notes page before filing, since a behavior change might be an intended rebalance rather than a bug. If you're unsure whether something is "working as intended" or broken, that's exactly the kind of question the Discord #bug-reports channel is built to answer quickly, before you spend time writing up a full formal report for something the team already knows about.
Bugs versus exploits: report them differently
Not everything you find is a simple bug — some issues are exploitable for unfair gold, item, or PvP advantage, and those need to be handled more carefully than a cosmetic glitch. If you discover something that lets you duplicate gold or items, bypass the 5% Auction House sale tax, farm PvP ELO without real risk, or otherwise break the game's economy, report it privately through the in-game feedback form rather than posting details publicly in Discord. Publicly describing an active exploit before the dev team can patch it just spreads the exploit faster and can get accounts penalized once it's identified. Genuine visual or minor gameplay bugs, on the other hand, are completely fine to discuss openly in #bug-reports — the distinction is whether the issue gives an unfair economic or competitive advantage if left unpatched.
After you submit: what happens next
Once a report reaches the dev queue, it's typically deduplicated against other submissions describing the same behavior, then triaged by severity. Critical issues affecting the whole player base — a broken Auction House tax calculation, a subclass skill dealing wildly wrong damage — usually get addressed in the next balance patch or a hotfix, while cosmetic and low-impact issues get batched into a later patch cycle. You won't always get a personal reply for minor reports, but confirmed fixes are listed in the patch notes, so it's worth checking there if you want confirmation that something you reported was addressed.