Explore a hypothetical November fixture, not the official September 12–13 program. Select wishlist blocks, compare durations across timezones, scrub the example timeline, and export its assumptions.
Toggle authored wishlist blocks to compare how entered durations change the example timeline.
| Time | Segment & Content | Duration |
|---|
Which times are official event information, and which are calculations from this planner’s fixture?
Blizzard’s published 2026 program places BlizzCon on September 12–13 at the Anaheim Convention Center, with the Opening Ceremony beginning at 10:30 a.m. PDT. This planner deliberately retains a different hypothetical start: November 6, 2026 at 11 a.m. Pacific standard time. Use its editable blocks to explore duration and timezone arithmetic, then consult the official program for actual sessions.
The November start, block lengths, running order and wishlist descriptions are authored examples. They are not GameSpot reporting, confirmed announcements, measured probabilities or a live stream. The countdown compares your device clock with the fixed example date; it updates when planner controls change, without a running timer, and does not check broadcast status or retrieve schedule updates.
The four active blocks last 25 + 20 + 25 + 20 = 90 minutes. Removing the 20-minute Diablo block reduces runtime to 70 minutes and moves all later blocks 20 minutes earlier. Adding a 15-minute custom block then produces 85 minutes. In the example’s Pacific zone, the end changes from 12:30 p.m. to 12:25 p.m.; these are hypothetical times, not Blizzard’s published program.
Blizzard’s published guide provides the actual program and notes that times and programming may change. It lists free livestream viewing and links its official channels, with programming varying by channel. Use that source to identify the appropriate session or replay rather than treating these wishlist titles as announcements. Blizzard: 2026 program and viewing guide
The fixed ISO start 2026-11-06T11:00:00-08:00 represents 19:00 UTC. In New York it formats as 2 p.m. that day; in Tokyo it is 4 a.m. on November 7. The timezone menu changes the displayed local representation, not the underlying start instant. A local date may therefore differ from the Pacific date.
Intl.DateTimeFormat uses the selected named timezone and the date being formatted. Seasonal offsets depend on that date: September’s Pacific daylight time is different from the November fixture’s standard time. The displayed abbreviation comes from the formatter; timezone labels are not reliable fixed UTC offsets. MDN: Intl.DateTimeFormat
Selected catalogue blocks keep catalogue order; custom blocks append after them. Block widths are duration divided by total runtime. Moving the scrubber changes the highlighted example block and clock display; it does not seek a video, change durations or verify a reveal. At the total-duration endpoint the monitor still names the final block, even though no table row is highlighted.
The runtime includes only the entered blocks. It does not add breaks, transitions, delays or overlapping sessions. With no active blocks, runtime is zero and export readiness is false, but JSON download remains available to record that empty state.
The copied summary and JSON identify the fixed hypothetical start, selected zone, durations and wishlist blocks. They do not create calendar events, book attendance or validate official broadcast links. Export Ready means at least one block exists. Reset restores the four original blocks, Pacific display and scrubber minute zero; custom titles and durations still in the input form are not a saved schedule.
Published September event dates, opening time and official viewing links. Does not support the November fixture or invented blocks.
Date-specific timezone formatting; not event schedule verification.