Juggernaut

Quick facts

Unit and official role

Juggernaut: explosive siege assault unit

Registry status

Juggernaut: UNRANKED · 1.0 CONFIRMED

Build boundary

version 1.0

Evidence check

2026-08-28

Confirmed identity and limit

The registry-backed summary above owns the exact official identity, role, and status text. The source does not define siege, describe an explosion, identify a preferred target, or publish a value, so this article focuses on those open checks.

Those gaps should stay visible. A familiar class name is not evidence that Orc Incremental follows rules from another game. The version 1.0 roster records the exact language for all four announced allies and keeps each performance state unranked.

For position experiments, begin with the formation diagnosis guide. It asks what changed on screen without assuming a fixed grid, lane, or target formula.

Define the siege observation

Start by identifying what the game presents as a siege interaction. Record the opponent or object involved, the visible action, and the result. If an explosive effect appears, note the affected targets without estimating a radius from a promotional frame.

Keep the army and encounter fixed across repeated attempts. Change only Juggernaut's position or the one comparison unit. Record whether the same target is selected and whether the same affected group appears. If the result varies, keep the variation in the report.

The word "assault" does not establish that Juggernaut must stand in front. Position is an open question until the released game supplies observable behavior. A name also cannot establish durability or movement.

Released-build checklist

Treat this as a post-launch checklist, not as a prediction of behavior.

For a named released build, record:

• what target or object triggers the siege description;
• how the interface identifies an explosive event;
• which targets are visibly affected;
• whether position changes reach or target selection;
• whether the behavior repeats in the same encounter;
• which draft or unlock condition is displayed;
• whether a later combat patch changes the case.

Use the build comparison worksheet to preserve conditions. A useful note says what happened and what single variable changed, not merely that one army won.

Unsupported conclusions

The main overclaim risk is filling the siege label with familiar but unverified rules.

No checked source provides Juggernaut's numerical output, blast area, attack interval, target priority, cost, rarity, or acquisition rule. This page does not assign any of them. It also does not claim that every enemy or structure receives a special effect.

The tier evidence page explains why a comparative placement has not met the evidence threshold. Missing placement is not a low placement, and a good result against one siege target would remain scoped.

The hero is the official Orc Incremental logo, not unit artwork. It makes no visual claim about Juggernaut. An official asset should be used later only when its identity is explicit and its build context is recorded.

Test the actual wall

If the army reaches normal enemies but stalls at a fortified or large target, Juggernaut's announced role suggests a test. It does not guarantee the answer. Compare the same encounter with one army change and record the relevant sequence.

If the front line fails before Juggernaut acts, the immediate wall may be survival or access rather than siege output. If the formation already clears the relevant target, another test may provide more information. The best-formations method helps state the bottleneck and comparison scope before a recommendation.

Record the case

Record the build label, encounter, army, arrangement, first relevant target, visible explosive cue, affected targets, and repeated outcomes. Separate facts shown by the interface from an explanation based on timing.

When a result cannot be repeated, keep it as an open case. When it repeats, describe only the conditions tested. That discipline makes a later patch review possible and prevents an isolated win from turning into a universal mechanic.

Official source

Confirmed unit record

Unit

Juggernaut

Official role

explosive siege assault unit

Evaluation

UNRANKED · 1.0 CONFIRMED

Checked

2026-08-28

Frequently asked questions

What is Juggernaut's confirmed role and status?

Juggernaut is an explosive siege assault unit. Its registry status is UNRANKED · 1.0 CONFIRMED, checked 2026-08-28.

Why does Juggernaut have that evaluation status?

Pre-release official evidence confirms the unit's role but does not provide comparable version 1.0 performance results. The evaluation is scoped to version 1.0 and carries the recorded status UNRANKED · 1.0 CONFIRMED.

What should be checked after release?

Observe what the game treats as siege and explosive behavior in a named build. Compare repeated battles while holding the opposing wave and the rest of the formation constant.