- StarCraft Dominion units are not yet a confirmed playable roster.
- Terran forces offer the clearest Dominion-related unit framework.
- Zerg and Protoss units should be treated as setting context unless officially announced.
- Battlefield roles help organize units without inventing damage or upgrade statistics.
- Status labels separate established StarCraft lore from future project speculation.
StarCraft Dominion Units: What Is Confirmed
StarCraft Dominion units should currently be understood as a lore and reference category, not a finalized in-game roster. Public descriptions of the project have not established specific playable units, unit statistics, upgrade paths, mission availability, or faction selection rules. This guide therefore uses established StarCraft roles to organize the subject without presenting unannounced content as confirmed.
The most reliable starting point is the Terran Dominion. Its military identity includes infantry, covert operatives, armored vehicles, air units, and capital ships. These categories are useful for understanding how Dominion forces may be represented in a future action-focused StarCraft experience, but they do not confirm that every listed unit will appear in the project.
| Status | Meaning | How to use it |
|---|---|---|
| Established lore | A unit or role exists in StarCraft canon | Use for background and faction context |
| Dominion-associated | Connected to Terran Dominion forces or military structure | Use as a likely reference point, not a confirmed roster entry |
| Project unconfirmed | No official unit announcement is available | Do not assign stats, unlocks, or rankings |
| Community speculation | A possible interpretation based on the setting | Label clearly and avoid factual claims |
For canonical background, consult the official StarCraft story overview and Blizzard’s StarCraft information hub.
Do not treat familiar StarCraft units as confirmed StarCraft Dominion units until Blizzard publishes an official roster, gameplay demonstration, or unit-focused announcement.
Terran Dominion Unit Roles
Terran forces provide the strongest foundation for a Dominion unit guide because the Terran Dominion is a major human power in the Koprulu Sector. Its military structure covers standard soldiers, elite specialists, mechanized support, and large-scale fleet assets.
The table below describes established battlefield functions rather than project-specific gameplay values.
| Unit or category | Faction context | Battlefield role | Status for Dominion |
|---|---|---|---|
| Marine | Terran military | General-purpose infantry and sustained ranged fire | Established lore; project appearance unconfirmed |
| Ghost | Terran Dominion and covert programs | Stealth, reconnaissance, and precision attacks | Strong Dominion association; project appearance unconfirmed |
| Siege Tank | Terran armored forces | Long-range fire support and area denial | Established lore; project appearance unconfirmed |
| Hellion | Terran mechanized forces | Fast attacks and anti-infantry pressure | Established lore; project appearance unconfirmed |
| Battlecruiser | Terran fleet | Capital-ship support and strategic presence | Established lore; project appearance unconfirmed |
| Worker units | Terran colonies and infrastructure | Construction, logistics, and resource operations | Established lore; project role unconfirmed |
Infantry and Specialist Forces
Marines represent the standard Terran combat profile: disciplined infantry using powered armor and ballistic weapons. Their importance comes from flexibility rather than a single specialized function. Ghosts occupy a different position, emphasizing stealth, intelligence work, and high-value target elimination.
A future action game could use these distinctions to create different combat identities, but no official loadout, class, or playable-character system has been confirmed. Avoid assigning marine health values, Ghost abilities, or weapon tiers until reliable product information becomes available.
Mechanized and Heavy Support
Siege Tanks and Hellions demonstrate how Terran forces combine mobility with heavy firepower. Hellions are associated with rapid movement and anti-personnel attacks, while Siege Tanks are designed for defensive lines, fortified positions, and long-range support.
These roles are useful when building a lore-based unit database. They should not be converted into a Dominion damage ranking or tier list without hands-on testing and official mechanics.
Aerospace Assets
Battlecruisers represent the scale of Dominion military power beyond ground operations. They function as fleet assets and symbols of Terran strategic reach. Their inclusion in a setting overview can explain the relationship between ground forces, planetary operations, and orbital command.
When unit statistics are unavailable, compare units by purpose: infantry, stealth, mobility, heavy support, or fleet command. This keeps the guide useful without inventing numbers.
Zerg and Protoss Units in the Dominion Setting
The Zerg and Protoss are essential to StarCraft’s wider conflict, but their relationship to a future Dominion-focused project remains unconfirmed. They should be presented as major factions and potential encounter groups rather than guaranteed playable unit rosters.
Terran Dominion
- Military organization
- Infantry, armor, covert forces, and fleets
- Strongest connection to the Dominion theme
- Project roster remains unconfirmed
Zerg Swarm
- Biological adaptation
- Mass assaults and rapidly changing threats
- Recurring enemy of Terran powers
- Specific encounter types remain undisclosed
Protoss
- Advanced technology
- Psionic abilities and specialized warriors
- Major power in sector-wide conflicts
- Playable or hostile role remains unconfirmed
Zerg Unit Categories
Zerg forces are commonly understood through biological roles. Some units pressure targets through numbers, others provide mobility, air support, burrowing, or heavy assault capabilities. This makes the Swarm suitable for encounter-based analysis, but not for a confirmed Dominion unit list.
A useful database structure can group Zerg entries by:
- Ground assault
- Fast harassment
- Air support
- Siege or area pressure
- Massive biological threats
- Support and detection
The exact creatures, enemy behaviors, and mission appearances should remain marked as pending until official materials clarify them.
Protoss Unit Categories
Protoss forces typically emphasize advanced technology, shields, mobility, and specialized combat functions. Their units can be grouped into frontline warriors, ranged support, aerial forces, psionic specialists, and high-value command assets.
These categories help readers understand faction identity. They do not establish which Protoss units appear in Dominion-related content, whether they are playable, or how their abilities would operate in a shooter environment.
| Faction | Core identity | Useful reference roles | Current interpretation |
|---|---|---|---|
| Terran Dominion | Organized human military power | Infantry, Ghosts, vehicles, fleet assets | Primary Dominion context |
| Zerg Swarm | Adaptive biological threat | Assault, mobility, air, siege, support | Likely setting context only |
| Protoss | Advanced psionic civilization | Warriors, specialists, air units, technology | Likely setting context only |
| Other Terran powers | Political and military rivals | Militia, intelligence, frontier forces | Requires story confirmation |
A faction’s presence in StarCraft lore does not automatically confirm playable units, enemy encounters, or mission content in StarCraft Dominion.
How to Build a Reliable Unit Database
A useful unit database should distinguish what the StarCraft universe establishes from what the Dominion project confirms. Follow the process below whenever a new unit is added to the wiki.
Record the canonical identity
Start with the unit’s established faction, role, and known StarCraft association. Avoid adding project-specific claims at this stage.
Assign a battlefield category
Place the unit under infantry, specialist, vehicle, air, support, siege, or capital-ship categories. Use role language instead of unverified damage values.
Separate lore from project data
Create separate fields for established lore, Dominion association, and official project confirmation. This prevents background information from being mistaken for gameplay documentation.
Add only verified mechanics
Record weapons, abilities, upgrades, health, armor, and unlock requirements only when an official source or reliable hands-on build confirms them.
Review status labels
Mark each entry as confirmed, established lore, reported, speculative, or pending. Update the label whenever new official information becomes available.
| Database field | Recommended entry | Avoid |
|---|---|---|
| Unit name | Official or canonical name | Fan-created replacement names |
| Faction | Terran, Zerg, Protoss, or other confirmed group | Assumed playable faction |
| Role | Infantry, stealth, armor, air, support | Unverified class title |
| Lore status | Established, associated, or speculative | Presenting guesses as fact |
| Project status | Confirmed, unannounced, or pending | Invented release-build details |
| Mechanics | Officially documented abilities only | Made-up stats or cooldowns |
A consistent structure also improves search performance. Readers looking for “Dominion Marines,” “Ghost units,” or “Terran vehicles” should be able to find the same fields on every page.
A unit page is ready for publication when its faction, role, and evidence status are clear. Missing gameplay data should be labeled pending rather than filled with estimates.
Unit Research Checklist and Comparison Framework
Use this checklist when expanding the StarCraft Dominion units section of the wiki. It is designed for both canonical lore pages and future gameplay updates.
Unit Page Review:
- Confirm the unit name and faction association
- Describe the battlefield role without inventing statistics
- Separate established lore from Dominion project information
- Mark playable, enemy, or unconfirmed status clearly
- Add official references when new information is published
Recommended Comparison Categories
The most useful comparison is not always raw power. Until official mechanics are published, readers benefit more from role-based comparisons.
| Comparison category | Key question | Suitable examples |
|---|---|---|
| Range | Does the unit operate close, mid, or long range? | Marine, Ghost, Siege Tank |
| Mobility | Does it advance quickly or hold a position? | Hellion, infantry, armored unit |
| Specialization | Does it focus on stealth, support, or precision? | Ghost, specialist unit |
| Scale | Is it a soldier, vehicle, or fleet asset? | Marine, Siege Tank, Battlecruiser |
| Faction identity | What does the unit communicate about its faction? | Terran technology, Zerg biology, Protoss psionics |
This framework supports future rankings without publishing an unsupported tier list. Once official combat data exists, the wiki can add survivability, damage, utility, mobility, and mission suitability as separate fields.
Q: Are StarCraft Dominion units officially confirmed?
No finalized Dominion roster has been publicly confirmed. Established StarCraft units can explain the setting, but their appearance, role, and availability in the project remain unannounced unless Blizzard provides direct confirmation.
Q: Which faction has the strongest connection to Dominion units?
The Terran Dominion has the clearest connection because it is a major human military and political power in the StarCraft universe. Terran infantry, Ghosts, vehicles, and fleet assets are useful reference categories, not confirmed project content.
Q: Can Zerg and Protoss units be listed in the wiki?
Yes, they can be listed as established StarCraft factions and possible setting context. Each page should clearly state whether the unit is confirmed for Dominion, associated with general lore, or still unannounced.
Q: Should the wiki publish a StarCraft Dominion tier list now?
A gameplay tier list should wait for an official roster and practical testing. Before that information exists, use role-based comparisons and status labels instead of S-tier rankings or invented performance data.
Do not label any unit S-tier, best, meta, or weakest until the official roster, mechanics, encounter design, and practical testing support that conclusion.