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.
Suggested tracker columns
date,ledger,source,pack_label,count,paused,evidence,note YYYY-MM-DD,eligible-pack,level reward,visible pack name,1,false,screenshot URL, YYYY-MM-DD,uncertain,old promotion,unknown,1,false,,classification needed YYYY-MM-DD,collection,event,direct Mythic unlock,1,false,receipt URL,ledger only YYYY-MM-DD,collection,account,Shards balance,150,false,screenshot URL,ledger only
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
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.