Patch Notes

Star Wars Zero Company Patch 1.1: Fixes & Changes

Star Wars Zero Company Patch 1.1 fixes crashes, Beskar saves, 100% hit misses, Overwatch bugs, and adds important PC performance guidance for players.

Field guide ·

Star Wars Zero Company Patch 1.1 released on September 9, 2026. It is the first major post-launch update focused on stability, save safety, tactical combat bugs, progression logic, and PC performance. The most important changes for active players are fixes for crashes, temporary Beskar save disappearance, save corruption after forced shutdowns, 100% hit-chance attacks missing, several Overwatch problems, and multiple combat calculations that were producing incorrect results.

Jump to the Patch 1.2 release update.

Patch 1.2 is live: campaign options and changes

Checked October 16, 2026: EA's official Patch 1.2 notes, dated October 15, 2026, confirm that the update is live. This replaces the earlier announcement-only status; the September 9 Patch 1.1 summary below remains a record of that version.

Campaign Modifiers are selected when starting a new campaign, under Difficulty Settings → Additional Campaign Options. They work on any difficulty, and selected modifiers activate after the tutorial. These optional rules let you adjust how a fresh campaign plays; they are separate from the update's general balance changes.

AreaWhat Patch 1.2 changes
Optional campaign rulesConfigurable injury and death rules, progression, Advantage, Assist Shots, and other restrictions for a new campaign.
General balanceCly's Combat Jump is limited to one use per turn; Electroweb Dart to three. Recruiting an Operator now costs 100 Credits.
Selected fixesEA lists Overwatch targeting and interface fixes, missing Operation rewards or outcomes, and epilogue progression fixes.

These are publisher-reported changes. Consult the full notes for individual options and fixes before choosing rules or reassessing a build.

What changed in Patch 1.1?

Patch 1.1 is primarily a repair and reliability update rather than a content expansion. EA grouped the update around performance and stability, cinematics and conversations, customization, the Databank, encounters, strategy-layer systems, tactical combat, and a small set of feature adjustments.

For most players, the practical takeaway is simple: campaigns should be safer to continue, combat outcomes should match the numbers shown on screen more consistently, and several systems that depend on Specializations or character state now behave closer to their intended rules.

The biggest stability and save fixes

The update addresses multiple crash sources and visual stutters. It also fixes a serious Beskar-mode issue where saves could appear to be temporarily deleted, plus a separate Beskar crash problem. EA additionally fixed save corruption that could occur when the game was closed suddenly or forcibly while data was being written.

Preorder and Deluxe Edition owners should also benefit from a fix for missing bonus items. The patch updates the minimum suggested Nvidia and AMD driver versions and improves the wording of the driver warning shown to players whose graphics drivers are behind the recommended versions.

If your campaign had been affected by a missing Beskar save or repeated crashes, Patch 1.1 is the first version that specifically targets those launch-period problems. Keeping a backup of important saves is still sensible before major updates or troubleshooting changes.

100% hit chance should now behave correctly

One of the most visible tactical bugs involved attacks displaying a 100% chance to hit and still missing. Patch 1.1 fixes that issue.

The update also corrects several combat-value problems. Higher-tier Scatterguns were incorrectly using Tier 1 values, Ion Blasters could apply too much Critical Damage, and some of Tel-Rea's Force attacks displayed or applied damage bonuses incorrectly. The DC-17m Anti-Armor attack also received a fix so its damage can interact correctly with Critical Hits and bonuses that are supposed to apply to grenade-style damage.

For players comparing builds, this matters because launch-week impressions based on bugged weapon or ability values may no longer reflect Patch 1.1 behavior.

Overwatch received several fixes

Overwatch is another major focus of the tactical section. Patch 1.1 fixes situations where attacks could trigger against units outside the intended cone, where the wrong enemy or Operator could be attacked, and where Overwatch interactions contributed to incorrect turn ordering.

The patch also resolves a case where an enemy could fire through solid objects after an Overwatch trigger and a case where a Coil Captain attempted to heal a target that had already been killed by Overwatch.

Players who avoided Overwatch because its launch behavior felt unreliable should retest their setups after updating. Placement, line of sight, and cone coverage still matter, but several behaviors that looked like rule inconsistencies were confirmed as bugs and targeted in this update.

If enemies are still crossing a valid cone without any reaction attack beginning, see our Overwatch not working troubleshooting guide. Patch 1.1 fixes several specific Overwatch problems, but it does not explicitly claim that every no-trigger case is resolved.

Secondary Specializations now count correctly

Patch 1.1 also changes progression-related behavior. Secondary Specializations now correctly contribute their passive Cross Trainings to the available selection pool at Relationship level +8.

They also now count when Operations check Specialization-specific requirements and outcomes. This is important for hybrid builds after the Secondary Specialization system unlocks, because the second role is no longer ignored by those checks in the situations covered by the fix.

If you are planning around two-class combinations, re-evaluate Operation options and Relationship progression after installing the patch instead of assuming the launch behavior is still current.

Other tactical fixes worth knowing

The patch corrects targeting and UI problems across several abilities and combat states. Rocket Strike and the DC-17m Anti-Armor shot received targeting improvements, the Astromech Enhanced Scanners controller issue was fixed, and the Rally interface now appears correctly when targeting from a Move preview.

Several status and targeting problems were also addressed, including the Immovable status failing to provide its intended benefit, Sweeping Salvo affecting units outside its cone, and an A Life of Labor upgrade repeatedly accumulating bonuses when repurchased. Camera drift during target selection was reduced as well.

These changes do not create a new balance tier list by themselves, but they can change how reliable specific tools feel in real encounters.

Tel-Rea hero mission and strategy-layer fixes

Patch 1.1 fixes the final battle of Tel-Rea's hero mission so it no longer ends incorrectly when the survival counter reaches its final turn. The mission should now resolve after the intended enemy turn.

On the strategy layer, the Bacta Tank can no longer be used more often than intended in a cycle, an unnecessary autosave generated when loading has been removed, and a Medbay tutorial softlock was fixed. The update also resolves a progression block related to moving between squad selection and inspection mode.

Databank editing received additional protection against character data corruption and duplicate-name problems that could break customization for an affected Operator.

PC performance recommendation for older Nvidia GPUs

EA included a specific performance recommendation for players using supported Nvidia GTX 10-series or RTX 20-series GPUs. If performance is poor, open Options → Graphics, find Environment Geometry Detail, and switch it Off.

EA says this setting can reduce geometry-processing overhead on those architectures and may improve or stabilize frame rates. This is not presented as a universal fix for every PC configuration, so players on other GPUs should avoid assuming that the same setting is automatically the best choice for their system.

The update also changes the suggested graphics-driver baseline for Nvidia and AMD hardware, so checking for a current game-ready driver is a sensible first troubleshooting step after installing Patch 1.1.

What should you do after installing Patch 1.1?

First, load the campaign you were using before the update and confirm that your saves, bonus items, Operators, and mission state appear correctly. If you previously encountered combat oddities, test those situations again before relying on old workarounds.

Second, revisit builds that depended on Scatterguns, Ion Blasters, Tel-Rea Force attacks, Overwatch, Secondary Specializations, or the DC-17m. Several launch behaviors in those areas were explicitly corrected, so old advice may be outdated even if the underlying build concept is still strong.

Finally, PC players experiencing low frame rates should update their GPU drivers and test the Environment Geometry Detail setting when their hardware matches EA's recommendation.

Patch 1.1 release date

Star Wars Zero Company Patch 1.1 was published on September 9, 2026. This page was reviewed on September 11, 2026 against EA's official patch notes.

Sources