Orc Incremental Missions

Quick facts

Historical unlock

Accursed Elf

Exact Mission list

Not published

Building context

Shamanic Hut and Barracks tooltips

Assignment status

No exact activity-to-building assignment

Leave the catalog empty until observed

The historical source supplies an unlock context but no exact Mission catalog. This page therefore begins with a method, not a fabricated list. Generic key art does not show a Mission screen, building, objective, or reward.

Use the Trials reference for separately named historical activities and the buildings overview for the tooltip ambiguity. Do not assign either activity to a building because the terms appeared together.

Add one Mission at a time

Create a row only when the current interface supplies a name. Preserve its build and exact text so another reader can distinguish a current observation from the Demo-era source boundary.

Field	What to capture
Name	Complete visible Mission label
Build	Exact version or date
Access	Screen and availability state
Objective	Full visible condition
Restrictions	Any army, upgrade, or timing text
Start state	Formation and progression context
Completion	Exact success indication
Reward	Visible reward wording

Missing text remains unknown. Never derive a reward from an icon or an objective from a title.

Diagnose a failed attempt

Record the first event that makes the objective impossible: loss of a required ally, missed threshold, insufficient damage, or another visible condition. Verify the wording before proposing a change.

Change one controllable variable and repeat. A formation move can test survival order; one purchase can test a named bottleneck. If several variables move together, describe the result as a case study rather than a solution.

Verify the access path independently

The page or building from which a Mission is opened should be recorded from the current interface. A historical tooltip reference is not an exact ownership statement. Capture the navigation path and visible header without turning proximity into a mechanic.

If access changes after an update, keep the old path labeled and add the new one. That distinction matters for troubleshooting without rewriting history.

Avoid false completion

A few observed rows do not prove a complete list. Mark catalog coverage by build and source. Avoid invented ordering, categories, optimal teams, or recurring schedules unless the current interface explicitly supports each claim.

The useful Mission guide is reproducible and modest: exact visible text, a clear access path, one controlled observation, and an honest statement of what the checked material does not publish.

Keep reward and objective evidence separate

A completion screen can prove the displayed reward for that run without proving a fixed reward table. An objective screen can prove wording without proving every hidden eligibility rule. Capture both and connect them only through the same run record.

If a repeat produces a different display, compare build, modifiers, completion grade, and other visible context before proposing a rule. Publish the variation rather than choosing the row that looks most representative.

Official source

Verification boundary

Build boundary

Demo v0.09 patch-note scan

Evidence check

2026-08-28

Still unknown

Mission names, Mission rules, rewards, building assignment, version 1.0 state

Frequently asked questions

What is verified about Missions?

Demo v0.09 patch notes state that Trials and Missions unlocked at the Accursed Elf and mention Shamanic Hut and Barracks tooltip context. Boundary: Demo v0.09 patch-note scan. Checked 2026-08-28. The checked source publishes no exact Mission list and does not assign one activity to one building or establish current version 1.0 rules or rewards.

How should a Mission observation be recorded?

Use the exact current label, build, where it appeared, stated objective, entry state, completion result, and visible reward. Keep the building association unknown unless the interface explicitly states one.