Orc Incremental Cryomancer

Quick facts

Entity

New version 1.0 enemy unit

Verified detail

Name only

Mechanics

Not published

Image status

No exact registered image

Do not infer an ability from the name

The fact panel contains the full checked identity evidence. A fantasy archetype may suggest ice, range, control, or another behavior, but those are hypotheses until the current game shows them. Generic key art does not depict or identify this enemy.

Return to the enemy ledger for the release name scope. Use the formation guide only after an actual encounter supplies a failure event worth testing.

Confirm the encounter identity

Capture the complete visible label and build in the same record as the encounter. If no label appears, describe an unknown enemy rather than attaching this name by resemblance.

Field	What to record
Build	Exact version or dated build
Name evidence	Label, tooltip, or official identity source
Encounter	Level, wave, and modifiers
Starting position	Relative battlefield placement
First action	Visible animation and timing order
Target	Clearly selected ally or area
Result	Exact visible change
Repeat	Comparable outcome count

Keep estimated timing separate from official text. Do not publish hidden damage, range, or cooldown values from a short recording.

Test one behavior claim

Start with a neutral description: what moved, what was targeted, and what changed. Repeat without altering the army. Then change one position or defensive choice and observe the same checkpoint.

If a status icon or tooltip appears, transcribe it exactly. A visual color shift without text is an observation, not a named status. If several enemies act together, simplify the encounter when possible before assigning cause.

Bound any counter note

A counter statement needs a named failure, a reversible change, and a repeated result. Include the formation, progression state, and other enemies present. Avoid converting one successful clear into a permanent matchup rule.

If the tested change also raises overall power, say so. The result may show that the wall moved without proving why.

Add facts only when they become visible

Future updates can fill role, action, target, and counter rows. Preserve the old unknown state and attach every addition to a build. Do not copy a mechanic from another game or from community shorthand.

Until then, this page is an identity boundary and an encounter worksheet, not a speculative bestiary entry.

Handle conflicting observations

If two attempts suggest different behavior, compare encounter modifiers, target positions, active upgrades, action order, and build before averaging them. A changed target may be conditional rather than random; a missing effect may have failed an eligibility rule.

Publish the two rows and design a third attempt where the suspected condition differs cleanly. Do not select the more dramatic result or invent a probability from a tiny sample. Unresolved variation belongs in the unknown panel until the test can separate it.

Official source

Verification boundary

Build boundary

version 1.0 announcement

Evidence check

2026-08-28

Still unknown

role, stats, abilities, encounter, counter, exact image identity

Frequently asked questions

What is verified about Cryomancer?

The version 1.0 announcement confirms Cryomancer as a new enemy unit by name. Boundary: version 1.0 announcement. Checked 2026-08-28. The checked source does not publish its role, stats, abilities, encounter, unlock timing, counter, or exact image identity.

Can the Cryomancer name establish an ice mechanic?

No. A thematic name is not mechanics evidence. Record current visible text and controlled encounter observations before describing an ability or recommending a counter.