VERSION LEDGER / PUBLIC DEMO
A practical demo reading order
Check the build boundary before reading a feature claim. The October demo is the current public build, the full game is planned for 10 November 2026, and the named heroes added to the demo describe the current playable picture rather than a complete launch roster. This check prevents most accidental overstatement.
Next, separate reach from product state. The June and July player milestones show meaningful public reach, but they do not establish sales, retention, or final launch performance. The same distinction applies to a showcase: a video can show a character or setting without establishing every rule behind it.
For a bug report, record the version, platform, location, action, expected result, observed result, and a repeatable sequence. A report that says when the issue appears is more useful than one that only assigns a feeling to an effect or weapon. Add a short clip when the problem is visual and preserve the exact wording of any on-screen message. Note whether the issue appears while moving through crowd pressure, after a status effect, or when a weapon relationship changes.
For a content question, start with the dated update and then open the matching topic. Champions gives the character context, Weapons gives the named arsenal record, Status Effects gives the consequence, and Progression gives the loop position. The demo date tells you which version boundary applies.
A player returning after several weeks can use the same sequence without relearning the whole game. Confirm the newest demo label, decide whether the question concerns a hero, weapon, foe, effect, or reward, then read its universe, role, faction, or run context.
Keep a personal note tied to the build label when testing. Record the champion, weapon, effect, battlefield, and exact action involved, then compare the note with the next build update. That gives feedback a durable reference point and keeps a demo observation separate from a claim about the final game. Burning can speed enemies, Poisoned can slow them, Oiled increases fire damage, and Berserk raises attack frequency through Frenzon, so name the effect when it matters. A Burning observation from the October demo is a version-tied result, not a promise about the November launch balance.
The public demo is also a good place to learn the game's deliberate control rhythm. Movement is the active choice while attacks auto-aim, so a test note can describe both the build decision and the path taken through pressure. That makes a report about Burning, Poisoned, a weapon, or a foe more precise without requiring final balance numbers. An October note should also separate a Warhammer 40,000 demo hero such as Legend of Catachan from an Age of Sigmar demo hero such as Lyssa Revenya; neither name establishes the final launch roster.