The Den is where a recoverable combat mistake can become a campaign problem. A Tactical Mission advances the Cycle; Operations compete for Intel; an Injury competes for Credits and treatment time; a new recruit competes for roster space; a Bond can open permanent Cross Training benefits. Those decisions share resources even when their menus do not.
This guide maps the current management rules before Star Wars Zero Company launches on August 27, 2026. It uses official EA and Bit Reactor material available through August 17. Exact costs, reward rolls, upgrade prerequisites, and story gates remain shipping-client checks, so the goal is a reliable decision method rather than a fabricated optimal build order.
Put every Cycle on one decision board
The Holotable shows the Operations and Tactical Missions available in the current Cycle. Operations are short strategic assignments rather than turn-based battles. They cost Intel and can grant Credits, Weapon Mods, Utilities, information, or additional opportunities. Some include choices that affect Bonds or enemy development. Tactical Missions are ground-combat deployments that can award Intel, Credits, Focus Points, Weapon Mods, Utilities, Zone Influence, and other rewards.
The sequencing rule matters more than the reward list: Bit Reactor says a Cycle ends with a Tactical Mission selection, and the gameplay deep dive says completion advances to the next Cycle. Both Operations and Tactical Missions can expire. Story-critical missions eventually become obligatory. That means a Tactical Mission is not merely “the next fight”; it is the button that may remove unfinished choices and advance construction or treatment.
Before launching, sort the board into three columns:
- Expires if I advance: Operations, side missions, Contacts, or Influence opportunities whose current timers would close.
- Changes my next deployment: an Injury treatment, weapon purchase, Utility transfer, recruit, Focus upgrade, or facility completion.
- Can wait safely: customization and conversations with no visible timing warning, plus any upgrade whose result cannot affect the selected mission.
Resolve the first column deliberately, inspect the second, then launch. If the interface does not reveal an expiry or completion timer, save and record the before-and-after Cycle rather than assuming the opportunity is permanent.
Keep six resources in separate ledgers
Several management systems feed one another, but the currencies are not interchangeable. A compact ledger prevents a tempting reward from hiding its real cost.
| Ledger | Confirmed inflow | Confirmed use | Decision warning |
|---|---|---|---|
| Intel | Tactical Missions; some story exploration can also grant Intel | Paying for Operations at the Holotable | An Operation can expire, but spending all Intel may close a later option in the same Cycle |
| Credits | Operations, Tactical Missions, and Den treasury rewards | Facilities, Black Market equipment, and Injury treatment | A purchase can compete directly with keeping a veteran deployable |
| Focus Points | Tactical Mission rewards and primarily Bond increases | Talents, Abilities, and Passives in an Operator’s Focus Tree | Do not spend from a pre-release build order before reading the current node and prerequisite |
| Zone Influence | Operations and Tactical Missions in the relevant planetary region | Unlocking Zone Rewards | Compare an expiring local reward with progress toward the next threshold |
| Contacts | Named Zone Rewards | Large Influence gains | Confirm whether a Contact is consumed and which zone receives the gain |
| Build Slots and Cycles | Additional slots unlock over time | Facility and roster-wide upgrades | Construction takes at least one Cycle, so the slot has an opportunity cost even after Credits are paid |
Advantage does not belong on this Den ledger. It is a combat pool, capped at 10, that is earned by landing hits and spent on powerful actions. Keeping it separate stops a launch guide from inventing a conversion between strategic and tactical resources.
Recruit for the missing profile, not a species bonus
Zero Company divides the roster into Authored and Custom Operators. Authored Operators join through the story. The revealed group includes Trick, Jae Mordant, Tel-Rea Vokoss, Luco Bronc, Cly Kullervo, and Kabb Uppercut, with Hawks as leader. Custom Operators are recruited from a pool and can be customized in appearance, clothing, voice, name, and other fields.
The current operator limit is 20, while a new campaign starts with capacity for seven. Den upgrades and story progression increase that capacity as Authored Operators join. Each Cycle presents Custom Operator choices, and the recruitment pool can be refreshed at will. Players can also create a custom pool from which recruits appear. “Refresh at will” does not prove that hiring is free or that every requested profile appears immediately; check the launch UI for cost, limit, and generation rules.
A generated recruit arrives with a Name, Talent, Primary Specialization, weapon type, and backstory, all described as adjustable after recruitment. Evaluate the card in this order:
- Missing job: identify the mission or recovery problem the roster cannot currently solve.
- Talent and authored kit: find the least replaceable contribution before comparing cosmetics.
- Weapon and Specialization: check whether the initial combination can perform that job within its real AP and range.
- Bond opportunity: decide which existing Operator can train with the recruit without breaking another important pair.
- Capacity cost: reserve room for upcoming Authored Operators or a specialist the current pool cannot supply.
Species should not move ahead of those checks. Bit Reactor explicitly says species and faction do not confer weapon proficiency bonuses; the team did not want optimization to force a particular identity. Choose the appearance you want, then build effectiveness through the actual Talent, Specialization, equipment, Focus Tree, and Bonds.
Use the confirmed species lists without inventing traits
Hawks and Custom Operators do not have the same published list. The Customization Facility currently names these options:
| Character type | Officially listed examples and options | What is not established |
|---|---|---|
| Hawks | Devaronian, Human, Mirialan, Togruta, Twi’lek, Zabrak | Mechanical species traits, exclusive weapons, or a permanent choice lock |
| Custom Operators | Devaronian, Human, Mirialan, Neimoidian, Ovissian, Rodian, Togruta, Twi’lek, Weequay, Zabrak | A power ranking, proficiency differences, or identical access for every authored character |
The official deep dive says Hawks and Custom Operators can change species at the Customization Facility. The community Q&A also says most cutscenes render in real time so customized characters remain visible. Verify any cost, story restriction, and save behavior before treating appearance changes as unlimited.
Clone Troopers unlock after a point in the story, and official answers say a full clone team is then possible. Astromechs arrive early enough that a full astromech group can be built, while the Den deep dive ties Custom Astromech recruitment to a Droid Bay upgrade. Those are recruitment gates, not proof of four universal “exotic classes.” Keep the story unlock, facility requirement, and Specialization system as separate client checks.
Manage Bonds as pairs with two different payoffs
Every pair begins with a relationship that is usually neutral or negative. Operations, Tactical Missions, and Calling for Backup can raise Bonds. Dilemmas give each Operator an opinion, and Hawks’s decision can alter a relationship. Bond growth matters twice: Focus Points are earned primarily from increasing Bonds, and the paired Operators can Cross Train for permanent combat-stat bonuses. At maximum Bond, the pair can unlock a special Cross Training Passive.
That creates a common trap: repeatedly deploying a favorite group can strengthen several pairs but leave the reserve roster without partners or Focus progression. Permadeath and injuries make an isolated reserve especially dangerous. Use a pair sheet rather than one generic “team chemistry” score:
- Current level and direction: neutral, negative, improving, or at a visible threshold.
- Cross Training already chosen: the exact permanent bonus and which half benefits.
- Maximum-Bond target: the Passive promised by the current panel, not one copied from a preview.
- Shared deployment job: why the pair belongs in the same mission beyond gaining relationship points.
- Replacement bridge: one third Operator who can work with either member when the other is injured.
Advance a pair when the mission also suits them. An easy Operation may be a safer Bond opportunity than forcing an under-equipped partner into a Critical Tactical Mission. Conversely, do not spend scarce Intel on a relationship choice without comparing its immediate reward, expiry, and effect on the coming Cycle.
Distinguish Downed, Injured, dead, and failed
When an Operator loses all Health, that Operator is Downed and takes an Injury. A Downed unit cannot act but can be Rallied by an ally. Injuries reduce combat stats. On standard difficulty, accumulating three Injuries causes permanent death. Permanent loss starts active, although the campaign settings let the player switch it off. Hawks follows a different failure rule: if Hawks dies in combat, the mission fails and must be restarted.
The Medbay turns those states into a schedule. A standard bed takes one Cycle to heal an Injury; a Bacta Tank heals immediately. Treatment costs Credits. Before paying or advancing time, ask:
- How many Injuries does the Operator have, and what exact stat penalty is active?
- Will the selected Tactical Mission advance the standard bed to completion before the Operator is needed?
- Can another Operator perform the same mission job without breaking a crucial Bond pair?
- Does instant Bacta recovery preserve an expiring opportunity that is worth more than its Credit cost?
- Is permadeath actually enabled for this save and difficulty configuration?
Do not send a two-Injury veteran merely because a Medic is present. The Medic specializes in healing and Injury prevention, but the final ability panel must establish the timing, range, cost, and whether it can stop the third Injury in that situation. The campaign rule is state prevention; the class description is not a guarantee.
Make the Armory solve a named deployment problem
The four published weapon types are Longarm, Repeater, Rifle, and Pistol. Each weapon has Modification Slots that can grow during the campaign. Mods alter stats or add effects. Utilities grant combat abilities such as Impact Bombs and Concussion Grenades, and a Specialization determines whether an Operator can carry one or more. The Black Market sells Weapon Mods and Utilities for Credits.
Do not buy a higher number without tying it to a failed check. A weapon or mod should solve one of these:
- the Operator cannot contribute at the range required by the mission;
- the attack consumes too much AP to preserve movement or an exit;
- the squad lacks a way to remove cover, hit an enemy type, or control a cluster;
- the current weapon cannot convert a teammate’s opening into a removal;
- a Utility would prevent a more expensive Injury treatment or missed objective.
Bit Reactor advises having Ion weapons against Separatist droids. Verify whether “Ion” is a weapon, mod, Utility, effect, or several categories before buying around the word. The Armory screen, not a pre-launch class page, decides which Operators can equip the answer.
Queue infrastructure against the next two Cycles
The Upgrade Facility builds Den infrastructure and roster-wide improvements. An official example is a Droid Bay that permits recruitment of Astromech Custom Operators. Other upgrades can raise weapon stats across the roster. Construction takes at least one Cycle and occupies a Build Slot; additional Build Slots unlock later.
Evaluate a project across two horizons:
| Question | Build now when | Delay when |
|---|---|---|
| Does it unlock a missing roster category? | The next mission set exposes a job the current seven cannot cover | Capacity or Credits prevent using the new recruit after completion |
| Does it improve every Operator? | Several active weapon users receive the displayed benefit | The bonus misses the weapons or roles in the next deployment |
| Will it finish before the need? | The required number of Tactical Mission advances is visible and acceptable | An expiring Critical Mission arrives first |
| What else needs the slot? | The second-best project has no immediate effect | A Medbay, capacity, or recruitment gate solves the sharper campaign risk |
Do not call a universal first upgrade before reading the launch tree. Starting difficulty, early authored recruits, random Custom Operator pool, injuries, and current mission rewards can change which bottleneck appears first.
Close the Den only after a twelve-point readback
- Record the current Cycle and every visible expiry.
- Mark which story mission becomes obligatory and when.
- Compare remaining Intel with all Operations worth preserving.
- Read the exact rewards and Zone Influence destination for the chosen action.
- Check all Operators for Injury count, stat penalties, and treatment timers.
- Confirm the next squad fits the standard four-seat limit and includes Hawks if the mission requires Hawks.
- Inspect each seat’s Talent, Specialization, weapon, Utility, and mission job.
- Review the Bonds created by that deployment and the Cross Training already selected.
- Spend Focus Points only after checking the current node, prerequisite, and affected ability.
- Compare Black Market purchases with treatment and construction costs.
- Confirm every active Build Slot and the Cycle in which its project should finish.
- Save the roster, resource, mission, and version state before launching.
Leave exact recruit prices, refresh costs, random pool odds, full Focus Trees, all Bond thresholds, optimal Dilemma answers, story recruitment order, upgrade prerequisites, treatment prices, and final mission timers out of the plan until the client reports them. The current official material defines the decisions; it does not supply those numbers.
Sources & credits
The management rules—Cycle flow, Holotable rewards, Personnel, Bonds, recruitment, equipment, construction, Medbay states, and species choices—come from EA and Bit Reactor’s Den and gameplay overview. Roster limits, Hawks’s deployment rule, the species-proficiency boundary, permanent-loss setting, unit unlock timing, and mission structure were confirmed in the developer question-and-answer article. The Operators hub controls authored-character identities. Steam AppID 2075800 provided release metadata and the three untouched 1920×1080 JPEGs. Community character, species, and beginner pages remained audit references and did not supply missing costs.