Orc Incremental Bloodlines

Quick facts

Confirmed count

Nine distinct bloodlines

Name status

Not published

Effect status

Not published

Evidence boundary

Version 1.0 announcement

Keep the empty catalog honest

The registry records the announced scope and nothing more. The checked release source does not supply a usable catalog, so there are no names, effect summaries, unlock requirements, or recommendations to list yet. An empty evidence-backed catalog is more useful than a complete-looking table assembled from guesses.

The vertical key art is generic. It does not depict a labeled bloodline, prove a character identity, or disclose an effect. Its presence should not be read as a roster clue.

Use the Chieftains overview for the surrounding battlefield boundary and the Martyrdom guide for the separately named passive. Neither page supplies the missing catalog.

Add a row only from visible evidence

When names and descriptions become available, every row needs a source and build label. Use the exact current spelling rather than normalizing it from memory.

Field	Required evidence
Name	Complete visible label
Build	Exact version or dated build
Description	Full visible text
Availability	Where and when the option appears
Relationship	Any visibly stated prerequisite or exclusion
Observation	One controlled, repeatable result
Unknowns	Missing numbers, rules, or interactions

Do not give an icon a fan-made name. Do not turn a position in a selection screen into an unlock order. A locked slot establishes only that the slot was locked in that captured state.

Test effects without ranking them

After an exact description exists, choose one claim small enough to observe. Record the same encounter, army, formation, progression state, and objective before comparing two available options. If multiple systems change, the result is a case study rather than a clean comparison.

An effect can be useful for one bottleneck and irrelevant to another. “Changed this observable result at this checkpoint” is evidence. “Always strongest” requires much broader coverage and remains patch-sensitive even after testing.

Keep qualitative interface language distinct from measured behavior. A tooltip adjective does not disclose a hidden multiplier, and a visible animation does not prove the full affected area.

Track interactions as separate claims

Interactions multiply the ways a small test can mislead. Record the base observation first, then add one companion system at a time. Note the selected army, formation, upgrades, current cycle, and any active passive. If a result changes, repeat before attributing the difference.

Create separate rows for description, observed outcome, and interpretation. That structure makes it possible to correct an inference without erasing what the interface actually showed.

Preserve unknowns after release

Release does not automatically make every hidden rule public. If an option appears without exact numerical text, preserve the visible wording and mark the rest unknown. If a description changes, keep the earlier version labeled rather than merging them.

The upgrade-priority guide can organize a later decision around a diagnosed wall, but it cannot provide a priority list before the options and their current effects are verified. The wiki hub links to other published references without treating planned pages as evidence.

Reject false completeness

Common warning signs include an uncited list, confident effect prose without a build, a ranking without an objective, or a recommendation copied from a different version. A trustworthy catalog should look incomplete while the source is incomplete.

For now, the correct result is a confirmed scope, an explicit unknown list, and a procedure for adding current observations without pretending the missing names or mechanics are known.

Official source

Verification boundary

Build boundary

version 1.0 announcement

Evidence check

2026-08-28

Still unknown

bloodline names, individual effects, unlock order, interactions, rankings and builds

Frequently asked questions

What is verified about Bloodlines?

The version 1.0 announcement confirms nine distinct Chieftain bloodlines. Boundary: version 1.0 announcement. Checked 2026-08-28. Their names, individual effects, stats, unlock order, interactions, rankings, and recommended builds are not published in the checked source.

How should future bloodline details be added?

Transcribe the exact visible name and text with a build label, then record unlock context and a narrow observation separately. Do not turn a reveal order into a strength order.

Can an empty slot or icon reveal a bloodline effect?

No. Layout can guide a later inspection, but an unlabeled icon does not establish a name, effect, rarity, or recommended use.