Skip to content
Warhammer Survivors Tier list
Powered by Pagefind
English
Page type: Source-led reference Checked: 10/8/2026 Certainty: Use the cited source and build label
All Evolutions

Warhammer Survivors Evolutions: Official Links and Leads

Compare two announced weapon evolutions and review labelled Demo research leads without treating unverified pairs as complete recipes.

10/8/2026 Last updated: 10/8/2026 5 min read

FAQ

What evolution relationships are officially announced?
Auroch announces Power Fists evolving into Gauntlets of Ultramar, with Calgar as a companion, and Orbital Bombardment as an evolution of Whirlwind Battery. The requirements and trigger are not confirmed here.
Are the Steam Demo ingredient pairs verified recipes?
No. They are historical community research leads from Steam discussions, marked candidate with zero independent checks. Names and claims conflict, so they must not be used as current recipes.
Does this page include a complete evolution finder?
No complete verified recipe list is available yet. Release-build records still need ingredients, requirements, trigger, build, source, and a repeatable observation.

Which evolutions are officially announced?

The strongest pre-release evidence is two relationships in the Auroch announcement. Power Fists evolve into Gauntlets of Ultramar and bring Calgar as a companion. Orbital Bombardment is described as an evolution of Whirlwind Battery. These are announcements about named relationships, not a complete recipe table or a release-build balance assessment.

The announcement does not establish the item requirements, levels, trigger, chest behavior, unlock cost, or whether the relationships changed between Demo builds and the full game. Keep those fields blank until an official source or a repeatable observation fills them. The characters guide records Calgar and the other officially named figures without turning a companion mention into a character ranking.

Original diagram showing the two officially announced evolution relationships and their unconfirmed recipe fields.

Original informational diagram, not gameplay footage: it distinguishes a named relationship from an unconfirmed recipe.

What does a complete evolution record need?

A useful evolution page should answer more than “item A plus item B.” Before publishing a release recipe, record:

  1. The exact base weapon and required passive or item names as they appear in the game build.
  2. Any level, upgrade, chest, timing, or other trigger that makes the evolution happen.
  3. The platform, game build, stage or mode, and observation date.
  4. The resulting name, whether a companion or side effect appeared, and whether another run repeated it.
  5. A source URL or a repeatable observation with enough detail for a reader to check the entry.

Original diagram listing the ingredients, trigger, result, build, and source fields needed for a complete evolution record.

Original informational diagram, not gameplay footage: it is a checklist for recording a claim, not a statement of current requirements.

The editorial standards explain why these fields matter. They also prevent a historical Demo comment from being silently promoted into a launch answer. The Demo guide keeps old and new builds separate, which is essential when a discussion post uses an alternate item name.

Historical research leads: candidate pairs only

The table below is intentionally separated from the official announcements. These are community claims from the Steam Demo Weapon Evolutions discussion and the evolution questions discussion. Both sources were accessed on 2026-10-08. Every row is a historical Demo lead that has not been independently checked; none is a verified recipe.

Historical context Claimed ingredient pair Source/date and caveat Status
Age of Sigmar Demo Nuin Oil + Hourglass Steam Community discussion, accessed 2026-10-08; source uses Nuin while the official store uses Nuln. Candidate only; 0 independent checks
Age of Sigmar Demo Tempest Axes + Sabaton Steam Community discussion, accessed 2026-10-08; output is not established. Candidate only; 0 independent checks
Age of Sigmar Demo Boltstorm Pistol + Lightning Bolt Steam Community discussion, accessed 2026-10-08; output is not established. Candidate only; 0 independent checks
Age of Sigmar Demo Nebulous SeaFog + Glue Steam Community discussion, accessed 2026-10-08; output is not established. Candidate only; 0 independent checks
Warhammer 40,000 Demo Chainsword + Tape Measure Steam Community discussion, accessed 2026-10-08; naming is not reconciled to the official Astartes Chainsword. Candidate only; 0 independent checks
Warhammer 40,000 Demo Bolt Pistol + Dice Cube Steam Community discussion, accessed 2026-10-08; comments use alternate weapon names. Candidate only; 0 independent checks
Warhammer 40,000 Demo Whirlwind Battery + Tape Measure Steam Community discussion, accessed 2026-10-08; a comment says the pairing may have changed. Candidate only; 0 independent checks
Historical ambiguous lead Boltgun + Dice Steam Community questions discussion, accessed 2026-10-08; no output or build was captured. Candidate only; 0 independent checks
Historical ambiguous lead Missile + Tape Measure Steam Community questions discussion, accessed 2026-10-08; no output or build was captured. Candidate only; 0 independent checks
Historical ambiguous lead Axe + Running Shoes Steam Community questions discussion, accessed 2026-10-08; no output or build was captured. Candidate only; 0 independent checks
Historical ambiguous lead Crossbow + Lightning Bolt Steam Community questions discussion, accessed 2026-10-08; no output or build was captured. Candidate only; 0 independent checks
Historical ambiguous lead Blue sphere + Glue Steam Community questions discussion, accessed 2026-10-08; no output or build was captured. Candidate only; 0 independent checks

Original diagram separating historical Demo claims from the release-build checks still required.

Original informational diagram, not gameplay footage: it keeps community leads in their historical build context.

How will the chart change after release?

Add a confirmed label only when the source, build, trigger, and repeatable observation are recorded. Add a correction date when the relationship is confirmed. Until then, keeping official relationships separate from unverified candidates is more useful than a crowded list: official names remain visible, candidate pairs remain searchable, and no player is told that an untested combination is guaranteed.

The release-date guide gives the announced launch timeline, while the wiki hub points to the other pages with cited sources. None of these pages claims a complete recipe list, unlock tracker, or hands-on ranking before the data exists.

Source trail

Keep the cited source, build label, and observation date with every factual change. Report a changed claim through the correction route.

Report a correction

Related Articles

Was this helpful?