Blizzard

Quick facts

Spell

Blizzard

Official role

Blizzard slows a boss that is pressuring the frontline.

Build boundary

version 1.0

Evidence check

2026-08-28

Unknown fields

slow percentage, duration, area, cooldown, stacking, cost, unlock, damage, final version 1.0 balance

Test frontline survival, not hidden values

The registry-backed answer establishes one broad tactical use. The next useful step is a matched observation of whether cast timing changes the frontline's survival sequence. No rate or duration is needed to record that outcome.

Start with one boss encounter and one fixed army. Choose a visible pressure cue before the attempt. Record the first allied defeat and final result without a cast change, then repeat with only the cast moment changed.

Use the spell hub framework if the battle symptom has not been diagnosed. Use formation diagnosis if changing one position may address the pressure without changing the cast.

Non-numeric observation checklist

Capture the following fields:

• exact named build;
• boss or reproducible encounter;
• full army and arrangement;
• progression state relevant to the battle;
• visible pressure cue;
• cast moment relative to that cue;
• first allied defeat;
• whether the frontline recovers or collapses;
• final battle result;
• unresolved alternative explanation.

Run the baseline twice when possible. A baseline that changes on its own cannot support a clean timing conclusion.

Observation	Baseline	Changed timing
Pressure cue	Same definition	Same definition
First allied defeat	Record sequence	Record sequence
Frontline state after cue	Describe visibly	Describe visibly
Boss state	Describe visibly	Describe visibly
Result	Record	Record

Keep the wording descriptive. If the game later exposes a current slow value or duration, that can be added with its own source and build label. Do not estimate it from animation frames.

The snowy battlefield is thematic

The hero on this page is a registered promotional screenshot of a snowy battlefield. The source does not prove that a Blizzard cast appears in the frame. Snow, pale effects, or slowed-looking movement are not enough to identify an ability.

This distinction prevents the image from becoming accidental evidence. It supports the battle setting and nothing more. The factual role remains sourced to official store prose.

Attribution mistakes to avoid

One attribution mistake is equating longer survival with a measured slow. Survival can change because of target choice, allied timing, random variation, or another active effect. Report the sequence first.

Another is treating the visual edge of an animation as a verified area. Without official UI or repeatable target observations, the boundary remains unknown.

A third is assuming that multiple casts, copies, or upgrades interact in a familiar way. This source set does not publish stacking, cooldown, cost, unlock, damage, area, duration, or a final upgrade path for Blizzard.

Do not use the snowy hero to fill those gaps. Do not borrow values from Fireball, a Demo memory, or another game.

Decide whether timing helped

Compare the same visible events in the same order. Did the first allied defeat move relative to the pressure cue? Did the frontline remain present through the same boss sequence? Did the final result repeat?

If the answer changes across repeated attempts, keep the conclusion narrow and record the variation. If the cast moment makes no repeatable difference, that is still useful evidence for that setup. It does not prove the spell is weak in every encounter.

Use the build comparison worksheet when a purchase changed between attempts. Use the Fireball timing reference when the fight instead reaches a nearly won state and then reverses.

Preserve the build boundary

A future patch can change combat behavior. Start a new record group after a relevant update and keep the old group under its original build. This makes it possible to compare evidence without presenting one result as permanent.

A publishable sentence names the build, boss, army, cue, repeat count, and visible result. Anything broader remains an open question.

Official source

Verified Blizzard record

Name

Blizzard

Boundary

version 1.0

Verified statement

Blizzard slows a boss that is pressuring the frontline.

Checked

2026-08-28

Still unknown

slow percentage, duration, area, cooldown, stacking, cost, unlock, damage, final version 1.0 balance

Frequently asked questions

What is Blizzard's confirmed role?

Blizzard slows a boss that is pressuring the frontline. The record is bounded to version 1.0 and was checked 2026-08-28.

Does the snowy hero prove that Blizzard was cast?

No. The registered image shows a battle on snowy terrain. It is thematic context only; without source proof, the image cannot identify a cast, its area, or its effect.

What belongs in a Blizzard survival record?

Record the build, boss, frontline arrangement, cast cue, cast moment, first allied defeat, and battle result. Repeat the same case with only timing changed before attributing a survival difference to the spell.