Why the former item-level lookup was removed
The old calculator marked three different The War Within seasons active at the same time, attributed an unlinked 2025 item-level JSON to Blizzard, and used third-party summaries for fixed Bountiful and Vault values. It then averaged two item levels and labeled the midpoint “EV,” while assuming every run lasted ten minutes. Item level is not a probability-weighted value, and a fabricated source label does not make an old table official.
Current official context is different
Blizzard's Midnight Season 1 schedule says Delves Tier 8+ opened with the season and reminds players to check the Great Vault weekly. Blizzard's 12.0.5 preview says the World-content row includes Delves alongside Prey and Ritual Sites. The Journeys overview explains that Delves tracking moved into Journeys and links that progression area with Great Vault access. These are current structural facts, but they do not provide a timeless three-threshold or item-level table for LootCalc to preload.
Blizzard: Midnight Season 1
Blizzard: 12.0.5 content preview
Blizzard: Journeys overview
Capture the live progress boundary
Record expansion, season, client patch, region, and verification time. Open the current Journeys or Great Vault interface and copy the World-row progress, all three thresholds, and the amount of qualifying credit the chosen Delve and tier grants. The labels in the planner preserve that context but never select data. If the UI changes, create a new shared scenario instead of relabeling the old one.
Keep existing mixed progress separate from the Delve plan
Current World-row progress can already include eligible sources outside Delves. Enter that combined amount once in current progress. The plan then adds only the qualifying Delves you intend to complete, multiplied by the currently observed credit per Delve. Do not add planned Prey or Ritual Site credit unless you expand the scenario and label it accordingly.
How slot projection works
Progress added by the plan equals planned qualifying Delves multiplied by progress units per Delve. Projected progress adds that amount to current progress. A slot is marked unlocked when the relevant total meets or exceeds its user-entered threshold. Runs needed from current progress use the ceiling of remaining units divided by current units per qualifying run. Thresholds must be strictly increasing so Slot 1, Slot 2, and Slot 3 cannot contradict each other.
Timing describes throughput, not reward quality
Full batch time divides into minutes per planned Delve and planned Delves per hour. Include travel, setup, queues, loading, combat, deaths, recovery, inventory work, and return to a comparable state. These rates do not say a faster Delve grants better loot, nor do they prove that a tier is optimal. They only describe the entered plan's time boundary.
What the planner deliberately does not calculate
It does not predict chest contents, call an item-level range expected value, assume Bountiful Coffer eligibility, price soulbound gear, model a boss-specific drop, or guarantee a reward choice. If Blizzard publishes a versioned numeric rule, it can be recorded as evidence; if the current UI displays a value, the user can preserve it as a note. Neither justifies inventing missing probabilities.
Save the evidence with the URL
Store a dated screenshot of the row, thresholds, qualifying-credit rule, activity/tier, and region beside the shared URL. Log actual completed and failed runs separately from a plan. The evidence-first Delves progress guide provides a full review checklist and an empty log schema.