Avatars, the latest QA release is upon us! Please use this forum for bug reporting of this QA release ONLY. Do follow the format below, because it will help us out greatly in responding. If you do not, it's possible your bug report will be misinterpreted, or worse, lost!

Read BEFORE submitting your first bug: Reporting Bugs… QA 101 Document

• Search for your bug before posting in order to avoid duplicate reports.
• Only reply to an existing thread if you have additional information for the reported bug. ALL extraneous commentary will be deleted to avoid cluttering the reports.
• Keep your bug report short and factual.
• There is no need to submit crash logs. Crash data we require is automatically logged.

Bug Report Template

1. Title:
2. Reproduction Rate:
3. Blocker?
4. Details:
5. Steps to Reproduce:
6. User Specs:

To get started, use /bug in-game (/devbug if on QA) to auto-create this template. It will even auto-fill some of the required information and open the browser for you. Then take the information that was just saved to your system's clipboard and paste it into a new QA forum post. Thank you bug hunters!

We have a QA initiative where we work with the community more closely than ever to get your bug reports into the hands of the developers. Please use this forum for LIVE Server bug reporting. Do follow the format below, because it will help us out greatly in responding. If you do not, it's possible your bug report will be misinterpreted, or worse, lost!

Read BEFORE submitting your first bug: Reporting Bugs… QA 101 Document

• Disable all Lua Add-Ons by using '/lua unload' in local chat or temporarily move all files/folders out of the SotA Lua folder then restart the game.
  Ensure the issue still occurs before submitting a bug; Support staff will not debug Add-On issues
• Search for your bug before posting in order to avoid duplicate reports.
• Only reply to an existing thread if you have additional information for the reported bug. ALL extraneous commentary will be deleted to avoid cluttering the reports.
• Keep your bug report short and factual.
• There is no need to submit crash logs. Crash data we require is automatically logged.

Bug Report Template

1. Title:
2. Reproduction Rate:
3. Blocker?
4. Details:
5. Steps to Reproduce:
6. User Specs:

To get started, use /bug in-game (/devbug if on QA) to auto-create this template. It will even auto-fill some of the required information and open the browser for you. Then take the information that was just saved to your system's clipboard and paste it into a new QA forum post. Thank you bug hunters!