Version watch
Azeroth Survivors updates and version notes
This page records what the guide checks and when. It does not turn a changed page, a community commit, or a Discord message into an official patch note without a clear source.
Current snapshot
The guide was checked against the published sources on October 31, 2026.
The creator page was checked for its browser entry, WebGPU warning, and alternate download language. The community repository was checked for its README, controls, local-build boundary, and documented mechanics.
- Creator source: wow.aethus.pl
- Community source: OutThisLife/azeroth-survivors-re
- Guide scope: where to play, controls, classes, builds, troubleshooting, and evidence status
- Next check: after a visible creator page change, new release, or confirmed gameplay update
Editorial rule
A source change is not automatically a game update.
We separate creator announcements, repository changes, player reports, and our own run notes. Each type answers a different question and should be labeled accordingly.
- Creator announcement: direct statement from the creator's published channel.
- Repository change: a code or documentation change in the separate community project.
- Player report: useful lead that still needs confirmation.
- Run note: an observation from a named version and test route.
Update types
Label the change before you describe it
A creator announcement, a repository commit, a host outage and a player observation do not carry the same weight. A useful update log keeps those signals separate.
Creator
Published announcement
Use this label for a direct statement or visible change on the creator's published page.
Community
Repository change
Describe changes to the separate local project without presenting them as an official browser patch.
Availability
Entry-point status
Record a WebGPU warning, busy host or changed download route as an access observation.
Run note
Tested behavior
Include the source, date, class, zone and result when a player observation supports a gameplay note.
Change-log format
Write entries that can be checked later
A short update is enough when it answers what changed, where it was seen and what players should do next.
- Start with the date and the type of source.
- Link to the page, commit or announcement that supports the statement.
- Separate confirmed behavior from a player report or open question.
- Explain which guide pages may need a recheck.
- Remove the note or mark it stale when the source is no longer available.
FAQ
Quick answers
Does this page list official patch notes?
Only when an official creator source publishes them clearly. Otherwise this page records verification notes and labels community or player information separately.
How often should the guide be checked?
Recheck after a creator page change, a confirmed release or gameplay announcement, or a change in the community reference that affects a guide claim.
Does a repository commit count as an official patch note?
No. It is a change in the separate community project. It can be useful evidence for that project, but it should stay labeled separately from a creator announcement.
What should I send when I spot an outdated guide detail?
Send the affected URL, the exact claim, the source or run that contradicts it, and the date or build you checked. That gives the guide something concrete to verify.