Orc Incremental Buildings

Quick facts

Historical Temple milestone

Acolyte

Historical tooltip context

Shamanic Hut and Barracks

Activity assignment

Not established

Current building data

Not established

Treat tooltip context as context

The registry preserves what the checked historical material can support. It does not turn nearby building and activity labels into ownership rules. The Blacksmith portrait is thematic system art and does not show one of the three covered buildings or a current unlock screen.

Use the individual Temple, Barracks, and Shamanic Hut pages for bounded records. Use Missions and Trials without assuming an exact building link.

Capture a locked state first

A reliable unlock record begins before the milestone, while the full tooltip is visible.

Field	Evidence
Building	Exact current name
Build	Version or dated build
Locked text	Complete tooltip wording
Preceding milestone	Exact visible label
Unlock event	Screen, prompt, or transition
First available state	Options visible immediately afterward
Activity link	Only explicit interface wording
Unknowns	Costs, effects, or requirements not shown

Screenshot order matters. Capture the before and after state under one build rather than reconstructing the sequence from memory.

Separate unlock, purpose, and upgrade

Unlock evidence answers when a building becomes available. It does not establish every function. A visible option answers what can be selected, not its hidden effect. An observed result answers one test under one setup.

Keep these layers in separate rows. That prevents a milestone tooltip from becoming a full mechanics page and makes later patch review easier.

Avoid false activity assignments

When two buildings and two activities appear in the same historical context, several mappings remain possible. Require direct wording from the current interface or an official statement before assigning either pair.

Navigation path is useful evidence but not proof of ownership. Record where a button appears and the label above it without expanding that relationship.

Version every current addition

On release or a later patch, check locked text, unlock event, visible options, costs, levels, and effects again. Keep the Demo record labeled. If a building changes purpose, add a new row rather than silently correcting the old source.

The result is a modest but dependable unlock map: exact visible facts, independent relationships, and explicit gaps.

Keep a current comparison table

Once several buildings are visible in one build, compare only shared fields: locked wording, milestone, first available options, and directly stated relationships. Do not force different systems into a universal level or cost table when their interfaces expose different concepts.

Mark every cell by evidence type. A tooltip transcription, observed transition, and inferred purpose should never look equivalent. This table can reveal which building needs a new capture without turning missing cells into guessed values or an upgrade ranking.

Official source

Verification boundary

Build boundary

Demo v0.09 tooltip context

Evidence check

2026-08-28

Still unknown

activity assignment, current costs, current effects, levels, version 1.0 unlocks

Frequently asked questions

What is verified about Buildings?

Historical Demo tooltip evidence places Temple at the Acolyte milestone and mentions Shamanic Hut and Barracks around the Accursed Elf activity-unlock context. Boundary: Demo v0.09 tooltip context. Checked 2026-08-28. The checked evidence does not assign Trials or Missions to one of those two buildings or establish current version 1.0 costs, effects, levels, or unlocks.

How should a current building unlock be verified?

Record the build, exact locked tooltip, preceding milestone, unlock event, and first available state. Do not infer an activity assignment from neighboring tooltip context.