What this page is, and what it is not
A reveal cinematic is the most watched and least reliable artefact of a game announcement. It is built to make you feel something, and it is finished long before the game is. Reading it well means separating three things: what was officially stated, what the developers say is in it, and what a viewer infers.
This is not a frame-by-frame breakdown with timestamps. We have not published one, and we would rather say so than manufacture a list of shots we cannot stand behind. Everything below is either an official statement or a developer statement, each attributed. Where that leaves a gap, the gap stays visible.
The reveal was a cinematic called “Dominion”
STARCRAFT was introduced during the BlizzCon opening ceremony on 12 September 2026 with a cinematic titled “Dominion”. [E] [A]
That title belongs to the cinematic. It is not a confirmed subtitle for the game, which so far carries no number and no subtitle at all. [A] This is the single most common way an announcement gets misreported: a piece of marketing gets a name, the name gets repeated, and within a week it is being written as though it were on the box.
The word does carry weight in this universe — the Terran Dominion is a long-running power in the setting — but a resonant name is an invitation to speculate, not evidence of a plot. Until Blizzard attaches it to the game itself, we write “the cinematic called Dominion”, never “StarCraft: Dominion”.
No gameplay was shown, and that shapes everything else
The public reveal contained no playable gameplay sequence, and Blizzard has since explained that decision. [B] It is worth sitting with what that means.
Every mechanic currently being discussed — the third-person camera, the marine armour, the open world, the progression, the feel of combat — comes from interviews, not from something anyone has watched being played. A described feature and a demonstrated feature are different kinds of evidence, and the distance between them is exactly where premature coverage goes wrong.
It also sets a realistic expectation for the wait. A studio that shows a cinematic four years ahead of a target window is telling you the game is not ready to be seen. The next genuinely informative moment will be the first continuous, unedited play footage.
The factions the developers point to
Terrans, Zerg and Protoss all appear in the announced game. For the cinematic specifically, Dan Hay says Protoss architecture is hidden in it, and separately names zerglings, mutalisks and overlords. [C]
Treat that as a pointer, not an inventory. Those named units are the ones a developer chose to mention in an interview; they are not a complete confirmed enemy list, and a creature appearing in a pre-rendered sequence is not a promise that you will fight it, or fight it in that form.
The more useful signal is structural. Naming all three factions and hiding Protoss architecture in the background suggests a world where the three-way history is present in the environment rather than confined to a briefing screen. That is a reasonable reading. It is still a reading.
Who scored it
The cinematic music is by Finishing Move, with early thematic contributions from Mick Gordon; Derek Duke served as music director. [D]
Those credits cover the cinematic. They do not confirm the same line-up for the full game soundtrack, and an early thematic contribution is not the same role as scoring a finished game. We mention it because the credit has already been widely compressed into “Mick Gordon is doing the StarCraft soundtrack”, which the source does not support.
How to read the next cinematic
Three habits keep a trailer useful instead of misleading:
- Separate the name from the product. Cinematics, demos and events all get titles. Only some of them end up on the game.
- Ask what a shot would cost to fake. Pre-rendered footage has no obligation to the engine, the systems or the final art. It tells you about tone and intent, which are real things — just not mechanical ones.
- Note what a developer mentions unprompted. A detail volunteered in an interview is usually something the team is confident about. A detail only visible to viewers is a detail someone may be over-reading.
When the first real gameplay arrives, this page should be rewritten rather than quietly extended, and the change history below should say so.
Change history
- First prepared draft. Title and summary changed from the original content plan: the planned version promised observations with verified timestamps, which we have not carried out. The page now states plainly that it is not a frame-by-frame breakdown and rests only on attributed official and developer statements.
Read and released by a named editor before publication. We have no access to the unreleased game: nothing on this page is an account of firsthand play, and every description of a mechanic is attributed to the source that stated it.