How to report bugs and contribute to the server

Why the way you report matters

The development team receives dozens of reports per week. The difference between a bug fixed quickly and one ignored for months is, almost always, the quality of the report.

A vague report — "the boss doesn't work" — cannot be reproduced. A detailed report — with class, zone, exact steps and expected behavior vs. observed — can be reproduced in minutes.

Efficient bug report step by step

1. Confirm it's a bug Check if it is WoW retail 3.3.5a behavior or a server customization. Sometimes what appears to be a bug is misinterpreted original mechanics.

2. Try reproducing Run the sequence again. If it happens again, you have a reproducible bug — much easier to fix.

3. Collect essential information:

• Class and spec
• Zone/dungeon/raid and specific boss (if applicable)
• Exact steps to reproduce
• What happened (observed behavior)
• What should happen (expected behavior)
• Frequency: always happens or intermittent?

4. Add evidence Screenshot or short video eliminates ambiguity. If possible, include it.

5. Send via the correct channel Use the server ticket system or bug report channel on Discord — not the general chat.

Essential information for reproduction

The minimum that every report needs to have:

• Where: zone, NPC, boss, skill
• When: specific conditions (group, solo, certain boss phase)
• What: clear description of incorrect behavior
• Expected: what should happen instead

Without these four points, the report will hardly move forward.

Reporting errors that delay correction

• Report in general chat instead of the correct channel
• Do not include steps to reproduce ("it happened once, I don't know how")
• Mix multiple bugs into a single report
• Use vague language ("it's broken", "it doesn't work")
• Not responding when the team asks for additional information

How to track issue status

After reporting, use the ticket number (if the system generates one) to follow up. On Discord channels, some servers maintain a public thread for known bugs — check to see if yours is already listed before creating a duplicate.

Continuous contribution best practices

• Research before reporting — the bug may already be in the known list
• One report per ticket — do not group different issues together
• Be objective and neutral — reports with an aggressive tone are less prioritized
• Return to the report if additional information is requested — ignoring the follow-up blocks the correction
• Confirm when the fix arrives — closing the loop helps the team validate the fix