Hero and chart figures use the same default values as the Pack Probability Calculator — platform base rates, loot ticks, and refunds match the calculator defaults.
Apex Pack Probability Guide – Drop Rates, Loot Ticks, Battle Pass Refunds
Apex Legends has always been upfront about its loot drop rules, yet the majority of players only hear the marketing bullet point: “You are guaranteed heirloom shards every 500 packs.” That statement hides nuance. Platform-specific base rates (1.1% PC vs 1.0% console), seasonal boosts, loot tick bonuses, collection events, and Battle Pass refunds all distort how quickly you hit that guarantee. This guide translates those moving parts into practical models, screenshots, and governance rituals so you can budget with confidence.
We structure the guide around the calculators on LootCalc: the Pack Probability Calculator, the Heirloom Tracker, and the Battle Pass Planner. Each tool solves a slice of the grind, and together they create a complete picture—packs supply shards, trackers log pity, and the pass supplies coins you reinvest. Throughout the article we reference glossary entries for expected value, variance, and probability, ensuring readers can audit every term. We also link to our Methodology page so transparency is built in.
The remainder of this guide breaks down platform-specific drop rates, seasonal boost scenarios, refund budgeting, loot tick logging, event bundle ROI, and team communication. You will see tables that convert EA’s statements into practical workflows, charts that illustrate how an extra 50 packs changes the probability curve, and checklists for sharing data with your squad. The Data Sources & Limitations section explains where each number comes from and which values are estimates, so teammates can verify the reasoning.
Apex Pack Drop Rates & Seasonal Boosts
PC vs Console Probability Modeling
PC accounts enjoy a slight advantage, so start by choosing the “PC / Steam” table inside the calculator. Record your platform in the shared spreadsheet and tag cross-progression merges with the exact date the merge occurred. If you grind on multiple devices, treat each profile independently until Respawn finishes the migration, then copy the new lifetime packs into the calculator and reset the pity counter. Doing so prevents “phantom packs” from inflating your probability curve.
Seasonal Boosts, Loot Ticks & Refund Packs
Respawn occasionally bumps odds—Spellbound, Dressed to Kill, and Harbingers each added between +0.2% and +0.5%—and the calculator mirrors those boosts in a 0.1% slider so you can model the exact patch. Loot ticks are limited-time +2% bonuses; track them in a dedicated Discord channel (“/tick +2”) so your Seasonal Boost field always reflects reality, and remove the bonus after 24 hours if the event specifies a duration. Refund coins behave like free packs: enter 600 for a full pass or the coin value of a bundle (divide by 100 to convert to packs) so “free” packs purchased with coins still count toward the 500-pack pity tracker. Prime Gaming and Twitch drops count toward total packs too, and every collection event supplies 150 shards—decide whether those shards replace your pity plan or simply accelerate the timeline, then update the tracker accordingly.
Keeping the Numbers Honest
Use the Glossary definitions for expected value and variance to set expectations with teammates: the probability curve describes the long run, and short droughts are still possible, so communicate that up front. Document source links in your governance doc to show where each boost originated, and store receipts, screenshots, and calculator exports in a shared folder. When someone questions the numbers, you can link directly to the evidence.
Example Tracking Sheet
Here is the row format we recommend for a squad pack log — date, platform, packs opened, loot ticks, refunds, and whether shards dropped. Copy it into Google Sheets or Airtable as a starting template.
date,platform,packs,ticks,refundPacks,shards,notes 2025-03-12,PC,122,4,6,false,"Seasonal boost +0.3%" 2025-03-20,Console,210,2,12,true,"Shards on pack 210" 2025-04-02,PC,340,6,8,false,"Cross-progression merge" 2025-04-15,PC,410,6,10,false,"Event + twitch drops" 2025-04-28,PC,500,0,0,true,"Pity trigger"
Recreate this example in the calculator: enter packs=340, ticks=6, refunds=8 on PC for ~80% shard odds; pity due at 500. Use cross-progression merge if platform changed mid-season.
Data Sources & Limitations
Base rates come from EA Help articles, seasonal boosts from official patch notes, and both are cross-checked against large community-run pack datasets and verified creator streams. One important limitation: Respawn rarely discloses the precise loot tick formula, so we treat each tick as an additive +0.02 — a community-standard estimate, called out as an assumption in the calculator’s tooltip. If Respawn publishes official numbers, we will update the model and note it in the changelog below.
The Math Behind the Guide
Assumptions: 1.1% PC base rate and 1.0% on console, pity triggers at 500 packs, loot tick bonus of +0.02 per tick, a Battle Pass refund equal to 600 coins, and promo bundles converting coins to packs at 100 coins per pack.
const base = platform === 'pc' ? 0.011 : 0.01; const boost = base + seasonalBoost / 1000; const total = packs + eventPacks + refundCoins / 100; const probability = total >= 500 ? 1 : 1 - Math.pow(1 - boost, total); const pityRemaining = Math.max(500 - total, 0);
Worked example: plan to open 120 purchased packs, 30 event packs, and earn 6 refund packs. On PC with a +0.3% boost, probability = 1 − (1 − 0.014)^156 ≈ 88%. Pity remains 344 packs away, meaning you either continue saving or accept that you may not hit shards that season. Edge cases—cross-progression merges, missing refunds, double XP weekend logins that grant unexpected packs, and limited-time store bundles—should be documented so you can override inputs immediately and keep projections honest. Watch for the common budgeting mistakes too: resetting pity late, double-counting Twitch drops, ignoring platform base rates, assuming event bundles bypass pity, or failing to communicate the variance of RNG. Address them using the checklist below.
Actionable Checklists & Governance
Use these steps to align your squad before each season.
- Export lifetime pack counts from each account and confirm with screenshots.
- Set a seasonal budget, entering planned purchased packs, event packs, and refund packs into the calculator.
- Screenshot the calculator output, annotate the seasonal boost and loot tick assumptions, and post it in Discord.
- After every loot tick or bundle purchase, update the Seasonal Boost and Event Pack fields to keep the plan accurate.
- When pity triggers, reset the counter and archive the previous season’s sheet for compliance.
Related Reading
FAQ
Where do the 1.1% and 1.0% base drop rates come from?
EA Help articles and Respawn developer streams reiterate that PC/Steam accounts have a 1.1% chance at heirloom shards per pack while console accounts sit at 1.0%. This guide cites those statements and explains how to override the values if future patches shift them.
How do I use the calculator for multi-season projections?
Log each season separately, store the output snapshot, then add the remaining packs into the next projection. The guide includes a template for labeling Season 21, 22, and 23 data so pity math remains transparent.
Do event bundles or Twitch drops affect pity?
Yes. Every pack—purchased, rewarded, or earned—counts toward the 500-pack guarantee. We show how to place bundle packs inside the Pack Probability Calculator so the curve reflects those freebies.
How should I treat loot tick bonuses?
Treat each tick as a temporary additive bonus. The calculator includes a Seasonal Boost field; the guide walks through recording +0.2% to +0.5% boosts as they appear in events.
Is this tool gambling-related?
No. LootCalc is an educational math platform. We do not sell packs and we encourage budgeting so players can avoid impulse spending.
Changelog
- 2025-11-14: Added loot tick workflow, seasonal boost references, and the actionable checklist.
- 2025-11-12: Linked to Heirloom Tracker and Battle Pass Planner for closed-loop budgeting.
- 2025-11-10: Initial guide release with methodology summary.
Last updated 2025-11-14. Refer to Editorial Policy.