Heirloom Shards Math After Cross-Progression: How to Merge Counts, Track Ticks, and Avoid Resetting Pity
Cross-progression is the easiest way to nuke pity by accident. This guide shows how to merge PC/console counts, track loot ticks, and keep your 500-pack tracker correct with the Heirloom Tracker and Pack Probability Calculator.
Cross-Progression Heirloom Math: Keep the Higher Pity
When Apex merges accounts, only one pity counter survives. Always keep the higher pack count plus the higher base rate (PC) to preserve expected value. Document both counts before the merge; once support asks for proof, your screenshots and logs are your only leverage.
Merge protocol (3 steps)
- Screenshot PC and console lifetime packs, loot ticks, recent drops.
- Export
data/apex/heirloom-log.csvor your personal copy with timestamps. - After merge, input the higher pack count into the Heirloom Tracker and zero the lower.
Why platform matters
PC base 1.1% > console 1.0%. With identical counts, PC yields ~+2–3% higher cumulative odds by pack 200.
Edge case: shards already spent
If pity triggered at 500 pre-merge, log the reset with proof so your new counter starts at 0 without dispute.
CTA
Use the Heirloom Tracker to pin the merged count and lock the new baseline.
Loot Ticks & Event Shards: +2% Bonuses and 150-Shard Collections
Loot ticks add +0.02 each; collection events add 150 shards—both can mask the pity timeline if unlogged. Treat each as a distinct column in your tracker so you never double count shards versus pity.
Data Snapshot – Heirloom Tracker Log (matches /data/apex/heirloom-log.csv)
date,platform,packs,ticks,shards,collections,notes 2025-03-10,PC,220,4,0,0,"Cross-progression merge" 2025-03-21,PC,340,6,120,1,"Collection event completed" 2025-04-05,Console,180,2,0,0,"Loot ticks from Twitch" 2025-04-18,PC,420,6,0,1,"Pity approaching" 2025-04-28,PC,500,0,0,1,"Pity triggered, shards spent"
How to log ticks
Channel “#loot-ticks”: add date, source (+2%), expiration, and screenshot. Remove expired ticks each day.
150-shard rule for events
Each finished collection = one guaranteed heirloom; never mix with pity math—keep a separate column.
Variance call-out
Ticks raise per-pack odds but don’t ensure shards early; communicate 50/75/90% ranges to teammates.
Avoid Resetting Pity: Governance for Squads
The easiest way to lose months of progress is a silent reset. Governance keeps squad spending honest and auditors satisfied when coins are pooled.
Assumptions
- 500-pack guarantee; pity resets only when shards are claimed
- Loot ticks are additive and logged per event
- Collection events add 150 shards but do not alter pity
- PC 1.1% vs console 1.0% base rates
Methodology (reproduce anytime)
All numbers in this article pull from data/apex/heirloom-log.csv + data/apex/pack-log.csv. We re-run the logs through the Heirloom Tracker to validate probabilities, then compare to real shard drops.
Worked example – midseason tracker
- Packs opened: 340 (PC)
- Loot ticks: 6 → +0.12
- Event shards: 120; collections: 1
- Probability ≈ 80%; pity remaining: 160 packs
Common mistakes
Resetting early, mislabeling event shards as pity, or losing screenshots post-merge.
Heirloom Probability Curve After Merge
Visualize two curves: pre-merge PC count vs console count; the merged line should start at the higher count and climb with ticks and events. Annotate the 500-pack line and any collection events that shortcut to shards.
Image guidance
Render a chart showing pack count on X-axis, cumulative shard odds on Y-axis, with markers for loot ticks and collection events. Include a callout “Start Here” at the merged count.
H5 loot tick banding
Shade plus/minus bands for 0, +0.2, +0.5 boosts to show range.
H6 CTA
Place a button linking to the Heirloom Tracker to rebuild the curve with personal data.
Risk note
Any reset breaks continuity; keep CSV and screenshots stored in cloud.
FAQ: Heirloom Shards Cross-Progression
Which pity count should I keep after merging?
The higher one, with proof; typically the PC count if odds are similar.
Do loot ticks survive cross-progression?
They do if the underlying event is active; log expirations explicitly.
Can I lose shards when merging?
Shards already claimed stay; pity progress can be lost if you reset packs—ensure support sees your log.
How do collection events affect pity?
They grant 150 shards independently; pity counter continues unchanged.
Do Prime/Twitch packs count?
Yes—log as packs so the tracker stays accurate.
Where to get the calculator?
Both the pack calculator and tracker live at LootCalc Apex tools.