Orc Incremental Shamanic Hut

Quick facts

Historical building

Shamanic Hut

Tooltip context

Accursed Elf activity unlock

Exact activity assignment

Not established

Current details

Not established

Keep art and building evidence apart

The fact panel preserves the historical tooltip boundary. The Shaman variants are thematic unit art; they do not show the Hut, a building screen, an activity, or an unlock relationship. Their appearance cannot fill any mechanics gap.

Use the buildings overview for the shared ambiguity and the Trials reference for one separately recorded activity.

Build a current unlock record

Start before the building becomes available and preserve the complete interface sequence.

Field	Current evidence
Build	Exact version or dated build
Locked text	Full tooltip wording
Requirement	Exact visible milestone
Unlock event	Prompt or screen change
Navigation	Path to the first building screen
Options	Names, descriptions, and costs
Activity link	Direct visible wording only
Unknowns	Values or relationships not exposed

If the building is already unlocked, state that the earlier transition was not observed. Do not reconstruct it from memory.

Test one option independently

Capture a description before using or purchasing it. Record a shared checkpoint, before state, choice, and first observable result. Hold other purchases and formation changes fixed where possible.

Separate what the tooltip says from what the test shows. A visual theme does not establish Totem, spell, unit, or activity mechanics unless the interface explicitly names the connection.

Refuse an inferred activity assignment

Historical tooltip context can guide where to inspect. It cannot decide which nearby building owns which nearby activity. Require an explicit current label or official statement.

If a button opens an activity, record the button text, destination header, and build. That is enough to document an access path without claiming broader ownership.

Version every change

On updates, compare locked text, requirement, navigation, available options, and observed outcomes field by field. Keep the Demo evidence as history instead of relabeling it.

The result should remain visibly incomplete until the current game supplies facts. That is more useful than a confident building guide built from thematic art and ambiguous proximity.

Troubleshoot a missing screen methodically

Record the current build, progression milestone, locked tooltip, and navigation steps. Restarting the interface may be a reversible check, but it should not erase the original observation. Never edit the save to expose a building.

Compare against another current-build record only when progression context matches. If the screen still differs, publish the discrepancy and checks performed in the known issues ledger rather than declaring the historical requirement current.

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 Shamanic Hut?

Demo v0.09 tooltip context mentions Shamanic Hut 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 Shamanic Hut or publish current version 1.0 costs, levels, effects, unlocks, or upgrade order.

Can tooltip proximity assign an activity to Shamanic Hut?

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