Orc Incremental Legendary Bosses

Quick facts

Confirmed count

Three new legendary bosses

Confirmed description

Unique attacks

Name status

Not published

Hero boundary

Promotional Grub art is not one of the unnamed-boss identities.

Do not name the unknown set from art

The fact panel contains the entire release-announcement scope. The Grub hero is a separately labeled promotional battle image. It provides boss atmosphere but is not asserted to be a member of the unnamed set. No missing identity is filled from the Serpent or Demon assets either.

Use the wider boss ledger for identity rules and the enemy ledger for the separately announced enemy units.

Add an identity only from direct evidence

Create a current row when the game displays a boss name or an official source explicitly ties a name to an asset. Preserve the exact build and source.

Field	Required record
Name	Complete visible label
Build	Exact version or date
Identity source	Interface or directly labeled official asset
Encounter	Entry path, level, and active modifiers
Action label	Exact text, if shown
Telegraph	Observable cue
Target and result	Visible sequence
Reward	Complete completion text

If the game does not name an action, use a neutral local label and do not present it as official.

Observe each action independently

Record the initial setup, action order, and earliest failure. Repeat under the same formation before changing one variable. Several actions in one fight should have separate rows so an effect is not assigned to the wrong animation.

A unique-looking sequence does not reveal its hidden numbers, cooldown, target rule, or best response. State only what the current screen and repeatable attempts support.

Keep strategy local

A response note should name the build, boss identity evidence, encounter, formation, failed event, tested change, and observed outcome. It should also say what varied unintentionally.

Avoid rankings before all identities and comparable encounter evidence exist. Even then, boss order, army progression, and patch changes may make a universal ranking misleading.

Review after official reveals

When names or attack details are published, attach them to the exact source and retain this earlier unknown record. Check whether promotional art receives an explicit identity; do not infer the match retroactively.

The current page is deliberately a shell with strong admission rules. That makes future additions traceable instead of turning promotional imagery into a confident but false boss list.

Avoid ranking unknown encounters

Difficulty comparisons need verified identities, comparable progression states, and a shared objective. Release order, promotional prominence, sprite size, or a single failed attempt cannot provide that foundation.

When enough current encounters exist, compare one clearly defined outcome such as attempts to first clear under stated constraints. Preserve army and patch differences beside the numbers. Until then, leave difficulty and priority unranked; an unknown field is a better planning signal than a fabricated ordering.

Official source

Verification boundary

Build boundary

version 1.0 announcement

Evidence check

2026-08-28

Still unknown

names, attacks, stats, encounters, rewards, counters

Frequently asked questions

What is verified about Legendary Bosses?

The version 1.0 announcement confirms three new legendary bosses described as having unique attacks. Boundary: version 1.0 announcement. Checked 2026-08-28. Their names, attacks, stats, encounters, rewards, counters, and images are not published; the Grub hero is promotional context and not an identity claim.

How should a newly encountered legendary boss be added?

Capture its exact current name, build, encounter, visible attack text, telegraph, target, and observed result. Keep the record separate from promotional boss imagery until an exact identity match exists.