Why the model starts with live inputs
Helltide values are version-sensitive. Blizzard's Diablo IV 1.5.0 notes provide a concrete historical example: specified Tortured Gift chests in World Tiers I and II changed from 100 to 75 Cinders. The same notes changed reward access and seasonal behavior. Blizzard's consolidated patch-notes page later states that Helltide chest rewards were improved, without publishing a reusable numeric expected-value table. Those official records establish that costs and rewards move; they do not authorize LootCalc to reuse one historical number as a current default.
Blizzard: consolidated Diablo IV patch notes
Blizzard: Diablo IV 1.5.0 patch notes
Step 1: freeze the exact game state
Before calculating, record the season or patch shown by the client, your difficulty or activity state, and the time at which you verified the options. Then copy each visible cinder cost into the form. The season field is a provenance note only: changing its text cannot silently replace the numbers. If a hotfix changes a cost, save a new URL rather than relabeling the old scenario.
Step 2: define a complete cinder budget
Cinders on hand and additional cinders planned form the scenario budget. The planned amount is your own target or measurement, not a rate supplied by LootCalc. Enter zero if the plan concerns only resources already held. Enter a positive amount only when the same session boundary includes earning those resources. The result reports either remaining cinders or an explicit shortfall; it never reduces your planned counts to make an over-budget scenario appear feasible.
Step 3: label two options without importing a loot table
Option A and Option B may be any two currently visible choices you want to compare. Their labels have no executable meaning. A label such as “armor option” does not load an armor table, and a label copied from a guide does not prove that the option still exists. Enter the current per-opening cost and the whole-number count you intend to open. The maximum-openings figures are simple budget divisions, not recommendations.
Step 4: keep the value unit honest
A value can be a personal utility score, a current externally derived price, or a measured average from a real log. Whichever you choose, use one unit and one inclusion boundary for both options. If salvage value, crafting materials, or retained gear count for one option, handle the same categories for the other. A “10” and a “4” are comparable only when they mean the same thing. The example values in the form demonstrate arithmetic and make no claim about Diablo IV rewards.
Step 5: measure the whole session
Value per hour is especially easy to inflate with mismatched clocks. Start before the resource-earning loop and stop only after opening, collection, town or stash work, loading, deaths, recovery, and return to a comparable state. If the budget uses cinders earned over an hour but the time field counts only seconds spent opening, the resulting hourly value is not a valid end-to-end rate. Keep both resource and time boundaries aligned.
How to read the output
Planned spend is the sum of each current cost multiplied by its planned openings. Total scenario value is the sum of each user value multiplied by its count. Weighted value per cinder divides the total user value by planned spend; per-option values divide each option's user value by its current cost. Value per hour divides the scenario value by the complete session duration. None of these transformations discovers a drop rate, predicts a unique, prices an account, or guarantees that an opening will match an average.
Save evidence beside the share link
A shared URL preserves the entered assumptions, but not the in-game screen that justified them. Store a dated screenshot or note with the exact patch, costs, value method, excluded rewards, session boundary, and who measured it. The evidence-first Helltide planning guide contains a blank review log and comparison checklist.