Action and Strategy Games

The Math Behind the Mayhem: Understanding Probability in First-Person Shooters

How hit chances, bullet spread, headshot multipliers and damage thresholds work in first-person shooters, with simple worked examples of the numbers involved.

On this page
  1. Why shooters feel like skill but run on numbers
  2. Damage thresholds and shots to kill
  3. Time to kill
  4. Hit chance and bullet spread
  5. Counting hits over several shots
  6. Shotguns and pellets
  7. Headshots, hitboxes and accuracy trade-offs
  8. Network and fairness effects
  9. What the numbers do and do not tell you

Why shooters feel like skill but run on numbers

A first-person shooter looks like a pure test of aim and reflexes, and a large part of it is. Underneath, though, every weapon is a bundle of numbers: damage per shot, fire rate, spread, recoil, headshot multiplier and the health pool of the target. Understanding how those numbers combine does not replace practice, but it explains why some weapons feel reliable, why some fights seem decided before they start, and why a bad streak of misses is sometimes just ordinary variation.

The details differ between games, and developers change values in patches, so the figures below are illustrative examples, not the stats of any particular title.

Damage thresholds and shots to kill

The most important number in a gunfight is often the count of hits needed to remove a target. It is a simple division, rounded up.

Suppose a target has 100 health and a weapon deals 30 damage per hit. Three hits deal 90, which is not enough, so the target takes four hits. The fourth hit “wastes” 20 of its 30 damage, but it is still required. This is a damage threshold: small changes in damage only matter when they move the shot count.

If a headshot does double damage, one headshot deals 60. Two headshots deal 120, which kills. So a player who lands two headshots needs two hits rather than four. A mix works too: one headshot (60) plus two body shots (60) makes 120, which also kills in three hits.

Time to kill

Time to kill combines the shot count with fire rate. A weapon firing 600 rounds per minute fires 10 rounds per second, so one round every 0.1 seconds. Four hits are needed in the example above, but the first shot lands at the start of the sequence, so only three intervals pass before the fourth: about 0.3 seconds, assuming every shot hits.

Real fights are rarely that clean. Misses add shots, and each extra shot adds another interval. This is why two weapons with similar damage can feel very different: a slower weapon with higher damage per shot and a faster weapon with lower damage can reach the same time to kill on paper, yet respond differently when some shots miss.

Hit chance and bullet spread

Many shooters add random spread, so the bullet lands somewhere inside a cone around the point of aim. A simplified model treats this as a circle at the target’s distance, with the bullet equally likely to land anywhere inside it. Under that model the chance of hitting a target that sits fully inside the circle is just a ratio of areas.

For example, if the spread circle has a radius of 0.5 metres and the target’s relevant hit area is a circle of radius 0.25 metres, the ratio is (0.25 ÷ 0.5)², which is 0.25. Each shot has about a one in four chance of connecting. Halving the distance to a target typically shrinks the spread circle at the target, which raises the hit chance considerably, because area scales with the square of the radius.

Real games often use more complicated spread, such as bullets clustering toward the centre, spread that grows while moving and recovers while standing still, or a fixed recoil pattern that can be learned. A learned pattern removes randomness from the equation, which is one reason experienced players value predictable weapons.

Counting hits over several shots

When each shot is an independent event with the same hit chance, the number of hits follows a binomial pattern. A couple of results are worth knowing.

The chance of at least one hit in n shots is one minus the chance of missing every time: 1 − (1 − p)ⁿ. With p = 0.5 and four shots, the chance of missing all four is 0.0625, so the chance of at least one hit is 0.9375.

Needing several hits is harder. If a player must land at least four of eight shots at a 50% hit chance, the chance is 163 in 256, or about 64%. The same player with the same aim fails about a third of the time, purely from variation. That gap is worth remembering when a single gunfight goes badly. A small sample of fights says little about skill, which is the core idea behind sample statistics.

Shotguns and pellets

A shotgun fires several pellets per shot, and each pellet has its own roll. If a shot fires eight pellets that deal 10 damage each and each pellet has a 60% chance to hit, the expected number of hits is 8 × 0.6 = 4.8, or about 48 damage. Expected value is an average, though. Individual shots will land more or fewer pellets, so the same shotgun can deliver a kill in one shot on one occasion and fall well short on the next. Consistency improves at close range because the hit chance of each pellet rises.

Headshots, hitboxes and accuracy trade-offs

Headshot multipliers raise the reward for aiming at a smaller target. The head is a smaller hit area than the torso, so aiming for it usually lowers the hit chance while raising the damage per hit. Whether that is worth it depends on the numbers. If a headshot deals twice the damage but the hit chance is less than half, the expected damage per shot is lower than aiming at the body. Weapons and distances shift that balance.

This is a recurring pattern in shooter design, and a good example of how video game design uses small numbers to shape player behaviour: a safer option with a lower ceiling against a riskier one with a higher ceiling. It is a small, concrete case of calculated risk, where the right choice depends on the actual odds rather than on feel.

Network and fairness effects

Online shooters add another layer. Latency means the server and each player see slightly different versions of events, and the game applies rules to decide who hit first. Players sometimes read the outcome as bad luck, when the cause is timing between machines. How that plays out in team modes, where your individual aim is only one input to multiplayer win chance, is a separate topic. Beyond that, matchmaking tries to pair players of similar skill, so long-run win rates in many games drift toward an even split instead of reflecting raw ability.

What the numbers do and do not tell you

Knowing the math helps with decisions such as which weapon to pick, when to close distance, and when to retreat and reset. It does not guarantee outcomes, and no calculation removes the variation in a short fight. The practical takeaway is modest: judge a weapon by its shots to kill and time to kill, expect streaks of misses and hits to happen, and treat a small number of fights as weak evidence about your own skill or the weapon’s strength.

Keep exploring

Guides from other topics

All topics →