AZEROTH FIELDGUIDE

Sources, freshness & corrections

How Azeroth Fieldguide distinguishes evidence, planned features and uncertainty without presenting an announcement as a live test.

Evidence comes first

Core game claims link to a first-party announcement. Directly read pages and search-index-only evidence are labeled separately. A forum post is treated as official only when its attributed author is identified; ordinary forum opinions are not game rules.

Dates mean different things

Source checked is the last evidence review. Content updated is the last substantial edit. We do not change publication dates simply to appear fresh. A build-specific assertion needs a matching build record; this edition contains no such client tests.

Updates are manual. Expired review intervals should prompt a fresh source check, not a claim that content is automatically accurate.

Conflicting or missing information

We retain both relevant statements and explain the conflict. For the launch-hour discrepancy, this means showing the difference and withholding a countdown. Unknown prices, specifications or regional rules remain unknown.

Corrections and reader verification

The update log records meaningful changes; each claim has a source you can inspect. A direct reader-submission channel is not yet available, and no nonfunctional contact form is offered. If a source disagrees with this guide, prefer the latest applicable official statement.

Content boundaries

We do not publish unsupported class rankings, generated gameplay screenshots, fake reviews or copied source articles. AI-assisted summaries are not substitutes for first-hand test evidence. Changes to the source register do not automatically rewrite game guidance.

CONTINUE YOUR JOURNEY
Source registerUpdatesAbout