What is confirmed

Steam confirms 11 achievements for Sir, We Have an Orc Problem. Existing guide material also points to help for Levels 3.2, 6.1, and 6.2, and a video title associates Mission 6.1 with an achievement called “Four-tified.” The collected material does not establish the full achievement list, exact unlock conditions, or one verified layout for every stage.

This hub separates a useful campaign workflow from stage claims that still need same-version proof.

Prepare a difficult stage

Use the first attempt as a scout rather than forcing a complete clear. Watch where the orc mass actually travels, where routes merge, and where the defense first loses control. Build the next attempt around that observed pressure point.

Concentrate overlapping fire at bends, gates, bridges, or merge points. Keep rear coverage for survivors and aim knockback back into the defended area. If the route behaves differently than expected, recall and rebuild with R instead of protecting a weak position for the rest of the run.

Turn failure into progression

Resources continue after won or lost runs and feed permanent upgrades. A failed stage can therefore answer two questions: what part of the defense failed, and which upgrade would change that failure? Strengthen damage when targets survive the kill zone, test economy when progress is resource-bound, and unlock a new role when the current turret mix cannot cover the map.

Avoid changing the placement, turret mix, and several upgrades at the same time. One controlled change per attempt creates a clearer stage solution and makes later advice easier to verify.

Known difficult-level leads

Current guide references identify Levels 3.2, 6.1, and 6.2 as stages for which players have sought dedicated help. They are useful research leads, not proof that only those missions are difficult. Exact enemy counts, coordinates, and wave-by-wave layouts remain To be confirmed.

For Mission 6.1, the “Four-tified” name is documented through a video title, but its precise requirement and required placement could not be verified from the available transcript. Do not present an inferred condition as a confirmed unlock method.

Achievement tracking method

Create a simple checklist with four fields: achievement name, visible description, attempted condition, and game version. Capture the unlock screen or Steam notification when a condition works. If the requirement is hidden, change only one factor per run so the result can be reproduced.

Steam achievement totals are reliable for confirming that 11 exist, but the store total alone does not explain their requirements. Community guides should label each entry as confirmed, community-reported, or To be confirmed.

Current campaign checklist

  • Scout the route and record the first leak point.
  • Rebuild around observed traffic, not decorative map geometry.
  • Use active abilities to recover from pressure spikes.
  • Spend permanent resources against the diagnosed bottleneck.
  • Track Levels 3.2, 6.1, and 6.2 as current research leads.
  • Verify achievement conditions on the live version before publishing them as facts.

This page now provides a complete process for progressing and documenting difficult stages. Detailed stage maps and all 11 achievement requirements will remain visibly marked until they can be reproduced.