Orc Incremental Known Issues

Quick facts

Current list

No official version 1.0 issue list verified in this snapshot.

Historical fixes

Demo patch notes record resolved and tentative fixes.

Active status

Not verified yet unless current official evidence exists.

Useful report

Build, platform, mode, steps, expectation, result, reproduction.

Save safety

Back up files before manual troubleshooting.

Read the status before the symptom

This page separates three categories:

Category	Meaning	Reader action
Current verified issue	Supported by a current official source or a documented current-build reproduction	Follow the stated workaround and scope
Fixed historical Demo issue	Recorded in a dated Demo patch	Do not assume it remains active
Verification gap	A plausible symptom without enough current evidence	Collect a safe reproduction before labeling

No current verified issue entries are available here because there is no current official 1.0 issue list in the checked source set. That plain gap is more accurate than filling the page with old fixes.

Historical Demo issue categories

Official Demo updates recorded work across several categories. The normalized research and implementation plan identify Warpath camera or progression behavior, a rendering crash, late-game performance, audio channels, disappearing units or drag overlap, tooltip overlap, upgrade-limit refunds, and infinite enemy health.

These are historical Demo categories. They help a reader search the official update ledger, but they do not establish current recurrence.

Unit movement and disappearance

The v0.09 follow-up described a tentative fix for a rare case where two units could disappear from the base after being dragged to the same location. "Tentative" and "historical" both matter. A similar current symptom needs a fresh build label and reproduction.

Upgrade limits and refunds

Another v0.09 follow-up fixed a case where a previously unlocked upgrade level remained visible after its limit was lowered and said the spent gold would be returned. That is evidence for the old Demo fix, not a promise about every refund path.

Trials and completion conditions

Demo v0.09 corrected several Trial behaviors and changed a condition from reaching level 60 to winning level 60. This illustrates why old guide wording can become wrong after a patch. The staged Trials guide must cite its build for any completion rule.

Battlefront, Warpath, performance, and interface

Demo v0.08 included Battlefront, Warpath, quality-of-life, performance, and fix changes. Demo v0.05 documented Warpath behavior. Camera, progression, rendering, late-game performance, audio, and tooltip records all remain tied to their dated Demo context. The staged Battlefront reference and Warpath reference will keep that boundary.

Reproduce a current symptom safely

Before reporting:

1. Record the exact build label and platform.
2. Name the mode, encounter, unit, or screen.
3. Write the shortest steps that trigger the symptom.
4. State the expected and observed results separately.
5. Restart and try the same steps once.
6. Note whether another save reproduces it without overwriting progress.
7. Attach a screenshot only if it contains no sensitive information.

If the issue involves progress or offline gold, back up %APPDATA%/OrcIncremental on Windows before touching files. Check the offline gains guide for a controlled timing test and the FAQ save answers for official Demo continuity and Steam Cloud facts.

Triage by symptom, not by an old patch title

For a crash, record the last stable screen and action. For disappearing or overlapping units, record the formation state and drag sequence. For a progress stall, separate a blocked unlock from slow economy. For audio, record the channel and whether settings or restart change it. For a tooltip problem, capture the viewport and element.

Do not label a symptom as infinite enemy health merely because an enemy survives longer than expected. Rule out target access, damage delivery, and build mismatch first through the progression diagnosis.

Known-issue reporting mistakes

• Posting no build or platform.
• Calling a historical Demo fix a current version 1.0 issue.
• Combining save sync, offline timing, and upgrade changes in one test.
• Sharing a live save without a backup.
• Treating an unreproduced visual anomaly as a mechanic.
• Using an old workaround without checking whether the relevant interface still exists.

The release status page is the authority for the current gate. Once version 1.0 is officially available, this tracker still needs current evidence before it can claim an active release issue.

Official source

Frequently asked questions

Is there a current official version 1.0 issue list?

No current official version 1.0 issue list was present in the checked source set. This page therefore separates that verification gap from older Demo fixes instead of presenting historical reports as active defects.

Does a historical fix prove the problem cannot return?

No. A dated fix proves what the developer reported for that historical Demo build. A later recurrence needs a fresh build number, reproduction steps, and current evidence.

What should an issue report include?

Record the build label, platform, mode, steps, expected result, observed result, and whether a restart reproduces it. Include a screenshot or save backup only when it can be shared safely.