Orc Incremental Warpath

Quick facts

Historical build

Demo v0.05

Historical source

Accursed Elf upgrade

Historical continuation

Survivors continued into new waves after a qualifying win.

Historical reward

Mini-chests for levels cleared

Historical toggle

Right click on the upgrade button

Read this as history first

The fact panel above contains the complete checked Demo behavior. Every element stays attached to that build. The axe preview is historical promotional art and does not prove that the mode, input, reward, or tuning exists unchanged now.

Use the Battlefront guide for a general wall record and the Trials reference for a separate historical activity. Do not merge their terms because they appeared in nearby patch notes.

Verify the current entry point

Before attempting a run, capture the current tooltip, availability state, input cue, and any prerequisite text. If the old label is absent, record the screen searched and stop there. Absence in one menu is not proof that a system was removed.

Field	Current-build capture
Version	Exact label or date
Entry	Screen and visible control
Requirements	Complete displayed text
Start state	Army, formation, and progression checkpoint
Transition	What happens after a qualifying battle
Reward	Exact visible label and amount, if shown
Exit	How the sequence ends

Keep the historical fields as comparison prompts, not expected results.

Observe the transition in order

Record survivor state at the end of the battle, the next screen or wave, and the first reward display. Order helps distinguish a continuation from a normal progression transition. Repeat at the same checkpoint before changing the formation or purchases.

If an ally is lost, treat that attempt as a separate condition rather than filling in what would have happened. If a toggle exists, capture both states and confirm which visual indicator changes.

Do not estimate hidden rewards

A visible reward can be recorded exactly. Missing reward text should remain missing. Do not infer a per-level rate, cap, or probability from a short sequence, and do not use the historical summary as a current calculation.

For a comparison, hold the build and start state fixed. Record levels entered, levels cleared, the stopping event, and the complete reward display. Several repeats can support a narrow observation; they still do not establish an unpublished formula.

Preserve the version boundary

If the present system differs from the old note, publish two rows. Name which control, requirement, transition, or reward changed. Avoid phrases such as “still works” unless every included element was checked.

A careful Warpath page should make the next current-build inspection easy while refusing to turn an old patch note into release advice.

Record negative checks precisely

If the old control or transition cannot be found, document the build, screen, prerequisite state, and terms searched. “Not found here” is more accurate than “removed.” Another unlock state or interface path may explain the absence.

Likewise, a sequence ending normally does not prove the special continuation is unavailable unless the starting conditions were visible and controlled. Negative evidence becomes useful when it is specific enough for another player to repeat, and harmless when its limits are stated beside it.

Official source

Verification boundary

Build boundary

Demo v0.05

Evidence check

2026-08-28

Still unknown

version 1.0 availability, current trigger, current rewards, current toggle, current tuning

Frequently asked questions

What is verified about Warpath?

Demo v0.05 documented Warpath as an Accursed Elf upgrade: with Auto-Progress enabled, a win without lost allies sent survivors into more waves and awarded mini-chests for levels cleared; its upgrade-button toggle used right click. Boundary: Demo v0.05. Checked 2026-08-28. The checked source does not confirm that trigger, continuation, reward, toggle, tuning, or availability for version 1.0.

How can a current Warpath test avoid carrying forward Demo behavior?

Start from the current tooltip and input cue, then record the qualifying battle, survivors, next visible state, and reward. Mark every historical field that is absent or changed instead of assuming continuity.