StarCraft intelligence · Evidence checked 25 September 2026
StarCraft Roxara transmissions: what BlizzCon confirmed
Blizzard's “Conflicting Records” archive told a 2575 story about Theta Squadron, dangerous research cargo, falsified Dominion incident reports and Project Spellbind. Dan Hay has now confirmed that Blizzard created the website experience to tease the announced STARCRAFT game. That resolves the marketing connection; it does not establish that Roxara or the archive's story appears in the final game.
Current status
Archived first-party record: Blizzard intentionally published Transmission 04 through its official StarCraft website. The captured payload contains five numbered records—000623, 001089, 001998, 003795 and 006214—plus a separate “Official Dominion Transcript.” [S01] [S02] [S03]
Current endpoint state: the same official /en-us/conflicting-records URL returned HTTP 200 while rendering Blizzard's generic 404 surface when rechecked at 20:46 BST on 18 September 2026. It exposed no transmission number, campaign payload or redacted records. The archived text and prior SHA-256 remain the evidence for what was published; Sourceborne does not describe the campaign endpoint as currently live.
Marketing connection confirmed: Dan Hay says Blizzard created the website experience to tease STARCRAFT. [S07]
Narrative continuity unresolved: Blizzard has not said that Roxara, Theta Squadron, Special Orders 132/176 or Project Spellbind appears in the final game's story. The redacted threat and patients also remain unidentified.
Confirmed information
How the artifact works
The earlier official homepage loaded a Blizzard-hosted JavaScript bundle. That code requested the conflicting-records route and progressively displayed the returned material with deliberate visual interference. This implementation rules out an accidental site failure in the captured campaign. [S01] [S03]
At the 12 September capture, the endpoint returned status 200 and labelled the stage transmission: "04". The captured response's SHA-256 hash is recorded below. On 18 September, the route still returned status 200 at the HTTP layer but its visible content was Blizzard's generic 404 surface, with no transmission data. That availability change does not alter the preserved payload. [S02]
What each record contains
| Record | Literal contents | What it does not establish |
|---|---|---|
| 000623 | A sensor detects 14 occupants where zero are registered. Medical records name redacted patients F. C. and T. W. A recovered order sends Theta Squadron and research cargo to Roxara. | The cargo’s species, purpose or product context. |
| 001089 | Another sensor detects 102 unregistered occupants. Workers say sealed crates move, change apparent weight and produce scratching or screeching. A user encounters missing records and inconsistent personnel history. | That the contents are Zerg; that the anomalies are time travel. |
| 001998 | A hidden warning says to question the records. Roxara’s recorded population rises beyond capacity. A crate ruptures, workers disappear, and Keri Parker reports an attack on trapped miners. | The attacker’s identity; a playable mission or mode. |
| 003795 | Official mine-fire reports conflict with special-access records describing failed experiments, containment failures and thousands of deaths on Roxara, Veil IX, Candore and Abaddon. An operations order names Project Spellbind. | That every report is complete or truthful; that Project Spellbind is a game title. |
| 006214 | A fugitive user alleges whitewashing, lists affected settlements and says Roxara was not the first. Two patients are recorded as deceased. The archive ends with a returned ping that was never sent. | Who the user is, what returned the ping or what follows. |
The two competing Roxara records
The public-style report says 114 people died after an uncontrolled burn and gas leak at Roxara Lunar Mining Complex. The special-access record instead lists 4,983 casualties after an attack tied to experiment and containment failures. The contradiction is the narrative device at the centre of “Conflicting Records.” [S02]
Project Spellbind
The retrieved order describes Project Spellbind as a Dominion security operation. Theta, Delta, Gamma and Lambda squadrons are ordered to investigate settlements, suppress dissenters or “hostiles,” preserve productive infrastructure and re-establish Dominion control. The name is therefore confirmed inside the fiction; it is not confirmed as a product title or codename. [S02]
Reported information
Before the complete current archive was captured, Icy Veins documented the site’s intentional code path and early fragments involving Roxara, Theta Squadron, research cargo and anomalous sensors. That coverage is useful for rollout chronology, but the live first-party endpoint now supersedes it for the text itself. [S04]
Before the announcement, Windows Central reported that Jez Corden saw early footage of an internal Blizzard StarCraft shooter featuring Terran marines fighting Zerg. Blizzard has since announced an open-world StarCraft shooter, but that does not retrospectively prove that the reported footage or Roxara fiction represents the final game. [S05] [S07]
Fan discussions and follow-up articles have proposed specific identities for redacted names and creatures. Those readings are not elevated here because the official text withholds the decisive nouns.
Community theory: S. K███████ = Sarah Kerrigan
A traceable community theory proposes Sarah Kerrigan as a solution to the redacted S. K███████ name in the ARG material. The match is based on interpretation of the redaction pattern and is not confirmation. Blizzard has not identified the redacted person and has not announced Kerrigan as part of the new game's cast. Sourceborne keeps the theory separate from the archived first-party record. Status: Community theory / unconfirmed. [S079]
Analysis
The archive’s structure is more informative than any one redaction. Each stage contrasts routine administrative language with impossible sensor counts, biological readings and higher-clearance reports. By Transmission 04, the story is explicitly about institutional falsification: disasters are reframed as industrial accidents while restricted files describe experiments, containment failures and coercive military operations.
Roxara is the campaign's evidence room: a place where official and restricted versions can be compared. The campaign is now confirmed as a marketing tease for STARCRAFT, but its story status is still open.
The strongest safe genre inference is “military science-fiction horror.” “Zerg outbreak,” “Kerrigan return” and “shooter campaign” are plausible fan readings, but all require filling redactions or connecting a separate report. The fact that one reading fits does not make alternatives impossible.
The numbers also require care. The casualty counts and medical values are fictional claims inside documents whose reliability is deliberately contested. They can be reported as text the archive contains, not as an omniscient canon account of what “really happened.”
Hypotheses
H-RX-01 — The sealed cargo contains Zerg organisms
Assessment: Possible.
Basis: The crates move, make animal-like sounds and precede containment failure; StarCraft’s Zerg are a natural fit. [S02]
Competing explanations: Another organism, infestation, experimental hybrid or deliberate misdirection.
Test: An unredacted species name, identifiable visual or official story continuation.
H-RX-02 — The impossible records indicate temporal or reality distortion
Assessment: Possible.
Basis: Timestamps run beyond conventional hours, packet age is unstable, logs appear opened in advance, and medical readings exceed plausible human limits. [S02]
Competing explanations: Corrupted systems, unreliable narration, biological transformation or stylised puzzle design.
Test: Explicit narrative explanation in a later transmission or product reveal.
H-RX-03 — The campaign's story continues in STARCRAFT
Assessment: Possible, unverified.
Basis: Hay confirmed the website experience was built to tease STARCRAFT. [S07]
Competing explanation: The fiction may have served only as pre-reveal marketing and may not be part of the final narrative.
Test: Official use of Roxara, Theta Squadron or Project Spellbind in story or gameplay material.
H-RX-04 — A redacted patient is an established StarCraft character
Assessment: Unverified.
Basis: Initials invite recognition, and the campaign trades on withheld identity.
Competing explanations: New characters or intentionally ambiguous placeholders.
Test: Full name or unmistakable first-party identification. Initials alone are insufficient.
FAQ entries
Are the Roxara transmissions official?
Yes. The captured records were served by Blizzard's official StarCraft domain and displayed by Blizzard-hosted site code. The route no longer exposed the archive when rechecked on 18 September; it returned HTTP 200 with Blizzard's generic 404 surface.
Is the “glitch” accidental?
No. The page script deliberately requests and reveals the records with glitch effects. [S03]
What is Transmission 04?
It is the current captured stage of the archive, containing five numbered records and an official-style Dominion transcript.
What happened on Roxara?
The records conflict. One account describes an industrial fire with 114 deaths; a restricted account describes 4,983 casualties after an attack and failed containment. The campaign does not supply an uncontested final account.
What is Project Spellbind?
Inside the fiction, it is a Dominion operation to control multiple settlements and eliminate dissenters or hostiles. It is not a confirmed game title.
Are the creatures Zerg?
Not explicitly in the retrieved text. The relevant words are redacted.
Is Kerrigan in the transmissions?
Not confirmed. Matching initials or biological anomalies to a known character is a hypothesis.
Does the campaign take place after StarCraft II?
The files repeatedly use the year 2575. Placing that precisely in canon requires separate timeline assumptions; the safe statement is only that 2575 is the date printed in the campaign.
Does this confirm a new StarCraft game?
The marketing connection is now confirmed: Hay says the website experience teased the announced STARCRAFT game. It does not confirm that the archive's plot or locations appear in the final narrative. [S07]
Sources
- [S01] Primary — Official StarCraft homepage. Campaign surface; accessed 12 September 2026.
- [S02] Primary — Official StarCraft “Conflicting Records” route. Transmission 04 captured 12 September 2026 at 07:18 UTC; archived response SHA-256
4f4e13e5f51b1901cd0e2360597cfa90cfe44cc804b209b7ffafa4c34a027036. On recheck at 20:46 BST on 18 September 2026, the route returned HTTP 200 but rendered Blizzard's generic 404 surface and exposed no campaign payload. - [S03] Primary technical artifact — Blizzard-hosted StarCraft homepage script. Fetch and display implementation; accessed 12 September 2026.
- [S04] Secondary observation record — Icy Veins: website glitches and early messages. Useful for early-stage chronology, not needed to authenticate current content.
- [S05] Original reporting — Windows Central: BlizzCon 2026 preview. Published 8 September 2026; separate shooter reporting.
- [S06] Primary event context — Blizzard: BlizzCon 2026 schedule. Accessed 12 September 2026.
- [S07] On-record developer interview — Inven Global: The StarCraft Shooter Is a Single-Player Boxed Game. Hay confirms the website experience was created to tease STARCRAFT; accessed 13 September 2026.
- [S079] Community theory — ARG redaction interpretation. Proposed Kerrigan match; not first-party identification.
Reliability and review dates
Reliability: High for the exact captured archive, its delivery mechanism and the on-record confirmation of its marketing purpose. Narrative-continuity claims remain unconfirmed. The archive's removal from the endpoint makes the preserved capture more important; it does not show that the fiction was retracted.
Created: 12 September 2026.
Evidence last checked: 18 September 2026 at 20:46 BST.
Next mandatory review: When the official route returns campaign content again or Blizzard publishes a new archive location.
Review triggers: Restored route, new record, unredacted identity, official product connection or materially changed response.