Server under development · A closed beta is running: the game server and the website may restart or go briefly offline without warning, and characters may be wiped before release. Learn more

How to write a bug report: template and statuses

Bug reports

140 · 0 replies
Asyncio
Administrator
#1 15.09.2026 21:10
A good report saves us hours and saves you the wait for a fix. One rule: one thread, one bug.

Before you write
- check "Known bugs": https://azeron.org/forum/known-bugs — it may already be in progress;
- scroll the section to see whether someone opened a thread before you;
- make sure it is actually broken and not just how Legion works.

Template
What is broken (one line):
Where: zone / dungeon / NPC / spell, with the ID if you know it
Class and specialization:
How to reproduce:
1.
2.
3.
What happens:
What should happen (as on retail):
Reproduces: always / sometimes / once
Screenshot or video:
When you ran into it (Moscow time):

The title
Not "bug" and not "help", but to the point:
"[Tomb of Sargeras] Goroth does not hold aggro after phase two"

Statuses
The team sets them; watch the badge on your thread:
- New — we have seen it, not checked it yet;
- Confirmed — we reproduced it ourselves;
- In progress — we are fixing it;
- Fixed — the fix is live, check after a restart;
- Not a bug — that is how it works on retail.

Shipped fixes are collected in "Fixes and patch notes".

What not to do
- "everything lags for me" with no details at all;
- several unrelated bugs in one thread;
- duplicates and bumping every half hour;
- posting exploits in the open — send those to the administration in a Discord DM. Using one quietly earns a ban.
The topic is closed — no new replies are accepted.