Quick answer
Before treating permadeath as a campaign rule, inspect the current release client’s difficulty and save screens. Search demand is real, but the official Steam description does not document whether permadeath exists, whether it can be disabled or how saves behave. Preserve the current setting and record its exact label before making a campaign decision.
Check the failure boundary first
Use this checklist before starting a serious run:
- Read the current difficulty and campaign setup text.
- Note whether the client shows a permadeath, ironman or similar option.
- Check what the save screen says about manual, automatic or mission saves.
- Capture the setting and campaign state in your own notes.
- Do not delete an existing save to test a theory.
If the client does not state a rule clearly, keep the answer bounded. A community comment can point to a setting worth checking, but it cannot establish a universal rule for every platform or mode.
Reduce the cost of learning
For a first campaign, use Difficulty Settings to choose a learning boundary. Use Squad Planning to make one composition experiment at a time. When a mission fails, record whether the failure came from the objective, position, ability sequence or recovery decision before restarting everything.
This is more useful than treating a single loss as proof that one class, difficulty or squad is wrong.
What this page does not claim
The current public source review does not establish a “turn off permadeath” control, save slot behavior, ironman rules, campaign rollback or a safe file-edit workaround. Do not publish a settings table until a current-client evidence capture supports it.
Sources
- STAR WARS Zero Company on Steam — official campaign and tactics context; checked September 2, 2026.
- Steam reviews — player questions that led to this task; sampled September 2, 2026.
Last verified: September 2, 2026. Recheck campaign setup and save behavior in the current release client.