Star Wars Zero Company Characters Guide

Hawks and the player role

PlayStation describes Hawks as a former Republic officer who leads Zero Company, an unconventional group of professionals for hire from across the galaxy. EA also says Hawks’ appearance and combat specialization can be customized.

Hawks is the player-facing anchor for the campaign. This guide keeps the protagonist role separate from the authored companions and custom operators who fill out the squad.

Authored operator roster

The names below are listed by the Zero Command community roster and discussed in PC Gamer’s hands-on guide. Role labels are current pre-release reference points, not a promise that every ability or class restriction will be unchanged at launch.

• Trick: human clone and soldier; Hawks’ Clone Wars companion.
• Tel-Rea Vokoss: Tognath Jedi Padawan; an exotic Jedi specialization.
• Cly Kullervo: Mandalorian human and gunslinger; an exotic Mandalorian specialization.
• Luco Bronc: Umbaran sharpshooter and former Umbaran soldier.
• Kabb Uppercut: Felshi mercenary and cybernetically enhanced boxer.
• Jae Mordant: human operator and ore-baroness of Luunata.
• M-3VO: bipedal utility droid serving as pilot and medic for the Caisson.

The Den and custom operators

EA describes a squad made from a wide range of archetypes, including scoundrels, astromechs, and a Jedi, while PC Gamer reports that players return to the Den to talk with companions and manage the wider team. Custom operators can extend the roster beyond the authored story characters.

The Den is therefore more than a mission launch screen in the current reporting: it is the social and preparation space where the squad’s equipment, relationships, and next operation come together.

Permadeath and recruitment boundaries

PC Gamer’s hands-on reporting says story squadmates and custom mercenaries share permadeath rules, while the Zero Command roster marks Hawks as immune to permadeath. Treat that as pre-release reporting until the final build and official documentation confirm every exception.

• Do not assume every named character is available at the start.
• Do not publish a guaranteed recruitment order without release-build evidence.
• Keep authored operators, custom operators, and base personnel as separate categories.

Character guide standard

A future character entry should include the in-game name, species, role, recruitment or availability condition, starting class, signature ability, customization limits, and a version label. This prevents a hands-on observation from becoming an unsupported permanent roster fact.