Maintain three ledgers
Confirmed eligible-pack progress
This is the only number used by the guarantee and probability model. Add a row only after identifying the actual pack type and confirming that eligibility was not paused.
Uncertain historical rewards
Old screenshots, remembered purchases, or rewards with an unknown pack label belong here. Keep a possible minimum and maximum if useful, but do not silently move the maximum into the confirmed total.
Collection history
Record event/direct Mythic unlocks and current Heirloom Shards balances for your own inventory history. The LootCalc tracker deliberately does not convert these values into pack odds or infer that every acquisition path resets the guarantee counter.
Start from a boundary, not a lifetime total
Open My records in the tracker. Choose your point estimate or finite range, explicitly confirm a fresh zero cycle, or leave older history unknown. Describe the opening boundary covered by that starting value. A record's acquisition source is useful context, but does not establish its pack type or whether eligibility was paused. Unknown facts remain pending instead of being converted to false or zero.
Demonstration: a backfill is not always an addition
This is an illustrative workflow, not a real player result. Starting at 240, recording 10 new eligible openings gives an estimate of 250. Backfilling 10 openings already included in the 240 does not change 250. With a starting range of 240–260, 10 not-included eligible openings instead produce 250–270. An unknown starting history plus 10 new openings still has unknown total history. Supplying a later baseline of 240 gives 250 only if that baseline does not already cover those 10.
Recording an award in the middle of a batch
Select the batch and the known position of its winning opening. In a batch of 10 with an award at 7, the preview keeps six before and one winning opening in the old cycle, and places three after in the next. Confirm any existing later batches moving with them. Do not guess an unknown boundary or infer the count from inventory reduction. Manual reorganization requires its own reason and is not an official reset.
An empty next cycle can be undone. Once later records exist, use the retained-record correction and review each record's relation to the previous baseline. The next starting estimate is not silently added to it. Collection records remain separate, and the latest dated Shards balance wins over older snapshots.
Saving, backup and clearing
Saved in this browser means the write succeeded in this browser profile, not that a cloud copy exists. Export JSON to preserve all records and cycles. Import validates, previews and replaces; it never merges duplicate rows. Before overwriting valid data, one recovery snapshot must fit and save successfully. CSV is only a readable export. The joint limits are 5000 pack/collection records, 200 cycles and 2 MiB of complete backup JSON, plus actual browser quota; long notes can exhaust the byte budget first.
A storage failure leaves the prior saved ledger intact. An unsaved session stays in memory and must be exported before closing. Unknown-version or damaged originals are preserved for raw download, which does not mean this version can restore them. Clearing removes the ledger, recovery copy and this tab's temporary/undo copies, with a nonpersonal invalidation marker preventing old tabs writing the data back. Clear does not delete unrelated storage or previously downloaded files. When another tab changes data, reload before saving; do not assume concurrent changes were merged.
Cross-progression without false arithmetic
Keep pre-merge platform notes, but do not add the two values or automatically choose the larger one. EA does not expose a public Heirloom counter that LootCalc can read, and public cross-progression information does not provide a general formula for reconstructing it. After a merge, use only a count supported by post-merge records or clearly label the value as uncertain.
When the tracker reaches 500
For a current waiting cycle, stop the probability calculation. Check whether excluded event packs were counted, whether eligibility was paused, and whether packs from an earlier cycle were included. The tracker must not use modulo arithmetic to turn 500 into zero or infer how many Shards awards occurred.