Loot Drop Probability: How Drop Rates Actually Work

I was staring at a loot chest timer and doing math on my phone

I was sitting there at like 1:12 a.m., half awake, watching the same boss fall over for the 47th time, and the game still wouldn’t cough up the one thing I needed. The tooltip said “rare.” Cool. Rare like “you’ll see it eventually,” or rare like “you’re basically adopting this boss as a roommate”?

I opened my notes app, typed a few numbers, and immediately confused myself.

So yeah, if you’ve ever said “this drop rate is rigged,” you’re in good company.

The thing is, most loot systems aren’t mysterious… they’re just probability doing that annoying probability thing where it feels personal. And if you’re trying to min-max a farm route, decide whether to burn a boost, or figure out if switching difficulties is worth it, you don’t need vibes. You need the math under the hood (but like, the friendly version).

Drop rate doesn’t mean “you’ll get it in X runs”

Games love to show a drop rate like 5% and let your brain do the rest. And your brain goes, “Okay, 20 runs.” Which is… kind of a lie you tell yourself so you don’t cry.

A 5% drop chance means each run is a new roll with a 0.05 chance of success. That’s it. One roll, one chance, no memory (unless the game has pity, and we’ll get to that).

So after 20 runs, you’re not at “guaranteed.” You’re at “pretty decent odds.” Those are not the same sentence.

Here’s the part that messed with me when I first learned it: the chance you don’t get the drop over and over is what you should calculate, because that’s the streak you’re actually living through.

And yes, I nodded like I understood that the first time. I didn’t.

The numbers you actually care about (50%, 90%, 95%)

If you’re min-maxing, you’re not asking “what’s the average.” You’re asking “how many runs until I’m probably done?” That’s a different question, and it has a clean answer.

We can rearrange the formula to solve for runs needed to hit a target probability:

Let’s do a worked example, because otherwise it’s just math soup.

Example: drop rate p = 5% (0.05). You want a 90% chance to see at least one drop.

1. Compute 1 − target = 1 − 0.90 = 0.10
2. Compute 1 − p = 1 − 0.05 = 0.95
3. n = ln(0.10) / ln(0.95) ≈ 44.9

So you need about 45 runs for a 90% chance. Not 20. That’s the whole emotional arc right there.

And if you’re thinking “okay but I did 45 and still didn’t get it,” yeah, that’s allowed. Probability isn’t a contract, it’s a weather forecast.

Here’s a quick table for common drop rates. These are runs to reach a given chance of at least one drop, rounded because nobody wants decimals mid-grind.

That 1% row is why “I’m on run 180 and nothing” is not automatically a conspiracy. It’s painful, but it’s in the ballpark of normal pain.

So why does it feel worse than it is?

Because your brain tracks streaks, not distributions. And games are basically streak-generators.

Also, people accidentally do the gambler’s fallacy thing, where you feel like you’re “due.” But if each run is independent, being unlucky doesn’t make the next roll luckier. It just means you’ve already paid the emotional tax.

And then there’s the other sneaky part: a lot of loot isn’t a single roll. It’s multiple rolls stacked together, or conditional rolls, or “roll a table, then roll within the table,” and the UI just shows you one friendly number.

This is where you, the min-max gremlin (affectionate), can squeeze value. Because once you understand the structure, you can compare farms correctly.

Case 1: Multiple independent chances per run. Maybe the boss drops two loot bundles, or you get an extra roll from a perk, or the chest has two independent item slots.

If you get k independent rolls per run at probability p each, your effective per-run chance becomes:

Example: p = 5%, k = 2 rolls per run.

p_eff = 1 − 0.95^2 ≈ 9.75% per run. That’s almost double! That’s a lot of runs saved!!

Case 2: “Drop rate” is conditional. Like: 30% chance to drop a weapon, then 10% chance that weapon is the one you want. The real chance is 0.30 × 0.10 = 3%.

And if it’s 30% to drop a weapon, then it picks from 12 weapons evenly, your chance is 0.30 × (1/12) ≈ 2.5%. (Unless it’s weighted, and then… good luck, honestly.)

Case 3: Pity systems (bad luck protection). Some games increase your odds after misses or guarantee a drop after N runs. That breaks the “independent runs” math, but in a good way. If the game says “guaranteed by 50,” then your 95% number doesn’t matter anymore after that point, because the ceiling is real. I love pity systems. I also wish games would just say it out loud instead of making you read a spreadsheet from a Discord pin (which is kind of the modern instruction manual, I guess).

How you use this to min-max your farm route

Okay, practical stuff. You’re deciding between Farm A and Farm B, and both communities are arguing like it’s politics.

Don’t compare drop rates directly unless the run times are the same. Compare chance per hour or expected time to reach 90%.

Here’s a simple workflow I use:

• Step 1: Estimate p (per run) as best you can. If it’s a table-within-a-table situation, multiply the pieces.
• Step 2: Count rolls per run (k). If you’ve got bonus chests, extra loot slots, or a “double drop” event, fold that in with p_eff = 1 − (1 − p)^k.
• Step 3: Measure your run time. Not the “perfect run” time. Your real time, including loading, vendor dumps, and the moment you stare at your inventory like it insulted you.
• Step 4: Compute runs needed for 90% (or 95% if you’re stubborn). Then multiply by minutes per run. That’s your planning number.

If you want to shortcut the math, I built calculators for exactly this kind of stuff.

Use the basic odds tool here: loot drop chance calculator. If you’re comparing two farms, this helps: farm efficiency calculator. And if you’re stacking multiple rolls or bonus loot sources: multiple rolls probability calculator. If you’re tracking a pity cap or guaranteed drop, try: pity system calculator. And for the “how many runs until X%” question: runs to probability calculator.

And yeah, I know, “just play the game.” But if you’re here, you’re like me: you enjoy the excessiveness of optimizing. It’s half the fun.

FAQ (the stuff people argue about in chat)

So next time you’re on run 38 and your friend gets the drop on run 2, you can be mad… but at least you’ll be mad with correct math.

That’s basically the whole vibe of min-maxing anyway.