Warg Raider

Quick facts

Unit and official role

Warg Raider: area-damage fighter with a hook to pull vulnerable enemies out of safety

Registry status

Warg Raider: UNRANKED · 1.0 CONFIRMED

Build boundary

version 1.0

Evidence check

2026-08-28

Official role boundary

The registry-backed summary above preserves the announcement's exact role sentence. It is a detailed description, but it is still not a full mechanic and should not be copied into independent authored facts.

The wording confirms area damage, a hook, and a purpose for the pull. It does not reveal how a vulnerable target is recognized, how often the hook acts, where a target lands, what the affected area looks like, or which conditions prevent the action.

The confirmed roster keeps the exact role beside the other three announced allies. The formation guide supplies a process for observing movement and access without inventing lane or slot rules.

Observe the hook as a sequence

Treat the description as a sequence of questions. First, identify the target before the hook. Second, capture the movement that follows. Third, record which enemies receive the area attack. Finally, repeat the same setup to see which parts remain consistent.

A recording should show the game build, encounter, army, arrangement, and any progression choices that could affect the result. If the game offers the same encounter again, hold those conditions fixed. Change only Warg Raider's position or one comparison unit.

Do not use a single dramatic pull to state a priority rule. The target may have been selected because of range, timing, a visible status, or an unpublished condition. List the alternatives and design the next repetition to separate them.

Released-build checks

Use this post-launch checklist to keep each observation tied to its build.

In a named version 1.0 build, check:

• which enemy is selected when several targets appear available;
• what the game visibly means by vulnerable in that situation;
• where the hooked target moves;
• whether the pull can fail or be interrupted;
• which enemies receive the area attack;
• whether arrangement changes any part of the sequence;
• which draft or unlock condition the interface states.

The best-formations comparison explains how to keep the setup narrow. A clean test may reveal that placement changes the observed sequence, but it should not become a universal rule until other encounters support it.

What not to infer

The main overclaim risk is treating one visible pull as a complete targeting rule.

No cited source provides a hook priority list, range, timing value, area shape, target count, or numerical result. This page does not infer those details from animation frames or marketing composition. It also does not claim the unit can pull every opponent.

The tier evidence page records the current evidence gate. The announced control focus may be valuable in a particular encounter, but usefulness under one condition is not a global ranking. Comparable results require the same build and recorded test scope.

The hero is official generic key art, not an identified Warg Raider image. It cannot establish appearance, mount, weapon, scale, or animation. No legacy unit portrait is relabeled to fill the gap.

Tie the test to target access

If an important opponent remains protected, the hook description gives you a testable question: can the Warg Raider change access under these exact conditions? Record the blocking enemy, the selected target, and the result after the pull. If the formation already reaches the important target, another role may answer the wall more directly, but that is a choice to test rather than a fixed rule.

The build worksheet keeps the army and progression state visible. This matters because a changed result after several purchases cannot be attributed to the hook alone.

Report format

A strong report states what was visible: target before the hook, movement, affected enemies, repeated attempts, and build. It labels any explanation as a hypothesis. If the next attempt selects a different target, record both cases instead of discarding the inconvenient one.

That record can support a narrow guide update after release. Until then, the official role is the complete verified boundary.

Official source

Confirmed unit record

Unit

Warg Raider

Official role

area-damage fighter with a hook to pull vulnerable enemies out of safety

Evaluation

UNRANKED · 1.0 CONFIRMED

Checked

2026-08-28

Frequently asked questions

What is Warg Raider's confirmed role and status?

Warg Raider is an area-damage fighter with a hook to pull vulnerable enemies out of safety. Its registry status is UNRANKED · 1.0 CONFIRMED, checked 2026-08-28.

Why does Warg Raider 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?

Record which target the hook selects, where it moves that target, and what the area attack reaches in a named build. Repeat the observation before stating a rule.