Troll

Quick facts

Unit and official role

Troll: durable tank that reflects damage

Registry status

Troll: UNRANKED · 1.0 CONFIRMED

Build boundary

version 1.0

Evidence check

2026-08-28

Verified record

The registry-backed summary above owns the exact official role and status wording. The source does not define how durable behavior is measured, supply a reflection percentage, name a trigger, state a target rule, or give a placement instruction, so this article keeps those items as questions.

The distinction matters because "tank" can tempt a guide to import assumptions from another game. This registry does not do that. It records only the Orc Incremental wording and leaves each unreported behavior open for a labeled test.

The four-unit roster places that role beside Assassin, Warg Raider, and Juggernaut without ranking them. The formation guide provides a neutral way to observe exposure and survival once version 1.0 can be tested.

Keep two observations apart

A long survival time and reflected damage are different observations. If Troll stays active longer after several things change, that result does not identify the cause. Likewise, an opponent losing health while Troll is present does not prove which event triggered reflection.

Build a small comparison. Keep the encounter, army, purchases, and arrangement fixed. Observe the baseline several times. Then change one relevant condition, such as Troll's position, and repeat. Record the first incoming hit, the visible response, the opponent affected, and whether the same sequence recurs.

If the interface provides a combat log, icon, or labeled value, capture it. If it does not, describe only what is visible. Do not back-calculate a reflection formula from a short or rounded health bar.

What to capture in version 1.0

Use this post-launch checklist only with a named released build.

For a named released build, verify:

• what visual or text cue identifies reflected damage;
• which incoming events can produce that response;
• whether the source or another target receives the response;
• whether position changes which events reach Troll;
• how consistently the unit survives the same encounter;
• what draft or unlock condition appears in the interface;
• whether a relevant patch changes any repeated result.

Use the build worksheet to keep the comparison conditions together. The note should distinguish the official role, the observed sequence, and the explanation you are testing.

Claims this source cannot support

The main overclaim risk is turning a broad tank role into exact behavior.

No cited source provides Troll's exact health, defense, reflection value, attack behavior, or acquisition rule. This page therefore does not claim a numerical advantage and does not describe reflection as guaranteed against every attack type.

The tier evidence page keeps identity evidence separate from comparison evidence. Longer survival in one encounter would not establish a universal result or a performance placement.

The hero is official Orc Incremental key art, not a Troll portrait. It must not be used as evidence for the unit's appearance, equipment, size, or animation. That boundary prevents unrelated legacy or promotional characters from being relabeled as a confirmed version 1.0 Troll.

Read a failing front line

If a formation fails, record what happened before choosing more durability. Did Troll fall before other roles acted? Did the army survive but fail to reach the blocking target? Did changing position alter the first incoming event? These observations point to different tests.

The best-formations method recommends one-variable comparisons and repeated attempts. Apply that method before saying Troll belongs in a particular place. A narrow claim tied to one build and encounter is useful; a universal tank rule without conditions is not.

Field-note format

Write the build label, encounter, full army, Troll position, repeated outcomes, and visible reflection cue. State whether the behavior was consistent and what alternative explanation remains. If an observation is ambiguous, keep it as a question for the next run.

This format makes corrections possible. Another player can repeat the setup, and a later editor can see whether a patch changed the behavior. A vague note that Troll "felt tougher" cannot support a mechanic or ranking.

Official source

Confirmed unit record

Unit

Troll

Official role

durable tank that reflects damage

Evaluation

UNRANKED · 1.0 CONFIRMED

Checked

2026-08-28

Frequently asked questions

What is Troll's confirmed role and status?

Troll is a durable tank that reflects damage. Its registry status is UNRANKED · 1.0 CONFIRMED, checked 2026-08-28.

Why does Troll 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?

Observe what counts as reflected damage and how the unit survives in a named build. Keep the enemy, formation, and other purchases fixed while changing one condition.