Orc Incremental Chieftains

Quick facts

Battlefield role

Units in version 1.0

Signature input

Right click

Bloodline scope

Nine distinct bloodlines are planned.

Detail status

Names, effects, stats, and builds are unpublished.

Use the announcement as a boundary

The summary above is the complete factual starting point available from the checked announcement. It establishes a release direction, not a roster database or strategy guide. The absence of published names, numbers, effects, and timing is part of the answer, because filling those gaps would make later verification harder.

The wide key art is generic promotional material. It does not identify either pictured character as a Chieftain and does not show an ability input, passive result, or build. Treat it as atmosphere only.

For the confirmed count and a template for later discoveries, use the bloodlines reference. For the separately announced passive boundary, use the Martyrdom guide. The unit codex covers the four release-confirmed army units without implying that their roles transfer here.

Build a current roster record

When the release build exposes this system, begin with transcription. A useful entry should be possible for another reader to reproduce without relying on a screenshot crop or a remembered tooltip.

Field	What to capture
Build	Exact version or dated build label
Visible name	Complete text, including punctuation
Unlock context	Screen, milestone, or prompt where it appeared
Displayed text	Full ability and passive wording
Input cue	What the interface visibly asks the player to do
Battlefield state	Allies, enemies, wave, and formation before the test
Result	First observable change after the input

If the interface omits a field, write “not shown.” Do not infer a missing stat from animation speed, art size, or a single damage number.

Separate transcription from testing

A tooltip is evidence for its visible wording. A battle is evidence for what happened in one setup. Keep those records separate before trying to connect them.

First capture the text and build. Then choose one observable question: whether an input becomes available, whether a visible state changes, or whether a result repeats at the same checkpoint. Hold the formation and encounter steady where possible. Record unsuccessful attempts as carefully as successful ones; they often reveal an eligibility condition without proving why it exists.

One trial cannot establish a cooldown, targeting priority, scaling rule, or optimal use. Those claims require repeated measurements with a stated comparison.

Avoid premature builds and rankings

A build recommendation needs named options, visible effects, an objective, and comparable results. None of those can be supplied by the broad announcement alone. A tier label or “best” choice published now would be fiction dressed as guidance.

Once current evidence exists, start with a narrow question such as “which observed choice addressed this named wall under this formation?” Preserve the losing comparison and any uncontrolled difference. The formation guide provides a way to document position tests without turning one result into a universal ranking.

Review after every relevant update

Store old observations under their original build. On a new build, check names, displayed text, availability, input cues, and observed results again. Do not silently overwrite a prior record; a changed label may be a content edit, while a changed outcome may come from the army or encounter.

The useful page today is an honest perimeter around the announced system. The useful page later will be a build-labeled record that grows only when the game or an official source supplies the missing details.

Official source

Verification boundary

Build boundary

version 1.0 announcement

Evidence check

2026-08-28

Still unknown

Chieftain names, bloodline names and effects, signature ability effects, stats and unlock timing, rankings and builds

Frequently asked questions

What is verified about Chieftains?

The version 1.0 announcement says Chieftains become battlefield units with signature abilities activated by right click. Boundary: version 1.0 announcement. Checked 2026-08-28. Names, stats, ability effects, unlock timing, sacrifice timing, rankings, and builds are not published in the checked source.

How should an unknown Chieftain detail be recorded?

Capture the exact current interface text, build label, where it appeared, and what remains hidden. Keep an observed label separate from any interpretation until a repeatable battlefield test is available.

Can a promotional image establish a Chieftain build?

No. Generic key art supplies visual context only. A build needs current in-game text and controlled observations for the named version.