Why the old season tables cannot remain active
The prior implementation simultaneously marked The War Within Seasons 1, 2, and 3 active. It loaded fixed item levels and weekly thresholds from Icy Veins and Method.gg labels, plus an unlinked JSON whose metadata simply said “Blizzard Entertainment.” It also treated the average of two item levels as expected value. Those are different factual and mathematical errors; changing the default season would not repair them.
What Blizzard's current pages establish
The Midnight Season 1 schedule identifies Delves Tier 8+ and weekly Great Vault rewards. The 12.0.5 preview says the World-content row includes Delves alongside Prey and Ritual Sites. The Journeys overview describes changed progress-tracking placement and Great Vault access. These sources establish current structure and volatility, but they do not expose a permanent numeric lookup table for LootCalc.
Blizzard: Midnight Season 1
Blizzard: 12.0.5 content preview
Blizzard: Journeys overview
What the planner can establish
Given current progress, planned qualifying Delves, current credit per run, strictly increasing slot thresholds, and full batch time, the planner can calculate projected progress, before-and-after unlocked slots, remaining units, runs needed from the current state, minutes per planned run, and planned runs per hour. Every result is a direct transformation of a visible input.
What the planner cannot establish
It cannot predict an item, assign item level from a tier name, prove Bountiful eligibility, estimate a boss-specific drop rate, price soulbound gear, or select an optimal tier. A progress slot is not itself a guaranteed item outcome. Reward details must be read from the current client or a suitable versioned Blizzard source, and any missing probability must remain missing.
The minimum evidence packet
- expansion, season, patch, region, character state, verification date, and time;
- a screenshot of current Journeys or Great Vault World-row progress and all three thresholds;
- the exact Delve, tier, and current rule showing qualifying credit per completion;
- planned completions and the treatment of failed, abandoned, or non-qualifying runs;
- the complete time boundary, including setup, loading, deaths, recovery, and inventory work;
- the shared URL and a new record whenever an update changes any rule.
Why three older articles were consolidated
The old Delves articles repeated fixed thresholds, stale item levels, invented gold-equivalent EV, fake run rows, route archetypes, and prescriptive tier rankings. One page even linked through a historical two-hop redirect. They now resolve directly to one current-UI workflow, removing both content duplication and the false impression that multiple pages independently verified the same unsupported values.