Orc Incremental Bosses

Quick facts

New legendary scope

Three bosses

Official description

Unique attacks

Names

Not published

Promotional art

Separate context, not an identity match

Separate pictured bosses from unnamed scope

The registry states the release-announcement boundary. The animated Demon is official promotional media with its own visible subject, but it does not identify any of the unnamed release bosses. The same rule applies to other labeled Grub or Serpent art.

Use the legendary boss reference for the announced unknown set and the enemy ledger for non-boss units. Do not merge these categories by visual size.

Require an exact identity match

A boss record needs a current visible name or a direct official asset label. Resemblance and file placement are supporting context only.

Field	Evidence to capture
Name	Exact current label
Build	Version or dated build
Encounter	Entry path, level, and modifiers
Telegraph	Visible cue before an action
Action	Complete observable sequence
Target	Selected ally, area, or formation section
Outcome	Visible damage, status, summon, or movement
Reward	Exact completion display

Do not estimate hidden stats or drop chances from a short sequence.

Learn an encounter in passes

First observe without changing the setup. Record action order and the earliest repeatable failure. On the next attempt, test one position or purchase against that event. Keep the same checkpoint and build.

If the result changes, state exactly what changed. A successful clear can validate one response for one setup; it does not establish the fastest or only strategy.

Treat attacks as separate claims

One boss may show several animations, and one animation may contain several visible effects. Give each candidate action a local observation name until the game supplies an exact label. Record telegraph, timing order, target, and result separately.

Avoid attributing a battlefield change to the boss when another enemy, passive, or progression modifier acts in the same window. Repeat with a simpler state where possible.

Preserve promotional history

Official art is valuable when labeled honestly. Keep the subject, source type, and build state with the image. Do not relabel an old promotional subject to fill gaps in a newer announcement.

After patches, start a new encounter row and compare visible names, actions, rewards, and availability. The result is a useful boss ledger precisely because identity and behavior are never guessed.

Build a reviewable attempt log

Number attempts within one build and link each conclusion to its baseline. Record when a test ends early, when a different action order appears, and when a reward screen is not reached. Failed rows prevent a successful outlier from becoming the whole guide.

For video evidence, keep the capture date and full encounter context. A cropped highlight may illustrate a telegraph, but it cannot establish the starting army, modifiers, or full sequence. Use it as supporting evidence beside the complete record.

Official source

Verification boundary

Build boundary

version 1.0 announcement and explicitly labeled promotional art

Evidence check

2026-08-28

Still unknown

new boss names, new attacks, stats, encounters, rewards, image identities

Frequently asked questions

What is verified about Bosses?

The version 1.0 announcement confirms three new legendary bosses with unique attacks; separately registered promotional art shows other labeled boss imagery. Boundary: version 1.0 announcement and explicitly labeled promotional art. Checked 2026-08-28. The announcement does not publish the three new names or attacks, and the promotional Demon, Grub, or Serpent imagery cannot identify those unnamed bosses.

How should promotional boss art be used?

Label the pictured subject and source boundary exactly. Do not use resemblance, color, or placement to identify one of the unnamed release-announcement bosses.