Assassin

Quick facts

Unit and official role

Assassin: stealth unit specializing in critical damage

Registry status

Assassin: UNRANKED · 1.0 CONFIRMED

Build boundary

version 1.0

Evidence check

2026-08-28

What the announcement confirms

The registry-backed summary above preserves the exact official sentence and its evidence boundary. This article starts where that sentence stops: it does not expand a named stealth and critical-damage focus into an ability list.

The announcement does not state how stealth begins or ends. It does not identify what can reveal the unit, whether every attack can become critical, or how target selection works. Those are post-launch questions. They are not missing sentences that a guide writer should complete from genre habits.

Use the confirmed unit roster to compare the four official role descriptions. Use the formation diagnosis guide to design a controlled position test without assuming a board shape or hidden target rule.

Formation questions, not formation claims

Stealth and critical damage suggest useful questions about time, exposure, and access. They do not establish an answer. A careful first test asks whether the Assassin performs the announced role under a repeatable condition.

Record the game build and encounter. Keep the rest of the army unchanged. Move only the Assassin, or replace only one unit, then observe the same encounter again. Note when the unit becomes visible, which opponent it attacks, and whether the interface identifies a critical event. Repeat the comparison before writing a rule.

This method distinguishes three possible causes of a changed result:

1. The position may alter exposure or access.
2. A different enemy arrangement may alter the target reached.
3. Random or timing variation may produce a result that does not repeat.

The best-formations evidence guide explains how to log those conditions. It does not name a universal arrangement.

Post-launch verification checklist

Check the following items against a named released build:

• how the interface signals stealth;
• when that state begins and ends;
• which actions can produce critical damage;
• whether a critical event has a visible label or combat-log entry;
• which targets Assassin selects in repeated identical encounters;
• whether moving the unit changes the observed sequence;
• what unlock or draft conditions the game actually displays.

Capture the smallest reproducible case. A video can show a sequence, but the written note still needs the build, encounter, army, and variable changed. If a later patch affects combat, repeat the case rather than carrying the old conclusion forward.

Overclaim boundary

Do not convert "specializing in critical damage" into a critical chance, multiplier, cooldown, or guaranteed priority. None appears in the cited announcement. Do not call Assassin the strongest attacker or place it above Troll, Warg Raider, or Juggernaut without comparable results.

The evidence-gated tier page explains the registry state and the evidence needed for a competitive placement. Leaving a grid empty is more accurate than filling it before anyone can test the same released build.

Promotional key art on this page shows Orc Incremental branding, not a verified Assassin depiction. The image is not used to infer equipment, animation, scale, or ability behavior. An actual unit image should be added only when an official asset can be matched to Assassin without guesswork.

A useful field note

A useful report says: named build, named encounter, fixed army, Assassin position, repeated attempts, and the visible result. It separates observation from inference. "The unit became hidden after this event" is an observation if the interface supports it. "Stealth always resets after that event" is a rule that needs repeatable evidence.

Keep the record beside the build comparison worksheet. If the result depends on another role or arrangement, state that dependency. If it cannot be reproduced, keep it as an open question rather than a mechanic.

Official source

Confirmed unit record

Unit

Assassin

Official role

stealth unit specializing in critical damage

Evaluation

UNRANKED · 1.0 CONFIRMED

Checked

2026-08-28

Frequently asked questions

What is Assassin's confirmed role and status?

Assassin is a stealth unit specializing in critical damage. Its registry status is UNRANKED · 1.0 CONFIRMED, checked 2026-08-28.

Why does Assassin have that evaluation status?

Pre-release official evidence confirms the unit's role but does not provide comparable version 1.0 performance results. The evaluation is scoped to version 1.0 and carries the recorded status UNRANKED · 1.0 CONFIRMED.

What should be checked after release?

Record how stealth and critical damage appear in a named build, then compare controlled battles with only one placement or army change. Do not infer hidden rules from a single result.