Orc Incremental Temple
A historical Temple unlock reference and current-build verification checklist without invented costs, levels, effects, activity ownership, or upgrade priorities.
- Published
- Updated
- Last checked
Not verified yet

Quick facts
- Historical building
- Temple
- Historical milestone
- Acolyte
- Current unlock
- Not established
- Effects and costs
- Not published in the checked evidence
Keep the milestone historical
The fact panel preserves one Demo tooltip relationship. It is not a promise about the current build. The Acolyte portrait illustrates the named milestone character but does not show the Temple, its unlock event, or its functions.
Use the buildings overview for the shared evidence rules and progression for diagnosing a currently locked system.
Verify before and after the milestone
Capture the current locked tooltip before reaching the relevant progression point. After the event, record the first available building state without purchasing anything.
| Field | What to record |
|---|---|
| Build | Exact current label |
| Locked state | Full tooltip text |
| Milestone | Exact visible name |
| Unlock event | Prompt or screen transition |
| First screen | Available tabs and labels |
| Costs | Exact visible values, if any |
| Effects | Complete visible wording |
| Missing fields | Explicit unknowns |
If the historical milestone no longer matches, keep both records. Do not rewrite the Demo tooltip into a current statement.
Learn purpose from the interface
A building name or portrait does not reveal functions. Transcribe every visible option before testing one. Separate displayed description from an observed result and from any interpretation.
When a purchase is possible, define one measurable outcome and hold other systems fixed. A changed result can support a narrow observation; it does not establish a hidden formula or optimal order.
Do not infer an activity link
Require explicit current wording before connecting the Temple to an activity. Screen proximity or a shared milestone is not enough. Record the navigation path as context only.
The Missions guide shows how to document an activity without assigning it to a building. That separation should remain until evidence connects the records.
Review on updates
Start a new row when the build changes. Compare locked wording, milestone, first screen, options, and observed results. Preserve screenshots with their dates and avoid using old art as proof of a current state.
This page answers the historical question while giving the reader a safe way to establish the current one.
Troubleshoot a missing unlock safely
Confirm the build and exact milestone label first. Reopen the relevant screen, check the locked tooltip, and record whether a prompt is pending. Do not edit save data or assume the historical condition still controls the current build.
If the building remains unavailable, compare a fresh screenshot with a successful current-build record only when progression context matches. Report the missing transition and the checks performed. That is actionable evidence for a known-issues report without declaring a live bug from one state.
Official sourceVerification boundary
- Build boundary
- historical Demo tooltip
- Evidence check
- Still unknown
- current unlock, costs, levels, effects, activity assignment, upgrade order
Frequently asked questions
- What is verified about Temple?
- A historical Demo tooltip says the Temple unlocks at Acolyte. Boundary: historical Demo tooltip. Checked 2026-08-28. The checked evidence does not publish the current version 1.0 unlock, Temple costs, levels, effects, activity assignment, or upgrade order.
- How should the current Temple milestone be checked?
- Capture the locked tooltip before the milestone, the unlock event, and the first available screen under one build. Preserve the historical Demo wording as a separate record.
Source ledger
- Demo Update v0.09
steam-announcement ·