Forum · Bug Reports

Sticky How to Report a Bug Correctly — Read Before Posting

5 · 0 replies

KNEUMA avatar
Original Post

Good bug reports get fixed fast — vague ones get ignored. Before posting here, please include:

One bug per thread. Don't pile several issues into one post; it makes tracking and fixing them much harder.

Clear title. Describe the actual problem, e.g. "Quest 'All Hell Breaks Loose' — trigger NPC doesn't spawn", not "broken quest pls fix".

What's wrong + what should happen. Explain the behaviour you got, and how it works on retail MoP 5.4.8.

Steps to reproduce. List them so staff can trigger it themselves — zone and coords, NPC/quest name, the spell or item, and your class/spec if relevant.

IDs help a lot. Quest ID, NPC entry, item ID, spell ID, achievement ID make a bug findable instantly. A WoW database site (Wowhead) is great for looking up the correct values.

Evidence. A screenshot or short clip. For crashes or server errors, paste the relevant log lines in a code block (three backticks — see the Markdown guide).

Search first. Check Bug Reports for an existing thread before making a new one — add to it instead of duplicating.

Stay civil. Calm, detailed reports get prioritised. Demands and rage do not.

Handy template to copy into your post:

Bug:
Expected (retail 5.4.8):
Steps to reproduce:
IDs (quest / npc / item / spell):
Zone & coords:
Screenshot / log:

Thanks for helping make the realm better — every solid report counts. — Staff

Please log in to reply.