Orc Incremental Patch Notes

Quick facts

Ledger scope

Selected official Steam announcements, not a rewritten complete changelog.

Current gate

Steam still showed Coming soon on August 28, 2026.

Demo records

v0.09, v0.08, and v0.05 are historical.

Issue rule

A historical fix is not labeled as a current defect.

Date rule

Each entry uses the publication date shown in the official Steam archive.

Ledger boundaries

This page is a navigation and interpretation layer over official posts. It summarizes only the facts needed to understand release state, Demo continuity, system history, and affected guides. The linked official announcement remains the primary source.

Ledger entry	Build context	What it can support
August 22, 2026 release announcement	1.0 Confirmed	Planned date and announced full-game scope
July 10, 2026 Demo retirement notice	Demo transition	Download status and save compatibility
June 29, 2026 Demo v0.09	Historical Demo	Dated gameplay, interface, unlock, and fix notes
June 11, 2026 Demo v0.08	Historical Demo	Battlefront definition, balance warning, fixes
June 2, 2026 Demo v0.05	Historical Demo	Warpath behavior and condition

The normalized research set contains the official v0.08 and v0.05 post records. Their June 11 and June 2 publication dates were verified against the official Steam news archive during the final content check.

August 22, 2026: release date announcement

The official post planned version 1.0 for September 8, 2026. It announced Assassin, Troll, Warg Raider, and Juggernaut; nine Chieftain bloodlines; a branching Blight Tree with more than 250 nodes; five new Totems; Cryomancer, Paladin, and Griffon; three new legendary bosses; and Trials, balance, progression, usability, and polish improvements.

The announcement does not publish all bloodline, Totem, boss, or node names. It also does not open the live gate by itself. The release date page pairs the announcement with the August 28 Steam Coming soon check, while the Demo comparison shows scope and unknowns row by row.

July 10, 2026: Demo retirement notice

The post titled "End of Demo is tomorrow (Jul 11th)" established the transition state. New Demo downloads ended. Existing installations remain playable indefinitely. The developer said the old save is compatible with the full game, requires no special transfer, and remains after uninstalling the Demo. The post also identifies %APPDATA%/OrcIncremental and Steam Cloud.

These facts answer continuity questions. They do not prove version 1.0 availability on a later date. Use the FAQ save section before manual troubleshooting.

June 29, 2026: Demo v0.09

Demo Update v0.09 is the latest historical Demo patch in the normalized research set. Its relevant records include:

• Unit cards displaying attributes in real time.
• Right-click muting for upgrades and clearer vendor ordering.
• A setting to go back one level after losing to a boss.
• Trial behavior and completion-condition corrections.
• Clearer text for Blight gain inputs and Totem stacking.
• Locked-building hints for Acolyte and Accursed Elf checkpoints.
• A warning that late Demo balance remained incomplete because later upgrades were reserved for the final game.

The post explains that Blight used maximum level and total gold during the current Dark Rebirth cycle as inputs. It does not publish the exact formula. It also describes a Rage cap increase through a Blight Tree upgrade and diminishing returns, while noting that Demo naming and art were work in progress.

Minor follow-up entries v0.09.01 through v0.09.03 addressed the new mute function, a bloodline interaction, a notification icon, an upgrade-limit refund case, and a tentative rare unit-disappearance issue. These remain historical Demo fixes. See the known issues tracker for the current evidence boundary.

June 11, 2026: Demo v0.08

The official v0.08 post defined Battlefront as the main incremental game mode. It added quality-of-life tools such as draw peeking and a DPS meter, changed Warpath controls, and included gameplay, balance, interface, performance, and fix work.

The most durable editorial fact is the developer's balance warning: after several Demo hours, missing later upgrades and rarities made the Demo unrepresentative of the final game. Any v0.08 purchase sequence belongs to historical Demo context. The upgrade priority guide uses this warning to reject a fixed cross-build order.

June 2, 2026: Demo v0.05

The official v0.05 post documented Warpath. The historical condition used the Accursed Elf upgrade, required Auto-Progress, and required winning without losing allies. Surviving units continued into new enemy waves, mini-chests rewarded cleared levels, and right-click toggled the upgrade.

These details belong in the staged Warpath reference. They are not a verified version 1.0 unlock or reward rule. The milestone tracker keeps the old checkpoint visible without carrying it forward.

How to use a historical entry

First match the guide claim to the entry's build. Then ask whether a later official source supersedes it. If the current release state or balance is unknown, keep the historical label and record a new observation separately.

Avoid three failures:

• Combining several Demo versions into a single timeless rule.
• Calling a fixed old issue active without a current reproduction.
• Filling a missing publication date, formula, name, or threshold from memory.

For system navigation, return to the wiki evidence hub. For a current symptom, use the known issues report format.

Official source

Frequently asked questions

Are these notes an official changelog mirror?

No. This is a fan-made index of selected official announcements with build labels and links. The linked Steam posts remain the primary records.

Do old Demo fixes describe current version 1.0 behavior?

No. Entries v0.09, v0.08, and v0.05 are historical Demo context. A mechanic may change before release, so current claims require a newer official source or a labeled build check.

Why is the release announcement listed with patch notes?

It is a major dated product-state update that defines the planned release and confirmed 1.0 scope. It is labeled as an announcement, not as a shipped patch.