Orc Incremental Beginner Guide

Quick facts

First check

Watch which ally falls first and which enemy stops the push.

Draft goal

Fill a missing job before collecting another copy of the same job.

Position test

Move one unit, replay, and compare the same battle result.

Upgrade rule

Spend against the observed bottleneck instead of following a fixed list.

Evidence limit

Demo details are historical; exact 1.0 values are not verified yet.

Read the first draft as a team decision

The official Steam page describes Orc Incremental as an incremental auto battler where players draft units and Totems, arrange a formation, and let combat resolve. That makes the first draft a team decision. A card is not useful only because its text looks strong; it is useful when it performs a job your current group cannot perform.

Start with three questions:

1. Who stands where enemy pressure arrives first?
2. Who deals damage while that front line holds?
3. Who changes a bad exchange through support, control, or a tactical spell?

The checked sources do not publish a universal opening draft or a complete version 1.0 unit table. Avoid turning a promotional screenshot into a ranked list. Use the unit roles reference when it is published, and keep an observation tied to the build label shown in your game.

Choose a missing job

If every ally needs protection, another fragile attacker may make the formation collapse faster. If the front line survives but the important enemy remains untouched, more durability may extend the loss without solving it. This distinction is more reliable than saying a unit is always the correct pick.

Write a short draft note: "front line fails," "damage cannot reach," or "economy is too slow." Pick the card that addresses that note. If none does, choose the option with the clearest testable effect and record the outcome.

Position before buying around a positioning mistake

Formation is an official part of the game, and position can change who is exposed, who reaches a target, and whether a unit has time to act. Before buying several upgrades, replay the same encounter after moving one unit. The formation guide will hold verified lane and placement details; this beginner procedure stays valid without claiming an unpublished grid rule.

Use a simple position test:

• Keep the drafted group unchanged.
• Move only the suspected unit.
• Replay the same battle if the game allows it.
• Note the first ally defeated and the enemy that remains.
• Keep the change only when it fixes the stated problem.

Do not infer a hidden targeting formula from one fight. Randomness, animation timing, or a different enemy arrangement can create a misleading result. Repeat a close comparison before treating it as a pattern.

Name the battle wall

A battle wall is the first repeatable reason the run stops making useful forward progress. Naming it prevents waste. Use the following diagnostic table before opening the upgrade screen.

What you see	Likely category	First controlled test
Front line disappears before allies act	Survival	Protect, reposition, or strengthen the exposed role
Allies survive but cannot finish the target	Damage delivery	Test access, focus, or a damage choice
Damage lands on the wrong target	Targeting or position	Change one position and replay
The formation works but the next purchase takes too long	Economy	Compare progress per run before buying combat power
A repeatable run adds little permanent progress	Reset timing	Check the available permanent system and opportunity cost

These categories are a diagnostic framework, not a claim about a hidden calculation. Continue with the progression wall guide when the same symptom persists across several purchases.

Avoid the five-change replay

A common failure is buying several upgrades, changing three positions, and using a different draft before replaying. A win after that sequence teaches almost nothing. You cannot identify which choice mattered, so the next wall produces the same confusion.

One-change tests are slower for a single click and faster for the whole run. Record the before state, make the smallest plausible correction, and compare. If it fails, undo it when possible and test the next category.

Buy for the diagnosed bottleneck

The official sources establish a broader incremental loop but do not provide complete costs, return-on-investment formulas, or a fixed purchase order. The upgrade priority framework therefore sorts choices by problem rather than by an invented numerical ranking.

For a first run:

1. Buy survival when the necessary unit dies before performing its job.
2. Buy damage or access when the group lives but cannot remove the blocking target.
3. Buy economy when the combat plan works and waiting for the next meaningful purchase is the actual limit.
4. Save for a permanent choice when short-run purchases no longer change the diagnosed result.

Demo update v0.08 matters here because the developer warned that its Battlefront balance became distorted after several hours; some upgrades and rarities were reserved for the final game. Treat an old Demo purchase sequence as historical evidence, not a version 1.0 prescription.

Decide whether another fight or a reset teaches more

Dark Rebirth and permanent bonuses are part of the official store description. Historical Demo notes also discuss Blight in a Dark Rebirth cycle, but the checked sources do not publish a current gain formula or a universal reset point. The Dark Rebirth guide will own those verified mechanics and the rebirth planner is staged for later implementation.

Before resetting, ask:

• Is the current wall diagnosed rather than merely slow?
• Does one affordable combat or position change still test the diagnosis?
• Is a permanent-progression option actually available in this build?
• Can you state what the next run is expected to do differently?

If the last answer is no, collect more evidence from the current run. If the answer is specific, such as keeping the front line alive long enough for one more action, the reset has a testable purpose.

Keep a compact first-run log

The log does not need exact formulas. Four fields are enough: build label, wall, single change, result. For example, record that the front unit fell before support acted, then note whether moving support or buying survival changed that sequence.

This is also the safest way to contribute a correction later. A result linked to a build and repeatable condition can be checked. "This felt stronger" cannot. For a visual experiment after the route ships, use the staged formation builder rather than treating a screenshot as verified mechanics.

First-run mistakes to avoid

• Do not copy an unlabeled build from a clip or screenshot.
• Do not call a Demo threshold a version 1.0 threshold.
• Do not buy across every category before checking the next fight.
• Do not assume longer survival means the important target is reachable.
• Do not reset only because progress feels slow; state what the reset changes.
• Do not publish a formula the official sources have not provided.

The goal of a first run is not perfect optimization. It is learning to separate formation, combat power, economy, and permanent progress so each later decision has a clear reason.

Official source

Frequently asked questions

What should I change when an early battle stalls?

Change one variable at a time. Check whether the front line survives, whether damage reaches the target, and whether a different position changes the result. That produces a useful diagnosis instead of hiding the wall behind several simultaneous purchases.

Should I copy an old Demo upgrade threshold?

No. Historical Demo updates describe systems and past balance, but they do not establish a version 1.0 threshold. Use them to understand the loop, then verify numbers in your own labeled build before making a numerical recommendation.

When should a new player consider a reset?

Consider it only after the relevant reset is available and the current run has a clearly diagnosed wall. Official sources verify reset and permanent-progression systems, but this snapshot does not publish a universal timing formula.