StarCraft Kerrigan Returns After 11 Years: 8-Letter Log [2026]

StarCraft ARG Second Transmission Reported Sept 7 Points to Rumored Kerrigan Return After 11 Years

Photo: Pexels free use.

On September 8, 2026, this rumored leak roundup collects second transmission reports dated September 7, 2026 that fans link to a possible Kerrigan return after 11 years without a new story appearance since the Legacy of the Void epilogue in 2015 with Raynor, 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 two main source reports for the second transmission are GamesRadar on September 7, 2026 by Anthony McGlynn and Enduins on September 7, 2026 by Sai T., according to the details supplied for this article. Readers should treat every decode, name match, timestamp 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.

1. Second Transmission Reported Sept 7 Overview and Rumored Kerrigan Link
2. Rumored 60 to 70 Year Jump After Legacy of the Void
3. GamesRadar Sept 7 Report by Anthony McGlynn and 8 Letter K Shipping Log
4. Reported Screeching Cargo Detail in Second Transmission
5. Reported Patient Log Detail in Second Transmission
6. Enduins Sept 7 Report by Sai T. on Glitch Effects and Console Timestamps
7. Kerrigan 11 Year Absence Since 2015 Epilogue With Raynor as Reported Context
8. First Rumored ARG Since 2013 Heart of the Swarm Plus July Patch Context
9. Table 1 Transmissions and Table 2 Rumor Tracker With Nexon and Shooter Context
10. FAQ Six Questions on Proof Status and Next Checks

1. Second Transmission Reported Sept 7 Overview and Rumored Kerrigan Link

According to GamesRadar reporting dated September 7, 2026 by Anthony McGlynn, a second transmission in the rumored StarCraft alternate reality game sequence surfaced with shipping log text, 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, with both outlets presenting the material as fan decoded clues rather than as a confirmed Blizzard product reveal. The rumored Kerrigan link comes from fan readings of those clues, not from a Blizzard statement naming Kerrigan, and no source cited here states that Blizzard has confirmed her return. The 8 letter K string in the shipping log is read by some fans as pointing to Kerrigan, according to GamesRadar on September 7, but that read remains interpretation only. The cargo audio and patient log add texture that fans connect to Zerg linked containment and medical observation themes, according to the same GamesRadar report, but those themes alone do not identify a character by proof. The Enduins report adds site level behavior and timestamp data that fans use to place the story far in the future, but that placement also remains a fan calculation, not a Blizzard timeline post.

According to the details supplied for this article, the second transmission follows an earlier first transmission that set up the current puzzle chain, and the second batch is described as denser because it mixes text logs with audio and site effects. GamesRadar on September 7 is attributed as the source for the three part breakdown of shipping log plus screeching cargo plus patient log. Enduins on September 7 is attributed as the source for official site glitch effects and console timestamp reads pointing to 60 to 70 years after Legacy of the Void. Neither outlet is described here as claiming Blizzard authorship with proof such as a signed news post, an in client string, or a press note asking press to follow the trail. Both reports are therefore kept in this article as rumor reports about a puzzle, not as proof of origin. That distinction shapes every section that follows, since a well made fan puzzle can mimic official style without official status.

According to fan readings summarized in those September 7 reports, the Kerrigan theory gained speed because Kerrigan has not had a new story appearance in 11 years, since the Legacy of the Void epilogue in 2015 that showed her with Raynor, and a long absence makes any possible hint feel large. The reports do not present a clear image of Kerrigan, a new voice line credited to a performer, a new model render, or a script page naming her in a new scene. The claimed link rests on an 8 letter K string plus thematic fits around containment and observation, which fans combine into a name guess. Short strings can match many words, cargo sounds can be read many ways, and medical logs are common science fiction framing, so the method limits are high. Until a Blizzard owned channel reposts a clue, links the puzzle from StarCraft social accounts, or adds matching text inside the StarCraft 2 client, the second transmission stays in the rumor file with Kerrigan as a fan guess only.

2. Rumored 60 to 70 Year Jump After Legacy of the Void

According to Enduins reporting dated September 7, 2026 by Sai T., console timestamp data linked to the rumored puzzle is read by fans as placing events 60 to 70 years after Legacy of the Void, and that calculation is presented here as a fan decode only, not as a Blizzard posted timeline. The range matters because a 60 to 70 year gap would move the story well past the human life span of many Terran cast members from the 2010 to 2015 trilogy, while leaving room for long lived Protoss, altered humans, Zerg linked entities, and recorded messages to bridge the gap. Enduins on September 7 is the attributed source for the timestamp observation and for the glitch effects said to surround the official site presentation, while the 60 to 70 year math itself is attributed to fan readers working from console output, not to a Blizzard lore article. No Blizzard timeline page, campaign text, novel excerpt, or cinematic is cited in the supplied details as confirming that jump. The range should therefore be read as a clue string with a proposed solution, not as a new canon date.

According to the context supplied, Legacy of the Void shipped in 2015 and closed the Amon arc with Kerrigan elevated to a Xel Naga linked status and shown with Raynor in an epilogue beat, which is why a 60 to 70 year jump draws immediate lore debate. A jump of that size would require any rumored Kerrigan return to address what her elevated status means over decades, how Terran succession worked after Raynor era figures, what the Dominion and fringe colonies became, and whether Protoss and Zerg broods remained organized or scattered. None of those questions are answered by the timestamp clue alone, according to the reports described here. The Enduins September 7 report is said to focus on presentation and console data, not on answering lore mechanics. Fans fill the gap with theory, but theory is not source detail. Any graphic that lists faction leaders, colony names, or battle dates for the jump period should be treated as fan made unless it links back to a Blizzard domain with a matching post.

According to standard puzzle checking practice noted in prior alternate reality game coverage, timestamp clues need raw proof before lore use, including exact console lines, time zone handling, whether the numbers are relative offsets or absolute dates, and whether the site code sets them by script or pulls them from a server. The Enduins September 7 report is attributed here as noting console timestamps, but this article has no Blizzard confirmation that those numbers were placed by Blizzard or that they use Koprulu calendar logic versus Earth calendar logic versus simple puzzle counters. A 60 year read and a 70 year read can come from different anchor choices for when Legacy of the Void ends in story time, which itself is not fixed to a single Earth year in public lore summaries. Small anchor shifts change the landing window by years. Copy errors, reused code, placeholder values, and fan edited screenshots can also create false timestamps. For those reasons, this article merges the full 60 to 70 year jump discussion into this one section and keeps it flagged as decoded rumor only, to avoid spreading one end of the range as if it were the locked date.

According to the rumor status rules used through this post, the jump claim will stay unproven until one of three anchors appears on a Blizzard owned surface. First, a Blizzard news post that restates the date range in plain text. Second, an in client string or official video description that carries the same numbers with clear story context. Third, a live event page that resolves the puzzle code to a time and place with Blizzard branding and support article backup. Style alone, such as static, flicker, redaction bars, star maps, or typewriter text, does not prove origin, because those effects are widely available in web code. Until an anchor lands, readers should log the 60 to 70 year range as an interesting fan solution tied to Enduins September 7 console observations, not as a new StarCraft era.

3. GamesRadar Sept 7 Report by Anthony McGlynn and 8 Letter K Shipping Log

According to GamesRadar reporting dated September 7, 2026 by Anthony McGlynn, the second transmission includes a shipping log section that contains an 8 letter K string which some fans read as Kerrigan, and that read is presented here strictly as fan interpretation reported by GamesRadar, not as a decoded name confirmed by Blizzard. The shipping log framing matters because StarCraft Terran logistics text often uses manifests, vessel names, cargo weights, origin points, destination codes, and inspection notes, which give puzzle makers many slots to hide a name length clue without stating a name outright. An 8 letter length match is weak on its own, since many words have 8 letters starting with K in English and in transliterated lore terms, and redaction can force fits. GamesRadar on September 7 is said to report the clue without claiming it proves Kerrigan, which is the careful line this article keeps. The log is a reported clue artifact, not a cast list.

According to the same GamesRadar September 7 report attribution, the shipping log sits beside two other reported pieces, screeching cargo audio and a patient log, and fans combine all three into a single Kerrigan guess rather than relying on the K string alone. That combination still lacks a second factor that would lift a guess toward identification, such as a voice match, a DNA tag with a lore linked serial, a ship registry tied by prior canon to a Kerrigan era vessel, or a destination tied by canon to a known Kerrigan location. Shipping logs in puzzles often include misdirection entries, damaged lines, and partial manifests, so one clean 8 letter hit inside noisy text can be selection bias. Readers who see social posts that present the K string as solved should ask for the full raw log text, the exact line number, the character count method, and the list of other 8 letter K words that were ruled out and why. If that method note is missing, the decode should be treated as art, not as news.

According to the source hygiene standard applied here, the GamesRadar September 7 byline by Anthony McGlynn is the citation for the shipping log claim, and any repost that omits that outlet plus date should be treated as weaker. A screenshot of a manifest without a URL bar, without page source, without file hash where files are shared, and without a time stamp of first appearance cannot test origin. An official origin would show a trail back to a Blizzard owned account, domain, or client build with consistent metadata. No such trail is described in the supplied details as confirmed. The 8 letter K detail therefore stays tagged as a reported clue with a fan proposed solution. It does not show that Kerrigan returns, it does not show a new game, short, novel, or hero reveal, and it does not show a release window.

4. Reported Screeching Cargo Detail in Second Transmission

According to GamesRadar reporting dated September 7, 2026 by Anthony McGlynn, the second transmission includes cargo audio described as screeching, and fans link that sound texture to Zerg linked containment, but that link is presented here as thematic association only, not as species proof. Audio clues in alternate reality game style puzzles often use reversed speech, slowed calls, filtered static, container rumble, alarm beds, and animal like shrieks to suggest a live specimen without showing it. Screeching can read as Zerg to a StarCraft fan, yet similar processing can make human screams, metal stress, brake noise, bird calls, or synth sweeps sound creature like. Without a raw file, a spectrogram, a speed and direction note, and a chain back to an official upload, the sound cannot identify cargo. The GamesRadar September 7 report is the attribution for the existence of the audio beat in the clue chain, not for a laboratory identification of what is inside the reported container.

According to the limits described for audio decodes, three checks would be needed before cargo sound could support a Kerrigan theory, and none are described as passed in the supplied details. First, a clean file with hash and upload trail back to a puzzle source with history, so editors can rule out a fan remix of old Zerg audio from Heart of the Swarm era cinematics or multiplayer voice packs. Second, a documented transform chain that shows what was reversed, stretched, filtered, or layered to reach the claimed phrase or match, with settings others can repeat. Third, a control comparison against known StarCraft audio plus common stock effects to test uniqueness. Old Zerg screams, Hydralisk hisses, Brood Lord calls, and Changeling cues are widely ripped and reposted, so a match to memory proves familiarity, not new origin. Until those files and notes are public and tied to a Blizzard anchor, screeching cargo stays as mood, not as evidence of who or what is shipped.

According to the combined clue logic reported by GamesRadar on September 7, some fans stack the screeching cargo with the 8 letter K shipping log to argue for a contained Kerrigan linked entity, but stacking two weak reads does not make one strong read. A manifest initial plus a spooky sound can fit many science fiction plots, including a new specimen, a smuggled hybrid, a feral brood, a Dominion experiment, a Umojan archive, or a pirate trap. The StarCraft setting is rich with contained threats beyond Kerrigan, from lab grown strains to Protoss artifacts that emit sound under stress. The report attribution does not narrow the field to one person. Readers should therefore log cargo audio as an unsolved texture clue from the September 7 GamesRadar report window, keep alternative explanations open, and avoid sharing captioned clips that label the sound as Kerrigan without marking the label as guess.

5. Reported Patient Log Detail in Second Transmission

According to GamesRadar reporting dated September 7, 2026 by Anthony McGlynn, the second transmission includes a patient log section, and some fans read medical observation framing as support for a Kerrigan containment or recovery story, but that story use is presented here as speculation only. Patient logs are a common puzzle device because they allow redacted names, vital signs, sedation notes, restraint checks, psionic field readings, visitor logs, and doctor initials, all of which can hide initials, dates, and counters without naming a subject. A redacted patient can be anyone in lore, or a new person created for the puzzle, or no one, if the log is set dressing. No performer credit, no script page, no motion capture note, and no new model still is cited in the supplied details as tying the reported patient to Kerrigan. The GamesRadar September 7 report is the attribution for the log beat, not for a medical identification.

According to careful reading practice, patient logs invite overread because short codes match many names, vital numbers match many states, and dates can be puzzle counters rather than story dates. An 8 letter redaction bar can hide Kerrigan, but it can also hide another 8 letter word, a vessel name, a drug name, a doctor name, or a fake entry. Psionic field language would feel Kerrigan adjacent to fans, yet psionics in StarCraft also cover Ghosts, Spectres, Protoss Templar, and hybrid experiments, so the field alone does not single out one woman last seen in 2015. Sedation and restraint language would feel containment heavy, yet containment is standard for many Zerg linked plots. Without exact quoted lines, line breaks, redaction widths measured against candidate words, and the full log with file source, the patient remains an unnamed reported subject. Any post that fills the redaction with Kerrigan in plain text without showing measurement method is adding detail not in the source report.

According to the tracking method recommended through this article, readers should save the exact patient log text as quoted by GamesRadar on September 7, note what is redacted versus what is legible, and keep a separate list of fan guesses with reasons. Useful fields are source URL, archive link, first seen time, quoted text, redaction counts, audio file hash if audio is attached, and which account posted it first. If later puzzle batches add a doctor name with a lore history, a facility name with canon coordinates, or a visitor log with a known call sign, those additions can be compared line by line. Until then, the patient log stays as a reported flavor document inside a rumored puzzle. It does not show that Blizzard wrote it, it does not show that the patient is Kerrigan, and it does not show a new campaign, co op commander, short film, or book.

6. Enduins Sept 7 Report by Sai T. on Glitch Effects and Console Timestamps

According to Enduins reporting dated September 7, 2026 by Sai T., the rumored puzzle window included glitch effects on the official site plus console timestamp clues read as 60 to 70 years after Legacy of the Void, and both observations are presented here as reported web behavior plus fan decode, not as Blizzard confirmation of a new story. Glitch effects in this context mean visual flicker, text scramble, image tearing, scan lines, rapid style swaps, or hidden layers revealed through developer tools, according to the report attribution. Those effects are easy to stage with style sheets and scripts, and they are also easy to misread when a site pushes a normal redesign, an A to B test, a broken asset, or a cached style conflict. The Enduins September 7 report is the citation for saying effects were seen, not for saying Blizzard placed them as lore. A video of flicker without network proof, page source, and console export cannot test authorship.

According to the supplied details, the stronger Enduins September 7 contribution is the console timestamp note, because console lines can carry numbers that fans convert to story years. That conversion still needs method transparency. Readers should ask which console lines were used, whether they were warnings, logs, or custom prints, what time zone and epoch were assumed, whether numbers were hex or decimal, and whether the same numbers appear in normal site code outside the puzzle window. If the site uses a countdown library, a build hash that looks date like, or a cache buster that looks code like, those strings can mimic lore dates. The report attribution does not resolve those alternatives with proof. This article therefore treats console timestamps as an interesting reported observation from Enduins on September 7 with a fan proposed 60 to 70 year solution, not as a timeline reveal.

According to origin testing logic, site clues need a Blizzard anchor before lore use. An anchor would be a link or repost from a Blizzard owned StarCraft account, a news post on a Blizzard domain that points to the puzzle, an in launcher banner with matching art, or identical strings inside the StarCraft 2 client with clear context. None of those anchors are described in the supplied facts as confirmed. Anyone can copy official style, reuse Protoss glyphs, Terran radio phrasing, Koprulu sector names, and static bursts. Style match alone is not authorship proof. Until an anchor appears, the Enduins September 7 glitch and console notes should be logged with links, times, page source snapshots, and console exports, and the Kerrigan jump theory built on them should stay labeled as fan reading of a rumored puzzle.

7. Kerrigan 11 Year Absence Since 2015 Epilogue With Raynor as Reported Context

According to series history cited in the supplied context, Kerrigan was last seen in a new story beat in the Legacy of the Void epilogue in 2015 with Raynor, which makes September 2026 an 11 year gap without a new appearance, and that gap is presented here as timeline context, not as proof that a return is now planned. The epilogue beat closed the Amon arc with Kerrigan in an elevated Xel Naga linked state and a quiet reunion note with Raynor, after the Queen of Blades arc across the original game plus Brood War and the Kerrigan focused Heart of the Swarm in 2013. An 11 year absence explains why fans react strongly to any K initial, containment sound, or patient redaction. Absence raises attention, but attention does not create evidence. No new cinematic still, voice session, novel page, comic panel, or game credit is cited here as showing Kerrigan in new material. The return idea remains a fan hope attached to weak clue fits.

According to lore risk notes relevant to a rumored return, Kerrigan reads fast in one frame, which helps rumors spread and also makes false spots easy. Red hair, chitin tones, wing blades, psionic glow, and Zerg flesh palettes can be mimicked with fan edits, cosplay lighting, old cinematic recuts, custom game models, and AI upscales of 2015 footage. Many supposed sightings in past Blizzard rumor cycles proved to be reused assets once frame comparison, reverse image search, and upload trail checks were done. The September 7 reports described here do not include a claimed clear face or body render, only text and audio plus site effects. That thin visual base makes a Kerrigan identification claim weaker than a normal character tease, which would usually leak as a high resolution still, a rigging test, a texture pass note, or a performer hint. No such item is attributed to either GamesRadar or Enduins on September 7 in the supplied facts.

According to story stakes often raised when Kerrigan trends, a return after 11 years plus a rumored 60 to 70 year jump would force large questions about mortality, succession, memory, and power scale, but those debates do not test the clue. Whether Raynor era Terrans could appear by recording only, whether a Xel Naga linked Kerrigan would still use ships and hospitals, why a near godlike figure would need cargo containment or sedation, and how Primal Zerg links would persist over decades are all fair lore questions, yet they assume the rumor is true. The supplied reports do not answer them because the source material is too thin. This article keeps the 11 year gap and the 2015 Raynor epilogue as agreed backdrop for why the rumor matters to fans, while keeping the return itself tagged as not proven. A real return would need Blizzard direct detail with title, format, and date, not a K initial plus sound texture.

8. First Rumored ARG Since 2013 Heart of the Swarm Plus July Patch Context

According to the background supplied for this article, the current puzzle is described as the first StarCraft alternate reality game style effort since the Heart of the Swarm campaign in 2013, and that 13 year gap is presented here as reported context for fan excitement, not as a Blizzard confirmed series. The 2013 Heart of the Swarm alternate reality game is remembered for spread clues across sites, videos, and social posts with Kerrigan linked texture, which is why longtime fans compare the September 2026 shipping log plus audio plus site glitch pattern to that older playbook. A format match across 13 years can feel persuasive, but puzzle formats are public and reusable, so a new actor can copy the old beats without Blizzard involvement. No Blizzard retrospective post, archive page, or press note is cited here as linking the 2013 run to the 2026 clues by authorship. The first since 2013 label should therefore be read as fan framing of scale, not as a confirmed Blizzard series count.

According to the same background, StarCraft 2 received a surprise patch in July 2026, and some fans treat that update as context that Blizzard still touches the game, but a maintenance patch does not prove an alternate reality game or a Kerrigan reveal. Surprise patches for old games often cover stability, launcher compatibility, map pool rotation, balance tuning, exploit fixes, or platform compliance, without story content. The July patch is noted here because timing proximity fuels speculation ahead of the September 7 second transmission, yet proximity alone is not authorship. A real link would need patch strings, data mined audio, or image assets that match the September clue text, audio hashes, or site code, with file paths and version numbers others can check. No such match is described in the supplied details as confirmed. Until data miners publish matching hashes with build numbers, the July patch stays as separate maintenance context, not as puzzle proof.

According to cautious tracking practice, the 2013 comparison and the July patch should be logged apart from the Kerrigan decode, so one thread does not prop up the other. Useful separation is simple. Thread A is puzzle history, with the 2013 Heart of the Swarm alternate reality game as the last large scale example remembered by fans. Thread B is client health, with the July 2026 surprise StarCraft 2 patch as evidence of ongoing support only. Thread C is the September 7 second transmission with shipping log, screeching cargo, patient log, glitch effects, and console timestamps. Thread D is the Kerrigan name guess built on Thread C. Only Thread C plus a Blizzard anchor could lift Thread D. Threads A and B explain why fans pay attention, but they do not test Thread C origin. Any post that says a July patch proves September clues, or that 2013 format proves 2026 authorship, is adding a link not present in the source reports.

9. Table 1 Transmissions and Table 2 Rumor Tracker With Nexon and Shooter Context

According to the context supplied for this article, talk of a Nexon deal and talk of a StarCraft shooter linked to Jason Schreier reporting background circulate near the puzzle, but both are flagged here as separate rumor context, not as proof of the alternate reality game or of Kerrigan. The Nexon deal chatter concerns possible Blizzard collaboration or publishing scope in Asia, as often discussed in business rumor coverage, while the shooter background concerns long running fan interest in a StarCraft shooter plus Schreier linked reporting notes about shooter exploration, according to the supplied framing. Neither thread includes in the supplied facts a Blizzard product page, a trailer, a job post naming a StarCraft shooter team, or a contract filing that ties puzzle clues to a game. Business talks can be real while a fan puzzle is fake, a shooter can be explored while clues are unrelated, and a puzzle can be official while business talk is wrong. This article keeps all three in separate rows so readers do not merge them into one assumed reveal. The tables below enforce that separation with outlet plus date on every row and rumor status on every claim.

Table 1: Reported Transmissions in Rumored StarCraft Puzzle Chain

Transmission	Date Window	Attributed Outlet	Reported Content	Status
First transmission	Before Sept 7, 2026	Fan chain cited as setup for Sept 7 reports	Early coded tease that set puzzle expectations	Rumor, no Blizzard anchor cited
Second transmission shipping log	Sept 7, 2026	GamesRadar by Anthony McGlynn Sept 7	Manifest text with 8 letter K string read by fans as Kerrigan	Rumor, name read is fan interpretation
Second transmission cargo audio	Sept 7, 2026	GamesRadar by Anthony McGlynn Sept 7	Screeching sound described as contained cargo	Rumor, species ID not proven
Second transmission patient log	Sept 7, 2026	GamesRadar by Anthony McGlynn Sept 7	Medical observation text with redactions	Rumor, subject ID not proven
Second transmission site effects	Sept 7, 2026	Enduins by Sai T. Sept 7	Official site glitch effects plus hidden layers	Rumor, authorship not proven
Second transmission timestamps	Sept 7, 2026	Enduins by Sai T. Sept 7	Console numbers read as 60 to 70 years after Legacy of the Void	Rumor, date math is fan decode

According to the table logic above, the second transmission looks dense because it mixes three GamesRadar reported text plus audio beats with two Enduins reported web beats, but density does not equal authenticity. A coordinated fan team can release text, audio, and site mirrors on the same day to mimic an official drop. The table keeps the first transmission vague because the supplied facts focus on the second transmission detail, and filling in first transmission specifics without a cited outlet plus date would add unsourced detail. Readers should use Table 1 to check that any new post they see maps to one of these six rows with matching outlet plus date. If a post adds a new row such as a third transmission, a video file, or a coordinate drop without outlet plus date and raw file, that addition should be logged as a new unproven claim, not as part of the September 7 set.

Table 2: Rumor Tracker for Kerrigan Return and Adjacent Claims

Claim	Attributed Source	Date	What Was Reported	What Is Missing	Status
Kerrigan returns after 11 years	Fan read of Sept 7 clues, via GamesRadar and Enduins reports	Sept 7, 2026	8 letter K plus cargo plus patient themes linked by fans to Kerrigan	Image, voice credit, model, script, Blizzard name post	Rumor
Story jumps 60 to 70 years after Legacy of the Void	Fan decode of console data noted by Enduins by Sai T.	Sept 7, 2026	Timestamp numbers converted to post 2015 story years	Raw console export, epoch method, Blizzard timeline post	Rumor
First ARG since 2013 Heart of the Swarm	Background context supplied for puzzle scale	2013 to Sept 2026	Format comparison to 2013 Kerrigan linked clue run	Blizzard link between 2013 run and 2026 clues	Rumor context
July 2026 SC2 patch points to puzzle	Timing context supplied	July 2026	Surprise StarCraft 2 patch shows ongoing support	Matching strings, hashes, assets tied to Sept clues	Rumor context
Nexon deal ties to StarCraft future	Business chatter context flagged as rumor	2026 chatter	Talk of Nexon linked Blizzard collaboration scope	Contract, filing, Blizzard plus Nexon joint post	Rumor context
StarCraft shooter in work per Schreier background	Shooter exploration background flagged as rumor	Prior reporting background	Notes on shooter exploration interest plus Schreier linked background	Title, studio, trailer, job post naming StarCraft shooter	Rumor context

According to the separation enforced in Table 2, the Kerrigan return row and the 60 to 70 year jump row are direct fan decodes of September 7 clues, while the last four rows are context that explains excitement without proving origin. The first since 2013 row explains format memory. The July patch row explains client attention. The Nexon deal row explains business hope. The shooter background row explains genre hope. None of the four context rows test whether Blizzard wrote the shipping log, rendered the cargo audio, staged the glitch effects, or set the console numbers. Merging business or shooter hope into the puzzle as if one proves the other is the most common error in comment threads, according to prior rumor cycle patterns. Keep each row on its own proof. A Blizzard anchor for the puzzle would move rows one and two first. A Blizzard business post would move row five alone. A Blizzard game reveal would move row six alone. Until those posts appear, all six stay as rumor or rumor context.

10. FAQ Six Questions on Proof Status and Next Checks

1. Did Blizzard confirm the second transmission or Kerrigan on September 7 according to the sources cited

No, according to the attributions used here. GamesRadar on September 7 by Anthony McGlynn is cited for reporting the shipping log with an 8 letter K string, screeching cargo audio, and a patient log as puzzle clues with fan reads. Enduins on September 7 by Sai T. is cited for reporting official site glitch effects and console timestamps read as 60 to 70 years after Legacy of the Void. Neither attribution includes a Blizzard confirmation line, a signed news post, an in client string with context, or a press note naming Kerrigan. Treat confirmation status as zero until a Blizzard owned channel posts direct detail.

2. Does the 8 letter K shipping log prove Kerrigan according to GamesRadar September 7

No, according to the careful line kept here. GamesRadar on September 7 by Anthony McGlynn is cited as reporting the log and noting the fan read, not as declaring the name solved. An 8 letter length match starting with K fits Kerrigan, but it also fits many other words, codes, and names, especially inside noisy manifest text with damage and redaction. Proof would need the full raw log, exact line citation, count method, ruled out alternatives, plus a second factor such as a lore tied registry, voice match, or Blizzard name post. None of those are cited as present. Keep the K string as an unsolved length clue with one popular guess.

3. What would prove the 60 to 70 year jump noted by Enduins September 7

According to the checks listed in section 2, proof would need a raw console export with exact lines, a stated epoch and calendar assumption, hex versus decimal handling, time zone handling, and a showing that the numbers come from puzzle script rather than build hashes, cache busters, or test code. After that, proof would still need a Blizzard timeline post that restates the range in story terms. Enduins on September 7 by Sai T. is cited for the observation of glitch effects and console numbers, while the 60 to 70 year math is cited as a fan decode. Style, flicker, and static do not prove authorship. Log the range as a proposed solution, not as canon.

4. Why do 11 years since 2015 and first since 2013 matter if they do not prove anything

According to the context sections, the 11 year gap since the Legacy of the Void epilogue in 2015 with Raynor explains why Kerrigan rumors move fast, and the gap since the Heart of the Swarm alternate reality game in 2013 explains why fans compare clue formats across 13 years. Both points are backdrop for attention, not tests of origin. A long absence raises stakes for fans who waited since 2015. An old puzzle memory gives a template for reading shipping logs, audio, and site effects. Neither backdrop shows who wrote the September 7 clues. The July 2026 surprise StarCraft 2 patch is similar context. It shows the client still receives care, but without matching hashes or strings it does not link to the puzzle.

5. Do Nexon deal talk and shooter talk make the ARG more likely according to this article

No, according to the separation kept in Table 2. Nexon linked business chatter and StarCraft shooter exploration background linked to Schreier notes are flagged here as separate rumor context. Business talks, publishing scope rumors, and genre exploration notes live on different proof tracks from puzzle authorship. A company can explore a shooter while fans make a puzzle. A publisher can discuss collaboration while clue audio is fan made. This article keeps those threads apart with rumor status on each. Do not use a business rumor to authenticate a K string, and do not use a cargo sound to confirm a shooter title. Each needs its own Blizzard direct post.

6. How should readers track this rumor without spreading false detail

According to the method recommended through this post, save each September 7 link with outlet plus author plus date, specifically GamesRadar September 7 by Anthony McGlynn and Enduins September 7 by Sai T., quote exact clue lines instead of paraphrased solves, mark every share as rumor in the first line, and keep raw files with hashes where files are shared. Ask for method on every decode, including full log text, audio transform settings, console exports, and ruled out alternatives. Watch for a Blizzard anchor such as a repost from StarCraft accounts, a news post on a Blizzard domain, launcher art with matching code, or client strings with version numbers. If no anchor appears, keep the second transmission, the 60 to 70 year jump, and the Kerrigan guess in the rumor file and revisit only when new sourced detail lands.

Bottom line as rumor only: according to GamesRadar on September 7 by Anthony McGlynn, the reported second transmission carries a shipping log with an 8 letter K fan read plus screeching cargo plus a patient log, and according to Enduins on September 7 by Sai T., the same window carries reported site glitch effects plus console timestamps read by fans as 60 to 70 years after Legacy of the Void, with a rumored Kerrigan return after 11 years since the 2015 epilogue with Raynor framed as fan guess, with first since 2013 Heart of the Swarm scale plus July 2026 patch care plus Nexon deal plus shooter background kept as separate rumor context, and with no Blizzard confirmation cited for any row.

Sources: GamesRadar September 7, 2026 by Anthony McGlynn for shipping log with 8 letter K plus screeching cargo plus patient log; Enduins September 7, 2026 by Sai T. for official site glitch effects plus console timestamps read as 60 to 70 years after Legacy of the Void; series context for Legacy of the Void 2015 epilogue with Raynor and 11 year gap to 2026; puzzle context for first alternate reality game since Heart of the Swarm 2013; client context for July 2026 StarCraft 2 surprise patch; business and genre context flagged as rumor for Nexon deal talk and shooter exploration background linked to Schreier notes.

Labels: Blizzard