Rules for the pages
Editorial policy
What we will not do
We do not invent lore, drop rates, player counts, or file hashes. We do not require a staff member to log into a game before a page can exist. Public pages, videos, and repository files are the record. We do not host game archives, addon zips, or edited saves.
Tier letters are quoted from the site that printed them. We do not collapse three lists into one “best class.” Community build routes are marked as community routes and tied to the patch note we last read.
Corrections and freshness
Email [email protected] with the URL and the better source. Azeroth Survivors pages are reviewed against the patch log; the date at the top of each page is the review, not a promise that the build number is still current tomorrow. Warcraft III pages move more slowly.
Affiliate links are not used. Google Analytics 4, Microsoft Clarity and Adsterra advertising start by default on first view. Reject stops analytics, ads and replay and sets analytics consent to denied, so a stored Reject sends no request to any of the three. The privacy page records this behaviour and is updated when a vendor or placement changes.
What I checked
The rule I keep tripping toward is a tidy single number. The zone page is where I stopped: 12, 9, and 16 stay in separate sentences. That choice is the policy, not a style preference.
Guide diagrams
FAQ
How do I report an error?
Email [email protected] with the page URL and a public source.
Do you use AI to invent stats?
No. Stats are copied from a named source or left blank.
Related
Sources
- Sources — The method, expanded
How we verify · Updated 2026-10-28