How does Overwatch work in Zero Company?

It sets a directional cone that fires when an enemy moves or acts inside it, and it ends the Operator's turn.

Does setting Overwatch end an Operator's turn?

Yes. Overwatch ends that Operator's turn.

Is there a hunker-down action in Zero Company?

No. There is no hunker-down action, which is why a spare Action Point is usually best spent on Overwatch.

Mechanic

Zero Company overwatch explained

Overwatch sets a directional cone that fires when an enemy moves or acts inside it. Spending more Action Points can increase the number of reaction shots. Using Overwatch ends that Operator's turn, so it is a trade: you give up acting now in exchange for acting on the enemy's turn. **The cone is stricter from Patch 1.1**, which fixed Overwatch triggering on units outside it, and stopped enemies firing back through solid objects at Operators they could not see. **One outlet reports the opposite failure surviving the patch** — a cone that does not fire on an enemy moving through it — and nothing in EA's notes claims to have fixed that.

Confirmed

Confidence: Confirmed
Verified: 14 September 2026
Version: Retail 1.1, 9 September 2026 — official patch notes

It is a cone, not a circle

Overwatch is directional. You choose where it points, which means it can be aimed at a chokepoint, a doorway, or the ground an enemy has to cross — and it can be aimed wrong.

This is what separates Overwatch here from a generic reaction shot: placement is a real decision, and a planner should treat 'has Overwatch' and 'has Overwatch pointed somewhere useful' as different things.

More AP, more shots

Investing more AP can increase the number of reaction shots the cone produces. Using Overwatch ends the Operator's turn regardless, so the question is not whether to spend the AP but how much of a turn the reaction is worth.

An Operator that moves and then goes on Overwatch has fewer points left to invest, which is the tension between repositioning and holding.

Reach costs accuracy

The cone is not a fixed shape. A previewer describes placing it further out and watching the hit chance inside it fall — so cone distance is a dial you set, trading probability for coverage.

That makes 'where do I point this' two questions rather than one. A tight cone near the Operator is a high-percentage trap that an enemy can simply route around. A wide, distant cone denies ground at poor odds. Which one is right depends on whether you are trying to kill something or to stop it arriving.

There is a partial fix. A Scout's attacks mark a target so that range penalties no longer apply to it, which is precisely the penalty a far-placed cone suffers. A Scout and an Overwatch holder are complementary in a way no other pairing found before launch is.

Patch 1.1 made the cone mean what it says

EA list three Overwatch fixes under Patch 1.1. Overwatch was triggering on units outside the targeting cone; an Overwatch shot triggered against an attacker was letting the enemies fire back through solid objects at Operators they could not see; and various other cases had enemies and Operators unintentionally attacked. All three were happening in the retail launch build. The first made Overwatch quietly better than it was designed to be; the second made holding a cone quietly more dangerous, because the return fire ignored the wall you were behind.

The practical consequence is that an August reader's experience of the ability is not a guide to a September one's. If you held wide cones and were rewarded with reaction shots on enemies who skirted the edge, that generosity is gone. Cones now have to contain the ground you want covered. And if you learned that going on Overwatch behind cover somehow got your Operator shot through it, that was the bug rather than the rule.

This does not touch the strategy this page is built on, and it is worth saying why. Every recommendation here — aim at a chokepoint, push an enemy into a prepared cone, ring a droideka so it is watched wherever it rolls — assumes the cone is a real shape that a target has to enter. All of them get *more* reliable when the shape is enforced, because a plan that relies on the enemy being in the cone is unaffected by the cone no longer firing at things outside it.

What does change is the margin for error. A cone placed roughly, on the assumption that the reaction will find something, is now a wasted turn rather than an inefficient one.

What the patch does not claim to have fixed

Every Overwatch line in EA's notes corrects a shot that should not have happened. None of them says anything about a shot that should have happened and did not — and PC Gamer report exactly that failure in their own play after the patch: Overwatch not triggering even when enemies moved through several targeting cones on their turn.

That is one outlet's account, it gives no rate and no reproduction, and this site has not reproduced it. It is recorded here because the alternative is worse. A page that lists the fixes and stops reads as a promise that the cone now fires when it should, and no source has made that promise.

For planning, the distinction is between the mechanic and its execution. Displacement into a prepared cone is still the best-evidenced pairing on this site and nothing about the design has changed. What a September reader should carry is a reserve: a plan whose whole turn depends on one cone firing has a failure mode that a plan with a second cone, or a Sharpshooter's Advantage shot in hand, does not.

Displacement is what makes it reliable

The strongest confirmed use of Overwatch is combining it with displacement. Tel-Rea Vokoss' Force Push and Kabb Uppercut's Uppercut both move enemies, and an enemy pushed into a prepared cone triggers the reaction on your terms rather than waiting for the enemy AI to walk into it.

Previewers demonstrate exactly this — punching an enemy into a waiting cone, and using an area Force push to move several at once. It turns a passive, hope-they-move ability into something you can plan a turn around, and it is the basis of the Force Push and Overwatch squad build.

It is the answer to a droideka

A droideka's ray shield deflects ordinary attacks, and partial damage is wasted because the shield regenerates completely unless broken within a single turn. But the shield is down while the droideka rolls to reposition.

Two previewers independently arrived at the same counter: ring it with cones so that wherever it moves, it moves through watched ground and takes real damage. Against this enemy, coverage beats accuracy — a low-percentage hit through a dropped shield is worth more than a high-percentage hit into a raised one.

There is nothing else to do with a spare point

A previewer went looking for a hunker-down or fortify action and concluded there is none. If an Operator finishes its business with an Action Point left, Overwatch is the only defensive use for it.

That raises Overwatch's floor considerably. It is not only a strategy; it is the default sink for leftover AP, which means most squads will use it whether or not they are built around it.

Confirmed

The rules as officially stated

Overwatch is a directional cone.
It triggers when enemies move or act.
More AP can increase the number of reaction shots.
Using Overwatch ends the Operator's turn.
Placing the cone further out lowers the hit chance inside it.
Enemies can be pushed or knocked into a prepared cone.
A droideka's shield is down while it moves, so cones catch it vulnerable.
There is no hunker-down action, so a spare AP is best spent on Overwatch.
From Patch 1.1, Overwatch no longer triggers on units outside the targeting cone, and enemies no longer fire back through solid objects at Operators they cannot see after an Overwatch shot is triggered against them. EA list both as bug fixes, so both were happening in the retail launch build.
PC Gamer report Overwatch sometimes failing to trigger on enemies moving through its cone after Patch 1.1. EA's notes fix only shots that should not have fired and claim nothing about this failure. One outlet, not reproduced here.

Planning

What this means for squad building

Tag Operators that can hold a cone, and tag the abilities that can push enemies into one.
A squad built entirely on stationary Overwatch will struggle with timed objectives.
Overwatch competes with attacking for the same turn, so an Overwatch-heavy squad trades damage now for damage later.
Pair at least one displacement tool with any Overwatch plan.
Pair a Scout with far-placed cones — its marking removes the range penalty they suffer.
Against shielded enemies, prefer coverage over hit chance when placing cones.
Place the cone over the ground you actually want covered, with a clear line to it. Patch 1.1 removed the slack that made a roughly-aimed cone work anyway.
Discount your own memory of Overwatch from the launch fortnight. A cone that seemed to catch everything was catching more than it should have been.
Do not let a whole turn rest on one cone firing. Until somebody shows the missed-trigger report is wrong or fixed, keep a second cone or an Advantage shot in reserve for the enemy that walks through unshot.

Open questions

Points the shipped game has not yet answered for us, or that need a controlled comparison to state as fact — recorded rather than guessed at.

The cone's angle and range, and how far 'further out' can be pushed.
The exact relationship between AP invested and number of reaction shots.
The exact relationship between cone distance and hit chance.
Whether reaction shots use the same accuracy rules as normal attacks. Patch 1.1 fixed several line-of-sight cases and published no rule, so what the cone now requires is known to be stricter and not known in detail.
Whether enemies can see and avoid the cone.
How often, and under what conditions, a legitimate trigger fails in 1.1. One outlet reports it happening on enemies crossing several cones in one move; a Steam discussion thread titled 'Overwatch not always working' is a lead and not a citation. No rate, no reproduction, and no acknowledgement from EA.

Questions

Common questions

The way these come up in search, answered directly.

How does Overwatch work in Zero Company?: It sets a directional cone that fires when an enemy moves or acts inside it, and it ends the Operator's turn.
Does setting Overwatch end an Operator's turn?: Yes. Overwatch ends that Operator's turn.
Is there a hunker-down action in Zero Company?: No. There is no hunker-down action, which is why a spare Action Point is usually best spent on Overwatch.

Every question, answered with its sources

Related mechanics

Force Push & Overwatch Squad Confirmed
Open in Squad Builder →
Overwatch Trap Theorycraft
Open in Squad Builder →
Hawks critical hit build Theorycraft
Open in Squad Builder →

Sources

Star Wars Zero Company: How Some of the Greatest Minds in Tactics Games are Pushing the Genre, Again
Xbox Wire · Tier 2 — Developer interview · accessed 6 August 2026
Supports: Greg Foertsch and James Brawley on the eight Specializations, Combat Stim + Gunslinger synergy, Advantage, and Specialization changes on authored characters
Lead Zero Company To Victory on August 27
Electronic Arts · Tier 1 — Official · accessed 6 August 2026
Supports: Operator introductions; 3 Action Points per turn; Advantage caps at 10; the eight Specializations; Bonds in the Personnel Facility; Hawks' species options
Is Z-COM our new X-COM? Star Wars Zero Company gameplay deep dive
ChristopherOdd · Tier 3 — Hands-on preview · accessed 11 August 2026
Supports: 2:13–13:51 — Sweeping Salvo at 4 Advantage with three uses per mission; Hawks granting an ally 1 AP for 3 Advantage; Combat Recon granting 1 Advantage per unit scanned; the Grit Talent's stacking invulnerability; Heavy attacks taunting; the droideka ray shield; the Scout's Spotted status; Defense as flat damage reduction
Star Wars Zero Company: turn-based tactics that aren't just for XCOM experts
IGN · Tier 3 — Hands-on preview · accessed 11 August 2026
Supports: 2:15–12:39 — Advantage earned from successful attacks; four difficulty settings; ringing a droideka with Overwatch cones; Bonds granting health and critical damage; changing Hawks' species at the Den; the Bespin guest mission; preview-build defects including shots passing through solid cover
I played Star Wars Zero Company — my honest thoughts
EckhartsLadder · Tier 3 — Hands-on preview · accessed 11 August 2026
Supports: 3:18–12:36 — no hunker-down action, so a spare AP goes to Overwatch; astromechs carrying three utilities and extra uses of each; Trick able to negate some injuries along an upgrade path; twelve galaxy zones; super battle droids telegraphing a rocket one turn ahead; many of the 150+ planets being text-only
STAR WARS Zero Company — Patch 1.1 Notes
Electronic Arts · Tier 1 — Official · accessed 14 September 2026
Supports: Published 9 September 2026, the first post-launch patch; re-read in full on 14 September 2026, when it was still the newest entry on EA's News & Updates page. **Every item below is listed by EA under bug fixes**, which is what makes each one a statement about 1.0 as well as about 1.1. Secondary Specializations: their passive Cross Trainings "now correctly enter the selection pool at Relationship +8", and Secondary Specializations "now count for Specialization-specific Operation requirements and results". Chance-to-Hit: attacks displayed at 100% "can no longer erroneously miss". Scattergun: Tiers II, III and IV "no longer incorrectly use Tier I values". Droid Dismantler: Harmony "is granted only on Droid deaths, not on every enemy death". Tel-Rea: the Ranged Damage Cross Training bonus "is now applied once rather than twice" to her Force attacks, and Critical Damage bonuses "now correctly apply" to them. DC-17m Anti-Armor: it "can now critically hit" and "receives damage bonuses that apply to grenades". Ion Blasters "no longer double Critical Damage". Sweeping Salvo: "enemies outside the targeting cone are no longer hit". A Life of Labor II "can no longer infinitely accumulate bonuses when purchased repeatedly". Immovable: the status "now provides its intended bonuses". Bacta Tank, missed on the first read and added 14 September: "Fixed an issue where the Bacta Tank could be used more than one in a cycle" — EA's wording, typo included; the intended rule is one use per cycle. Overwatch, three lines, quoted verbatim on 14 September because the first pass had paraphrased the first of them too loosely: "Fixed an issue where Overwatch shots triggered against attackers caused the enemies to fire through solid objects at Operators they couldn't see" — an enemy-side line-of-sight failure, not the player's reaction shots passing through walls; "Fixed some instances of Overwatch triggering on a unit outside of the targeting cone"; and "Fixed various Overwatch issues that caused enemies and Operators to be unintentionally attacked". A fourth mentions it in passing: "Fixed a turn ordering issue that caused the Coil Captain to heal a target already slain by Overwatch". **Checked for and absent**: any figure for anything — no Scattergun tier statistics, no Harmony amount, no DC-17m damage, no figure for what Immovable now provides, no Bacta Tank cost. Also absent: any fix for Overwatch *failing* to trigger. Every Overwatch line corrects a shot that should not have happened, and none claims a shot that should have happened now does.
Star Wars Zero Company gets much-needed first patch so you won't miss shots with a 100% chance to hit any more
PC Gamer · Tier 3 — Retail review · accessed 14 September 2026
Supports: Registered for one claim, and it is the one no patch note can make about itself: what the patch did *not* fix. The outlet's own playthrough had Overwatch failing to fire — in the passage as it surfaced through search, the main bug experienced was Overwatch not triggering even when enemies jog through multiple targeting cones on their turn, and that does not seem to have been addressed, although the bugs where Overwatch triggered on units outside the cone or behind solid objects have. The article body could not be retrieved by this site — pcgamer.com returns a membership interstitial to an automated fetch, as it did for `retail-pcgamer-talents` — so the byline and the exact build tested are unrecorded, and the claim is filed as one outlet's account rather than corroborated. It is consistent with EA's notes, which fix only shots that should not have happened, and it is why every Overwatch record here carries a reliability caveat rather than reading the patch as a guarantee. **Checked for and absent**: any statement of how often the failure occurs, any reproduction steps, and any acknowledgement from EA.

Apply it

The Squad Builder checks squads against this mechanic and warns you when a composition ignores it.

Open the Squad Builder

Editor’s note

Updated 2026-09-14, twice over. First, a correction to the 2026-09-10 pass: EA's through-walls line was relayed here as reaction shots firing through solid objects, and re-read verbatim it says something narrower — that an Overwatch shot triggered against an attacker caused *the enemies* to fire through solid objects at Operators they could not see. That is an enemy-side line-of-sight failure, and it means the launch build's Overwatch was not only more generous than designed but more dangerous to hold. The cone-edge fix was relayed correctly. Second, the caveat: PC Gamer report Overwatch failing to fire on enemies moving through its cone after the patch, and nothing in EA's notes addresses that direction of failure. It is one outlet's account and it is filed as such — a retail-reported observation on an official record, with its own unknown naming what would settle it. The section it earned is deliberately about execution rather than design, because the design is unchanged and the synergies built on it stand. Updated 2026-09-10 for Patch 1.1's cone and line-of-sight fixes, and the pleasant finding is that nothing on this page had to be retracted. Every recommendation here assumed the cone was a real shape enemies had to enter, which is what the patch enforces — so the advice was right about the design and the launch build was wrong about the game. The part worth writing down is the reader's side of it. Somebody who played the launch fortnight learned an Overwatch that fired off the edge of its own cone and drew return fire through walls, and they learned it from the game rather than from a source anyone can cite. That is the hardest kind of stale information to correct, because it does not live in any article — which is why the new section addresses their experience directly rather than only stating the fix. The displacement-into-Overwatch pattern is unaffected and stays this site's best-evidenced synergy: a pushed enemy lands inside the cone, which is exactly the case the patch tightened around. The cone-distance trade-off, the droideka counter and the absence of a fortify action are all preview-reported and change how the mechanic should be played, not what it is. The droideka counter is the strongest piece of specific counterplay evidence on the site: two previewers found it independently.