Orc Incremental Barracks

Quick facts

Historical building

Barracks

Tooltip context

Accursed Elf activity unlock

Exact activity assignment

Not established

Current details

Not established

Do not assign from proximity

The historical source places this building in activity-unlock tooltip context but does not establish an exact mapping. The orc warrior hero is thematic army art; it does not depict the building, an unlock screen, or one of its functions.

Use the buildings overview for the full ambiguity and Missions for a separate activity record. Neither page supplies a missing assignment.

Capture the current building path

Record every step from the locked state to the first available screen.

Field	Evidence to keep
Build	Exact version or date
Locked tooltip	Complete current wording
Milestone	Visible requirement and event
Navigation	Exact screen path
First state	Tabs, buttons, and labels
Options	Full descriptions and costs
Explicit links	Only named activity relationships
Unknowns	Anything not exposed

Do not infer purpose from the hero, building name, or nearby unit art.

Separate options from outcomes

Transcribe a visible option before selecting it. Record the before state, the choice, and the first observable change. If other purchases occur, list them as uncontrolled variables.

One changed result cannot establish a complete effect or upgrade priority. Repeat under a shared checkpoint and report the narrow observation.

Verify any activity relationship directly

An exact link needs current interface text or a direct official statement. A menu button inside the building can establish an access path; a tooltip listed alongside another activity cannot establish ownership by itself.

If a relationship becomes visible, capture both ends: the building screen and the activity header. Preserve the build so a later navigation change does not rewrite the old record.

Keep strategy provisional

Costs, levels, effects, and alternatives must be current before advice is possible. Use the upgrade-priority framework to test a diagnosed bottleneck only after those inputs exist.

Until then, the safe result is a versioned building shell with a clear evidence threshold for each addition.

That restraint also keeps later corrections small: a verified label can replace one unknown without forcing a speculative mechanics page to be unwound.

Troubleshoot access without save edits

Verify the current build, milestone text, and navigation path. Capture the locked or missing state before restarting the interface. If another current record shows access, compare progression context rather than copying its steps blindly.

Do not modify save contents to force the building open. Preserve a backup before any manual file operation and use the known issues ledger to distinguish a documented problem from an isolated observation.

Official source

Verification boundary

Build boundary

Demo v0.09 tooltip context

Evidence check

2026-08-28

Still unknown

activity assignment, current unlock, costs, levels, effects, upgrade order

Frequently asked questions

What is verified about Barracks?

Demo v0.09 tooltip context mentions Barracks around the Accursed Elf unlock for Trials and Missions. Boundary: Demo v0.09 tooltip context. Checked 2026-08-28. The source does not establish which activity belongs to Barracks or publish current version 1.0 costs, levels, effects, unlocks, or upgrade order.

Can tooltip proximity assign an activity to Barracks?

No. Require explicit current interface text or a direct official statement. Record nearby labels as context, not as an assignment.