Orc Incremental Battlefront

Quick facts

Historical build

Demo v0.08

Historical label

Main incremental game mode

Balance boundary

The Demo warning applied after a few hours.

Current status

Version 1.0 behavior is not established by this source.

Keep the warning with its build

The registered summary preserves old terminology and its limitation together. It is useful history, not a current speed target. The battle hero is promotional combat art; it does not show the named Demo build, an exact level, or current balance.

Use the progression diagnosis when the question is why a run stopped. Use the formation guide when positions or survivor order may explain the result. Historical patch notes remain the place to check the original version label.

Record the wall before changing anything

A useful Battlefront note begins with the first repeatable failure, not an impression that progress is slow.

Field	Record
Build	Exact visible version or date
Checkpoint	Named level, wave, or encounter
Army	Units and current roles
Formation	Positions before the attempt
Purchases	Changes made since the last success
Failure	First observable event that ends progress
Repeat	Result across comparable attempts

Separate an ally dying early from insufficient damage, delayed economy, or a locked system. Each points to a different next test.

Change one layer at a time

Start with the cheapest reversible check. Move one position, replay the same checkpoint, and record survivor order. If position does not change the failure, test one affordable purchase tied to the observed bottleneck. Do not change the army, route, upgrades, and reset state in one comparison and then credit a single cause.

A better result at one checkpoint does not establish a universal build. State the build and objective in every conclusion. Preserve unsuccessful tests because they narrow the next decision.

Measure without inventing balance

Choose a stable interval: attempts to clear a named encounter, time between two visible milestones, or survivor state after a fixed wave. Record exactly what the interface exposes. Do not derive hidden rates from animation frames or treat a promotional screenshot as a balance table.

Historical imbalance language explains why the old Demo was not a final benchmark. It does not prove that current progress should be faster, slower, or smooth for a particular number of hours.

Start a new record after updates

When the build changes, duplicate the observation template and update it from the current interface. Keep old results under their old label. Compare checkpoint, army, formation, purchases, and failure event before calling anything a balance change.

The safest Battlefront advice is local: name the wall, select one variable, define a stop condition, and report the observed result. That remains useful even when broader tuning changes.

Turn one result into the next test

End each note with a decision, not a vague score. If a position change delays the same failure, the next test can check whether that delay repeats. If a purchase moves the wall to a different event, start a fresh diagnosis for that event. If nothing changes, stop spending on the same theory until a new observation supports it.

Include the failed baseline beside the improved attempt. Readers need both to judge whether the comparison was meaningful. A table of only successful runs hides selection effects and encourages a result to be copied into a different army or build.

Official source

Verification boundary

Build boundary

Demo v0.08

Evidence check

2026-08-28

Still unknown

current balance, current rewards, current progression speed, current mode rules

Frequently asked questions

What is verified about Battlefront?

Demo v0.08 described Battlefront as the main incremental game mode and warned that the Demo could not stay balanced after a few hours because some upgrades and rarities were reserved for the final version. Boundary: Demo v0.08. Checked 2026-08-28. That historical definition and balance warning do not establish current version 1.0 balance, rewards, progression speed, or mode rules.

How should a current Battlefront observation be labeled?

Record the current build, checkpoint, army, formation, purchases, elapsed interval, and visible result. Keep it separate from the historical Demo warning rather than treating old balance language as a current benchmark.