Warhammer Survivors updates

UPDATES / OFFICIAL CHANGE LEDGER

What the current updates establish

The October demo adds Legend of Catachan and Lyssa Revenya to the named playable picture. Marneus Calgar and Fo’Baran connect to the Ork reveal, while the roster and foe groups show where those characters fit. Legend of Catachan is a Warhammer 40,000 demo hero, Lyssa Revenya is an Age of Sigmar demo hero, and Marneus Calgar is an Ultramarines leader.

The planned platform list covers Steam, GOG, PlayStation 5, Xbox Series X|S, Switch, Switch 2, iOS, and Android, with the full launch planned for 10 November 2026. A demo download may not be available on every listed platform yet, so check the matching storefront before installing. On PC, the listed minimum is Windows 10 64-bit, a dual-core 2.4 GHz x86-64 processor, 4 GB RAM, a GTX 750-class graphics card, and 5 GB storage.

The June demo reached 130,000 players and the July demo passed 190,000. Those figures measure public reach, not sales, retention, conversion, or final launch performance. They explain why a returning player may want to check the October boundary, but they do not answer a purchase or profitability question.

UPDATES / OFFICIAL CHANGE LEDGER

Follow an update into the reference

When an update names a champion, enemy, weapon, effect, or platform, follow that name into its related guide. Use the October demo entry for Legend of Catachan and Lyssa Revenya, the Ork reveal for Marneus Calgar and Fo’Baran, and the platform entry for the current requirements and storefront targets. For a run question, follow Oiled to Burning or Frenzon to Berserk; for an install question, read all five PC requirements together.

Treat a patch as current only when the public build has changed; a community comment alone cannot establish that. Keep older build milestones in mind when a familiar roster or platform note looks different. An older entry is still useful when you compare what changed between the June, July, and October builds.

Returning players can start with the newest date, open the changed record, and then compare its universe, role, faction, or run relationship with the surrounding entries.

UPDATES / OFFICIAL CHANGE LEDGER

A practical update reading order

Read any update in three passes. First identify the date and the public build boundary. Next identify the changed noun: demo hero, enemy family, platform, or planned launch date. Then open the related record to see its universe, role, faction, or run connection.

The October demo is a clear example. Legend of Catachan is a Warhammer 40,000 demo hero and Lyssa Revenya is an Age of Sigmar demo hero. The same check works for an Ork reveal, a weapon relationship, or a platform requirement. A platform note should be read with its target family and build status, while a champion note should be read with its universe and role. The 6 October entry changes the current demo boundary; the 10 November entry marks a planned full launch, so they answer different player questions.

June's 130,000-player milestone and July's figure above 190,000 describe public reach at two moments. They show why an update matters to returning players, but they do not establish sales, retention, payment, or the result of the future launch. Use them to place the October demo in the project's public history, not to estimate how the finished game will perform.

For a quick return visit, start with the newest boundary, open the affected record, compare its relationships, and then return to the dated history. Older entries help explain why a familiar roster, enemy family, or public milestone may look different from the current build. The same loop works for a player checking an effect interaction, a minimum PC requirement, or a planned console target.

A date tells you when the public build moved, a title tells you what changed, and the related record tells you how that change fits the run. This order keeps a returning player from treating a repeated description as a new feature. It also separates a new champion name from a platform target, a reach milestone from a sales claim, and a planned date from an available build.

If a new demo changes the public boundary, compare it with the June or July build you remember. The newest entry tells you what is current; an older entry explains why a roster, milestone, or platform note may look different. Open the changed champion, enemy, weapon, or platform entry before drawing a conclusion about the whole game. The October change is specifically a demo boundary with two named heroes, not a final balance or launch receipt.