All nine sessions, celebrity guests, hall themes and walking minutes are unverified examples. Consult Blizzard’s published program for actual events.
Can an example itinerary fit its entered sessions and walking assumptions without claiming they are official events?
This nine-session fixture illustrates schedule conflicts across four named halls. Select cards or presets to compare overlaps, allocated session hours and assumed travel minutes. Its celebrity names, session titles, hall themes and times are unverified scenario data. The published Blizzard program is the reference for actual events, not this fixture.
No booking, guest appearance, floor-plan route or live program is verified here. Walk times are authored pairwise assumptions, not measured journeys or accessibility advice. The conflict banner examines neighboring selected sessions in start-time order and displays only the first detected issue. A clean banner does not establish every possible overlap or practical feasibility.
The default four sessions allocate 90 + 90 + 75 + 120 = 375 minutes, or 6.25 hours displayed as 6.3h. The assumed hall transitions are 8 + 7 + 5 = 20 minutes. The gaps are 90, 90 and 75 minutes, each larger than its assumed walk. These totals exclude waiting, queues and breaks; they do not mean a 20-minute gap was reserved.
Blizzard’s published 2026 guide places the convention on September 12–13, with the Opening Ceremony in Hall D at 10:30 a.m. PDT. Its published show hours end at 7 p.m.; separate add-on events have their own locations and times. The example’s 7:30–9:30 p.m. celebrity closing set is therefore not evidence of an official program slot. Check the official schedule and viewing guide for actual sessions. Blizzard: Official 2026 program and viewing guide
Committed hours sums all selected session lengths, even when sessions overlap; it is not elapsed attendance time. Assumed walk minutes sums the transit matrix between adjacent selections, including impossible overlapping pairs. A same-hall transition is zero. Unknown hall pairs fall back to six minutes; the provided fixture uses its explicit matrix.
A time clash is reported when the current session ends after the next starts. Otherwise, a travel warning appears when the gap is smaller than the assumed transit time. These checks do not evaluate queues, crowding, seating availability or a participant’s travel needs. Cards are grouped by hall, rather than drawn to a common minute scale.
Auto-Resolve sorts selected sessions by start and keeps the first one, then retains later sessions only when their starts allow the previous retained session plus its walk. It does not search every combination, prioritize favorites, or maximize session count or utility. Ties keep the catalogue order. Review what was removed before accepting the suggestion.
For example, Dev & Lore initially selects the Warcraft keynote and Diablo lore session at 11 a.m., creating a clash. Automatic removal keeps the earlier catalogue entry, drops that Diablo session, and retains World of Warcraft System Design and Sanctuary Speedrunning. The remaining lengths sum to 255 minutes, displayed as 4.3h, with 10 assumed walking minutes.
JSON records the selected fixture sessions, including minute-of-day start/end values and their display strings. It has no event date or timezone, so those numbers cannot identify actual calendar instants. Its scope identifies the unverified fixture.
The ICS action downloads an incomplete, undated draft. Its VEVENT entries lack DTSTART, UID and DTSTAMP, so it is not a ready-to-import dated itinerary. RFC 5545 defines those event properties and requires UID and DTSTAMP; with no METHOD here, DTSTART is also required. Use JSON to review the fixture and establish real dates and timezones before preparing calendar events. RFC 5545: iCalendar event format
Published actual dates, opening ceremony, show hours and separate add-on context; does not support fixture guests or walks.
Calendar event property requirements; does not validate this incomplete draft export.