Orc Incremental Paladin

Quick facts

Entity

New version 1.0 enemy unit

Verified detail

Name only

Mechanics

Not published

Image status

No exact registered image

Reject genre shorthand

The release source supplies an identity, not a role sheet. Armor, healing, shields, support behavior, and targeting are all unverified until current interface text or repeatable observations establish them. The vertical key art is generic and does not identify the enemy.

Use the enemy ledger to see the full confirmed name scope and the bosses overview for the distinct legendary boundary.

Create a labeled encounter record

Do not attach this page to an unlabeled sprite. Capture the exact name and build before describing behavior.

Field	Evidence to preserve
Build	Exact current version or date
Identity	Complete visible name and source
Encounter	Level, wave, and active modifiers
Position	Starting battlefield place
Action order	First and subsequent visible actions
Target	Selected ally, enemy, or area
State change	Visible health, status, or movement
Repeat	Comparable attempts

If the interface does not expose a number, leave it unknown. Estimating from pixels or memory is not a substitute.

Distinguish survival from mitigation

An enemy lasting longer can have many causes: incoming target order, formation, another unit, encounter modifiers, or a hidden value. Record the attack sequence and all nearby enemies before naming defense or support behavior.

Use one formation move as a test and replay the same checkpoint. If the result changes, report the observed sequence. Do not claim an armor value or healing effect unless the current game visibly identifies it.

Write a narrow response test

Choose the first repeatable failure and one controllable change. Define what success would look like before the attempt. Preserve results that do not improve the wall, because they prevent cycling through the same guess later.

A clear report states the build, setup, change, outcome, and uncontrolled variables. It does not say the response is universal or best.

Keep the page versioned

When official text or current observations supply a role, ability, or encounter, add the exact source and build. Keep earlier rows rather than rewriting them. If official media later identifies the unit, link that asset directly; generic art remains generic.

For now, the correct page is deliberately incomplete. It gives the reader a way to verify the first encounter without turning a familiar name into invented mechanics.

Check interactions separately

If a visible state changes while several enemies are present, record every concurrent action. Repeat with a simpler encounter or different target order before assigning the change to this entity. Keep status text, animation, and numerical outcome as separate observations.

An interaction may depend on an ally, modifier, or progression system. Add those fields to the record instead of summarizing the result as a standalone ability. That makes a later correction possible without discarding the original encounter evidence.

Official source

Verification boundary

Build boundary

version 1.0 announcement

Evidence check

2026-08-28

Still unknown

role, stats, abilities, encounter, counter, exact image identity

Frequently asked questions

What is verified about Paladin?

The version 1.0 announcement confirms Paladin as a new enemy unit by name. Boundary: version 1.0 announcement. Checked 2026-08-28. The checked source does not publish its role, stats, abilities, encounter, unlock timing, counter, or exact image identity.

Can the Paladin name establish armor or healing?

No. Familiar genre associations cannot replace current game evidence. Capture visible text and repeatable encounter behavior before naming a role, ability, or counter.