StarCraft Shooter Leads BlizzCon 2026: Corden Footage [2026]

Rumored StarCraft Shooter to Lead BlizzCon 2026 as Reported Sept 8 With Terran vs Zerg Footage Claim

By Indie Kings | September 8, 2026 | Updated September 8, 2026 | 21 min read | Rumor, StarCraft, Blizzard, BlizzCon | Labels: Blizzard

Image: Pexels free use.

On September 8, 2026, this rumor roundup collects claims that a StarCraft shooter could lead BlizzCon 2026 on September 12 and September 13 in Anaheim, with all claims below treated as rumor only and not as confirmation from Blizzard.

All items below are rumors only. Nothing here is treated as fact. Each section attributes the outlet and date for the claim described. The lead claim is attributed to Windows Central reporting dated September 8, 2026 by Jez Corden. Supporting context on shooter design limits is attributed to prior reporting background linked to Jason Schreier. Adjacent business and strategy context on Nexon and on a canceled internal strategy effort reported as Blackbird is kept as separate rumor context. Corroborating puzzle context from the official site window is attributed to GamesRadar on September 7, 2026 by Anthony McGlynn and to Enduins on September 7, 2026 by Sai T. Readers should treat every footage description, staffing link, genre comparison, timeline read, and lore link as not proven until Blizzard shares direct detail on an official channel. This post uses words like reported, alleged, rumored, claimed, and fan read through the full text to keep that status clear.

Table of Contents

1. 1. September 8 Rumor Overview on Shooter as Reported BlizzCon Lead
2. 2. Windows Central September 8 Report by Jez Corden and Claim Scope
3. 3. Reported Early Terran vs Zerg Open World Footage Description
4. 4. Dan Hay Ex Far Cry Lead Role as Reported Staffing Context
5. 5. Reported Full Co-op Campaign Hope With Gears Siege and Helldivers Like Comparisons
6. 6. Schreier Not Destiny Caveat as Reported Design Limit
7. 7. Nexon Side Project Talk and Blackbird RTS Context as Separate Rumors
8. 8. Official Site ARG Glitch and Kerrigan Corroboration Reported September 7
9. 9. Table 1 Rumor Tracker and Table 2 BlizzCon Lead Options
10. 10. FAQ Six Questions on Proof Status and Next Checks

1. September 8 Rumor Overview on Shooter as Reported BlizzCon Lead

According to Windows Central reporting dated September 8, 2026 by Jez Corden, Blizzard is rumored to position a StarCraft shooter as a lead reveal for BlizzCon 2026, which is scheduled for September 12 and September 13, 2026 at the Anaheim Convention Center, and that positioning claim is presented here strictly as a report about plans, not as a Blizzard confirmed schedule. The report is described as stating that Corden was shown or told about early footage with Terran forces facing Zerg in an open world style space, that the project is linked to Dan Hay, a former Far Cry lead, and that the hope inside the reporting is for a full cooperative campaign with structure compared by fans and commentators to Gears style cover shooting, Siege style tactical co-op, and Helldivers style squad extraction loops. No title, no release window, no platform list, no price, no beta date, and no stage time are cited in the details supplied for this article as confirmed. The lead billing idea therefore stays tagged as a rumored plan that can shift before show week.

According to the rumor handling rules used through this post, lead billing at BlizzCon means placement in the opening ceremony plus demo floor space plus press follow up, and none of those placements are proven by a single pre show report. Opening ceremony slots often change late for polish, legal review, localization readiness, age rating readiness, music licensing, actor strike rules where performers are involved, and partner marketing holds. A project can be internally targeted as a lead in early September and still slip to a teaser card, a behind closed doors press demo, or a next year hold by September 12. The Windows Central September 8 report by Corden is the attribution for the lead billing claim, not a Blizzard stage schedule. Until Blizzard posts a schedule page, a map of the show floor, or a trailer premiere notice with a time, readers should log lead billing as an alleged plan with high change risk.

According to the wider rumor file summarized here, three separate tracks meet around this lead billing claim without proving each other. Track A is the shooter plan itself, with footage description, staffing link, and co-op hope. Track B is design scope control from Schreier linked background, which is read as warning against a Destiny style live service expectation. Track C is adjacent strategy and business chatter, with Nexon linked side project talk on one side and canceled internal real time strategy exploration reported as Blackbird on the other side. Track D is the official site puzzle window reported September 7, with shipping log text, cargo audio, patient log text, glitch effects, and console timestamps read by fans as pointing to Kerrigan and to a story jump decades after Legacy of the Void. Only a Blizzard direct reveal can join these tracks. Until then this article keeps each track on its own proof, with the September 8 Corden report as the sole citation for the lead billing idea.

According to the date logic stressed for pre show week, September 8 sits four days before the September 12 opening, which is a window when controlled teases, agency bookings, retail database entries, rating board updates, and social account follows often leak in advance if a lead reveal is real. The supplied facts do not cite a rating board entry naming a StarCraft shooter, a Blizzard store placeholder, a Battle.net backend string with a shooter codename, a trademark filing with a matching show week date, or a talent repost tying a performer to a September 12 premiere. Absence of those signals does not disprove the Corden report, because Blizzard can hold assets tight until stage time, but it keeps the claim at single source rumor strength. Readers who see reposts that upgrade the claim to confirmed should ask for the second source with outlet plus date plus raw asset. If that second source is missing, the correct label remains rumored lead plan reported by Windows Central on September 8.

2. Windows Central September 8 Report by Jez Corden and Claim Scope

According to Windows Central reporting dated September 8, 2026 by Jez Corden, the core claims are that a StarCraft shooter exists in playable or viewable early form, that footage shows Terran versus Zerg combat in an open world style area, that Dan Hay with a Far Cry lead background is connected to the effort, and that the project is positioned internally as a possible BlizzCon 2026 lead, with a stated hope for a full cooperative campaign rather than a competitive only package. That four part scope is the full extent of what this article attributes to Corden on September 8. The report as described does not supply a title, a cinematic, a release year, a business model, a player count lock, an engine note, a studio headcount, or a hands on build number that others can check. Scope control matters because reposts often add detail that was not in the source, such as a release year, a Game Pass note, a PlayStation build note, or a beta month. None of those additions are attributed to Corden in the supplied facts and none should be treated as part of his report.

According to standard source weighting for single reporter claims about unannounced games, a Corden byline on Windows Central carries interest because the outlet covers Xbox and Blizzard closely after the Microsoft acquisition era, but a single pre show claim still needs a second anchor before use as fact. Useful second anchors would be a matching report from a second outlet with its own sourcing on the same day or later, a Blizzard owned tease that matches the footage beats, a performer or vendor credit that names a StarCraft shooter team, a rating or database entry with a matching title shape, or a show week schedule leak with a matching stage slot. No second anchor is described in the supplied facts as present. The claim therefore stays at one outlet plus one author plus one date. This article repeats that citation in every section so readers can test reposts that drop the attribution and present the shooter as announced.

According to careful reading of pre show language, words like lead, headline, tentpole, and marquee are often used by sources to describe internal hope rather than locked show order. A source can correctly say a team hopes its game leads while the show team has not locked the order. A reporter can correctly pass that hope along while readers misread it as a locked opener. The supplied summary uses hope language around full co-op campaign structure, which signals aspiration inside development or publishing rather than a shipped feature list. The same caution applies to lead billing. An alleged internal target to lead BlizzCon 2026 is not a printed run of show. Until Blizzard posts the September 12 opening ceremony rundown with times, this article keeps lead as reported intent, not as a confirmed slot, with Windows Central on September 8 by Corden as the only citation for that intent.

According to the cross check method recommended here, readers should save the original Windows Central September 8 page with author name, timestamp, headline, and quoted lines, plus an archive copy, before comparing later claims. Later posts that cite Corden should be checked for added words. If a later post adds open world confirmed, release 2027, Game Pass day one, PlayStation 5 confirmed, or beta soon without a new source line, that addition is new rumor, not Corden reporting. If a later post cites anonymous social accounts, retail placeholders without screenshots, or AI voiced videos as proof, that material is weaker than the Corden report, not stronger. The correct stack is simple. Corden September 8 is the base rumor. Everything else needs its own outlet plus date plus raw detail before it can move the status. For related puzzle background that some readers merge into this shooter claim, see our Kerrigan ARG second transmission roundup at StarCraft ARG Second Transmission Reported Sept 7 Points to Rumored Kerrigan Return, which is kept as a separate rumor file and does not prove a shooter.

3. Reported Early Terran vs Zerg Open World Footage Description

According to Windows Central reporting dated September 8, 2026 by Jez Corden, early footage is described as showing Terran forces against Zerg in an open world style setting, and that description is presented here as a secondhand footage read, not as a frame by frame leak with timecodes, resolution notes, HUD captures, or file hashes. The phrase open world style needs care because it can mean a large contiguous map with outposts and patrols, a hub with large mission zones, a set of wide linear missions with optional objectives, or simply an early vertical slice with extra draw distance for a trailer. The supplied facts do not specify map size, traversal method, vehicle use, day night state, weather state, number of biomes, fast travel design, enemy density, civilian presence, or Protoss presence. Without those fields, open world functions as a loose area shape claim, not as a systems confirmation. The Terran versus Zerg pairing is the more concrete beat, because it names two factions, but even that pairing leaves open whether the player is Terran, whether Zerg are the main enemy or one of several, and whether Protoss appear later.

According to footage verification practice for unannounced games, a described viewing without shared frames cannot be tested by readers. Testable proof would be a clip with a HUD, a build watermark, a debug overlay, a matching environment asset with a prior Blizzard art post, a weapon model with a lore tied serial, a new Zerg variant with a rigging tell that differs from StarCraft 2 assets, or a file with metadata that others can inspect. None of those are cited as present in the supplied facts. That gap is normal for early pre show reports where sources describe a viewing room without permission to record, but it keeps the footage claim at witness description strength. Readers should not treat artist impressions, fan made Unreal mockups, recut StarCraft cinematics, or AI upscaled Ghost era footage as matches. A real match would need Blizzard direct frames with a show week trail.

According to lore and art risk notes relevant to Terran versus Zerg reads, Zerg textures read fast in low resolution, which helps rumors spread and also makes false matches easy. Hydralisk silhouettes, Baneling greens, Creep purples, Terran marine armor blocks, Siege Tank barrels, dropship engine glows, and colony prefabs can be mimicked with kitbashed models, old cinematic recuts, custom StarCraft 2 arcade maps, and cosplay photography with heavy grading. A short glimpse of brown armor plus purple biomass can feel like StarCraft even when the source is generic science fiction. The Corden September 8 footage description as summarized does not include a claimed new unit name, a new planet name with canon coordinates, a new ship registry, a dialogue line with a transcript, or a HUD objective string. Those missing specifics keep the footage beat thin. Thin does not mean false, but it means low test value until Blizzard shares frames.

According to the way open world claims often evolve, the next rumor step is usually a map size leak, a traversal leak, or a mission structure leak, and each of those steps needs its own outlet plus date before use. If a new post claims seamless continents, drivable vehicles, base building, or extraction zones as part of this StarCraft shooter, that post must be logged as a new claim with its own source, not as part of Corden September 8. The supplied facts limit Corden to early Terran versus Zerg open world style footage without systems detail. This article enforces that limit. Any graphic that lists planets, travel times, enemy counts, or weapon stats for the shooter should be treated as fan made unless it links back to a Blizzard domain, a rating entry, or a second sourced report with raw proof.

4. Dan Hay Ex Far Cry Lead Role as Reported Staffing Context

According to Windows Central reporting dated September 8, 2026 by Jez Corden, Dan Hay with a former Far Cry lead background is linked to the rumored StarCraft shooter effort, and that staffing link is presented here as reported personnel context, not as a Blizzard org chart post with title, studio, start date, and team size. Hay is widely associated in public coverage with Far Cry open world leadership at Ubisoft, including work around Far Cry 5 era systems and world building, which is why the link fuels open world readings of the shooter. A lead background in open world first person design would fit a Terran versus Zerg field game with outposts, patrols, and co-op objectives, but fit alone does not confirm assignment. Staffing moves in large publishers can involve incubation, advisory reviews, prototype direction, or a full production lead role, and those levels differ sharply in proof. The supplied facts do not specify Hay job title on the shooter, reporting line, studio location, or tenure dates tied to the project.

According to staffing verification practice, a personnel link needs a primary anchor before use as fact. Strong anchors would be a Blizzard news post naming Hay with a StarCraft shooter role, a LinkedIn history update with matching dates and project code, a conference bio with a Blizzard shooter credit, a patent or talk abstract with a matching team, or a second sourced report with its own employment records. None of those anchors are described as present in the supplied facts. Public knowledge that Hay joined Blizzard in past years for survival and shooter adjacent exploration is often cited in comment threads, but past employment alone does not place a person on a specific 2026 StarCraft shooter build. This article therefore keeps Hay as a reported name attached by Corden on September 8, not as a confirmed director with a quoted vision statement.

According to the limits of using a lead name to infer design, a Far Cry background suggests comfort with outposts, hunting loops, companion systems, and regional control, yet a StarCraft shooter could use none of those if Blizzard targets a tighter co-op campaign instead. Leads often change genre when they change company, and publishers often pair an open world lead with a linear shooter team to restrain scope. The supplied facts do include a hope for a full cooperative campaign with Gears style, Siege style, and Helldivers style comparisons, which points away from a pure Far Cry clone and toward squad missions with shared objectives. Readers should not convert Hay background into a feature list. The correct use is narrow. Corden September 8 links Hay to the effort as a rumor. Design detail still needs its own sourced lines with build proof.

According to the tracking method used here, any new staffing claim around the shooter should be logged with name plus claimed role plus claimant outlet plus date plus anchor type. A repost that says Hay confirms open world because of Far Cry history is adding inference not present in the source report. A post that names additional leads, writers, audio directors, or art directors without outlet plus date is adding new rumor. A post that shows a conference badge, an email header, or an internal slide without metadata and trail is weaker than a second sourced report. Until Blizzard names the team on a stage or on a jobs page that specifies a StarCraft shooter, the staffing file stays at one reported name with one citation. That citation is Windows Central on September 8 by Jez Corden.

5. Reported Full Co-op Campaign Hope With Gears Siege and Helldivers Like Comparisons

According to Windows Central reporting dated September 8, 2026 by Jez Corden as summarized for this article, the hope attached to the rumored shooter is for a full cooperative campaign, and commentators frame that hope with comparisons to Gears style cover shooting, Siege style tactical co-op, and Helldivers style squad extraction loops, with all comparisons presented here as shorthand for desired feel, not as confirmed systems. Full co-op campaign in this context would mean a story campaign playable solo with AI support and in squads with shared progression, checkpoints, difficulty tiers, and mission replay, rather than a competitive multiplayer only package or a short tutorial plus horde mode. The supplied facts do not lock a squad size, a mission count, a difficulty system, a friendly fire rule, a revive rule, a class system, a loadout system, or a progression wipe policy. Without those fields, full co-op remains an aspiration label with wide implementation range.

According to careful use of genre comparisons, each like comparison points to a different design risk. Gears style points to cover, roadie run pacing, active reload feel, and arena encounters with large enemies, which would fit Terran marines against Zerg waves in trench and colony spaces. Siege style points to breaching, intel tools, tight interiors, operator like roles, and round structure, which would fit ship boarding and facility clears more than open fields. Helldivers style points to drop in extraction, friendly fire tension, stratagem calls, patrol pressure, and live service rotation, which would fit a replayable Zerg planet loop but would push the project toward ongoing operations. A single game rarely delivers all three at full depth, so the triple comparison should be read as a wishlist of tones from different observers, not as a three way hybrid confirmed by Corden. The source report as summarized expresses hope for full co-op, while the Gears Siege Helldivers language is the surrounding shorthand used to explain that hope.

According to scope control lessons from prior Blizzard incubation history, full co-op campaign is the claim that most affects schedule, headcount, and BlizzCon readiness. A full campaign needs script lock, voice capture, localization, cinematics, accessibility passes, difficulty tuning, network rollback or host migration testing, cross play testing where promised, and age rating submissions with final content. A competitive only slice or a co-op horde slice can be demoed far earlier than a full campaign with an ending. The supplied facts describe early footage only, which is consistent with a vertical slice rather than a content complete campaign. Readers should therefore treat full co-op as a development target reported as hope, not as a shipped mode list. Proof of full co-op would need a mission count, a squad size lock, a difficulty and progression note, and a Blizzard stage demo with live squad play.

According to the demo logic relevant to a rumored BlizzCon lead, a full co-op hope helps explain why Blizzard might want the shooter on stage, because live squad play photographs well and fills a show floor with repeatable pods. It also explains risk, because live network demos fail often and full campaigns leak spoilers fast. If the shooter leads BlizzCon 2026 as rumored, the safest stage proof would be a short live squad mission with Terran players against Zerg pressure, a clear objective string on the HUD, a revive and extraction beat, and a no spoiler promise for later missions. A cinematic only reveal would prove less about co-op readiness. Until September 12, the co-op file stays as hope language from the September 8 window, with Windows Central by Corden as the attribution for the hope and with Gears Siege Helldivers language kept as comparison shorthand, not as sourced systems.

6. Schreier Not Destiny Caveat as Reported Design Limit

According to prior reporting background linked to Jason Schreier as framed in the supplied context, the StarCraft shooter exploration is described with a not Destiny caveat, meaning observers should not expect a Destiny style shared world live service grind as the default model, and that caveat is presented here as reported context about scope, not as a Blizzard design document quote. The not Destiny line matters because any StarCraft shooter rumor immediately triggers Destiny comparisons around hubs, strikes, raids, power grind, seasonal resets, and eververse style monetization. A caveat that the project is not Destiny shaped would point toward a more contained campaign plus co-op structure, a limited live tail, or a premium box with optional expansions rather than a decade long power chase. The supplied facts do not provide a direct Schreier quote with date, outlet, word for word wording, or build context, so this article keeps the caveat as background framing with Schreier attribution, not as a locked design pillar.

According to the way design caveats function in rumor cycles, not Destiny can be misread as no live service at all, which overstates the point. A game can avoid Destiny structure while still shipping seasonal maps, rotating mutators, battle pass cosmetics, or paid story chapters. It can also avoid live service at launch and add operations later if the launch lands. The supplied context does not resolve monetization, seasons, or post launch support for the rumored shooter. It only signals that readers should temper Destiny expectations. That tempering fits the full co-op campaign hope in section 5, because a Gears style campaign plus a Helldivers style loop can coexist without copying Destiny power grind. Fit across rumors still does not equal proof. Each design beat still needs a Blizzard direct line with systems detail before use as fact.

According to source hygiene for secondhand Schreier references, a caveat needs a primary citation with outlet plus date plus exact wording before it can carry weight equal to the Corden September 8 report. Paraphrases that travel through social threads often sharpen into false quotes, such as not a live service, single player only, or no microtransactions, none of which are stated in the supplied facts. This article does not upgrade the caveat beyond not Destiny shaped expectation control. Readers who see posts that claim Schreier confirmed no seasons, no shop, or no battle pass should ask for the original post with timestamp and full text. If that original is missing, the claim is new rumor layered on old background. The correct label remains reported background with Schreier link, kept separate from Corden September 8 footage and staffing claims.

According to the practical use of this caveat for BlizzCon expectations, a not Destiny shooter would be easier to demo as a lead without promising a ten year roadmap on stage. Blizzard could show a campaign mission, name the squad size, name the difficulty options, and promise a story ending, which is a cleaner stage message than a systems heavy live service reveal with power bands and season calendars. That stage fit may explain why the caveat travels with the lead billing rumor, but stage fit is not proof of design. Until Blizzard shows a menu with campaign, co-op, and extras tabs, or publishes a fact sheet with player count and progression rules, the not Destiny line stays as expectation control only. The attribution stays as Schreier linked background, distinct from Windows Central September 8 by Corden on footage, staffing, co-op hope, and lead billing.

7. Nexon Side Project Talk and Blackbird RTS Context as Separate Rumors

According to business chatter context supplied for this article and flagged as rumor, talk of a Nexon linked side project circulates near the shooter rumor, but that talk is kept here on a separate proof track because no contract, filing, joint post, title, genre lock, or date is cited as tying Nexon to the specific shooter described by Corden on September 8. Nexon linked Blizzard collaboration talk in 2026 coverage often concerns publishing scope, service operations, or co development for Asia facing builds, as often discussed in business rumor coverage, while the Corden shooter is described as a Blizzard led console and PC style campaign shooter with open world style Terran versus Zerg footage. Those shapes can coexist as two projects, one internal shooter plus one Nexon adjacent effort, or the Nexon talk can be wrong while the shooter is real, or the shooter can be wrong while business talks are real. The supplied facts do not join them. This article therefore logs Nexon talk as adjacent rumor context with no shared proof.

According to strategy history context supplied and flagged as rumor, an internal real time strategy exploration reported under the name Blackbird is cited as canceled or shelved context, and that context is also kept separate from the shooter proof track. Blackbird talk matters because StarCraft fans track every real time strategy hint as a possible mainline return, and a canceled strategy incubation would help explain why Blizzard might push a shooter as the StarCraft lead instead of a strategy sequel at BlizzCon 2026. A cancellation can free staff, budget, and stage time for a different genre lead. It can also create morale and direction questions that make a shooter reveal harder, not easier. The supplied facts do not provide a Blizzard postmortem, a headcount transfer memo, a prototype asset, or a date stamped cancellation note for Blackbird. Without those, Blackbird stays as background rumor that frames genre strategy, not as proof of a shooter.

According to the error pattern seen in past Blizzard rumor cycles, the most common mistake is to merge business plus strategy plus puzzle threads into one assumed reveal, such as Nexon funds the shooter which adapts the ARG Kerrigan story after Blackbird was canceled. That sentence strings four unproven links into one story. Each link needs its own outlet plus date plus raw detail. The shooter needs Corden September 8 plus a second anchor. Nexon needs a business source with document or joint statement. Blackbird needs a strategy reporting source with employment or asset proof. The ARG Kerrigan thread needs a Blizzard anchor for puzzle authorship plus a lore post for timeline use. No merged reveal exists in the supplied facts. Until Blizzard joins tracks on stage, readers should keep Nexon and Blackbird in a side box labeled rumor context that explains why fans debate genre, not as evidence that a shooter leads BlizzCon.

According to the tracking discipline enforced in the tables in section 9, Nexon side project talk and Blackbird real time strategy context each get their own row with rumor status and a missing proof note. Useful missing proof for Nexon would be a joint press note, a regulatory filing with project scope, or a jobs page naming a Nexon Blizzard team with a StarCraft adjacent title. Useful missing proof for Blackbird would be a named cancellation report with dates, a staff move trail, or a prototype detail that others can check. Neither set is described as present. The shooter lead claim therefore cannot borrow weight from either row. If Blizzard announces a shooter on September 12, that announcement will move only the shooter row. Nexon and Blackbird rows will move only on their own business or strategy posts. That separation prevents a single stage reveal from being misread as proof of a business deal or a canceled strategy past.

8. Official Site ARG Glitch and Kerrigan Corroboration Reported September 7

According to GamesRadar reporting dated September 7, 2026 by Anthony McGlynn, a second transmission in a rumored StarCraft puzzle chain surfaced with shipping log text containing an 8 letter K string read by some fans as Kerrigan, plus cargo audio described as screeching and a patient log section, and according to Enduins reporting dated September 7, 2026 by Sai T., the same window included glitch effects on the official site plus console timestamp clues read by fans as 60 to 70 years after Legacy of the Void, with both reports presented here as puzzle rumor, not as Blizzard confirmation of a shooter or of Kerrigan. The corroboration value for the shooter rumor is indirect at best. A live puzzle would show Blizzard is willing to tease StarCraft before BlizzCon, which fits a lead reveal plan, but puzzle authorship itself is unproven, the Kerrigan read is fan interpretation, and no puzzle line names a shooter, a studio, a title, or a stage date. Timing proximity from September 7 to a September 12 show does not prove shared origin.

According to the clue detail attributed to GamesRadar on September 7 by McGlynn, the shipping log beat is a manifest style text with a K initial of Kerrigan length, the cargo beat is an audio texture linked by fans to Zerg linked containment, and the patient log beat is medical observation framing with redactions read by fans as containment or recovery, but none of those beats identify Sarah Kerrigan by proof such as a voice credit, a model still, a script page, or a Blizzard name post. According to the web detail attributed to Enduins on September 7 by Sai T., glitch effects mean flicker, scramble, tearing, or hidden layers, plus console numbers converted by fans to a 60 to 70 year jump after the 2015 Legacy of the Void epilogue that last showed Kerrigan with Raynor after an 11 year gap to 2026. Those web observations need raw page source, network proof, console exports, and a Blizzard anchor before lore use. For full clue tables and method checks, see our separate Kerrigan ARG second transmission roundup at StarCraft ARG Second Transmission Reported Sept 7 Points to Rumored Kerrigan Return, which logs six transmission rows with outlet plus date on each row.

According to the first since 2013 framing often attached to this puzzle, the current chain is described by fans as the first StarCraft alternate reality game style effort since the Heart of the Swarm campaign in 2013, a 13 year gap that raises attention but does not prove Blizzard authorship, because puzzle formats are public and reusable. According to July 2026 client context often cited nearby, StarCraft 2 received a surprise patch that shows ongoing support, but no matching strings, hashes, or assets tying that patch to September clues are cited as confirmed. Both points explain why fans pay attention in the week before BlizzCon, but neither tests whether Blizzard wrote the shipping log, rendered the cargo audio, staged the glitch effects, or set the console numbers. This article therefore uses the September 7 puzzle only as atmosphere that fits a pre show tease pattern, not as corroboration that a shooter exists or leads.

According to the rule against merging tracks, a Kerrigan puzzle even if proven official would not prove a Terran versus Zerg shooter with Dan Hay and full co-op. Blizzard can run a lore puzzle for a novel, a short film, a co-op commander, a balance patch story note, or a BlizzCon lore panel without a shooter. Blizzard can also reveal a shooter without Kerrigan, with new marines, new colonies, and new broods far from the 2015 epilogue. The 60 to 70 year jump read would complicate a Kerrigan shooter link further, because it would force questions about mortality, succession, memory, and power scale for a Xel Naga linked figure last seen with Raynor, none of which are answered by a K initial plus sound texture. Until a Blizzard channel links the puzzle to the shooter by shared title, shared art, or shared stage code, the September 7 ARG material stays in its own rumor file with Kerrigan as fan guess only.

Table 1: Shooter and Puzzle Rumor Tracker With Outlet Plus Date

Claim	Attributed Source	Date	What Was Reported	What Is Missing	Status
Shooter leads BlizzCon 2026	Windows Central by Jez Corden	Sept 8, 2026	StarCraft shooter positioned as possible show lead	Schedule page, floor map, premiere notice	Rumor
Early Terran vs Zerg open world footage	Windows Central by Jez Corden	Sept 8, 2026	Early viewing described as Terran vs Zerg open world style	Clip, HUD still, build number, file hash	Rumor
Dan Hay linked to shooter	Windows Central by Jez Corden	Sept 8, 2026	Ex Far Cry lead connected to effort	Title, role, studio post, tenure dates	Rumor
Full co-op campaign hope	Windows Central by Jez Corden, hope language	Sept 8, 2026	Target described as full co-op, Gears Siege Helldivers like shorthand	Squad size, mission count, progression note	Rumor
Not Destiny scope	Schreier linked background	Prior background	Expectation control against Destiny style live service	Direct quote, outlet, date, systems sheet	Rumor context
Second transmission Kerrigan read	GamesRadar by Anthony McGlynn	Sept 7, 2026	Shipping log 8 letter K plus screeching cargo plus patient log	Image, voice credit, model, Blizzard name post	Rumor
Site glitch plus 60 to 70 year jump	Enduins by Sai T.	Sept 7, 2026	Glitch effects plus console numbers read as decades after Legacy of the Void	Console export, epoch method, timeline post	Rumor