Know the number behind the action
Many in-game actions have a chance attached: a shot that can miss, an ability that may proc, an attack that can land critical hits, a block that sometimes fails. Some of these numbers are published. Others can be estimated from experience. Either way, playing with a rough idea of the number is different from playing with a vague hope.
This article is about the small, repeated choices where those numbers matter. It is less about big strategic decisions and more about what to press in the next few seconds.
Reliable versus strong
A common trade-off is between an action that works more often and one that works less often but does more when it lands. Here is an illustration with made-up numbers.
- Attack A: hits 90 percent of the time for 30 damage.
- Attack B: hits 70 percent of the time for 40 damage.
On average, A does 0.9 × 30 = 27 damage per use, and B does 0.7 × 40 = 28. They are close. The average does not decide the question; the situation does.
If an opponent is nearly defeated and needs 30 damage to go down, A finishes them more often, because the extra 10 damage on B adds nothing and B misses more often. If you are attacking a high-health target with plenty of time, the averages matter more and B is marginally ahead. Knowing the numbers lets you see that the better choice depends on what you need, not on which attack feels better.
Variance is part of the picture
Averages hide how uneven results can be. An ability that has a 25 percent chance to trigger an extra effect will, on average, trigger once in four uses, but in practice it may trigger twice in a row and then not at all for a dozen uses. That unevenness is normal, and it is the reason a short run of luck or bad luck tells you little. Streaks and random clumping occur even when the underlying chance never changes.
This is useful in two ways. First, it stops you from reading too much into a short run: a few misses in a row does not mean the ability is bugged or that your timing has gone off. Second, it reminds you to avoid plans that only work if the lucky outcome occurs. A line that wins only when the 25 percent effect triggers will fail most of the time. A line that benefits from the trigger but does not depend on it is steadier.
Adjusting after a streak
After several good or bad results in a row, players often change their play. Sometimes this is justified, because the opponent may have adapted. Often it is not. Believing that you are “on a roll” is the hot hand idea, and believing a good outcome is “due” after a long wait is the mirror-image error. If each use has the same independent chance, past results do not change the next one.
There are exceptions worth knowing. Some games use systems that do change the chances, such as a pseudo random distribution that raises the odds after each failure, or a guaranteed result after a fixed number of misses. If your game does that, your estimate should reflect it. The point is to base your adjustment on how the system works, not on how the last few attempts felt.
Using rates for timing
Knowing odds also helps you plan when to commit. Suppose an effect you rely on has a modest chance per use. If you need it to land, count how many chances you have. A situation with several attempts available is very different from one with a single attempt. In the long run, you can think in terms of expected attempts: how many tries it typically takes for something to happen. That average still hides a wide spread, so it is a guide rather than a promise.
In practice, the simple rule is to prefer lines that give you more chances over lines that stake everything on one.
Putting it into the match
A few habits turn this into better play without slowing you down:
- Learn the key numbers for your main character or loadout. Hit chances, proc rates, cooldowns. You do not need all of them, just the ones that affect choices you make often.
- Ask what you need, not what is best on average. Finish a target, survive one more hit, or deal as much as possible are different goals with different best answers.
- Prefer robust plans. If a plan fails whenever a low-chance event does not happen, look for an alternative that has a fallback.
- Do not read too much into recent results. A handful of attempts is a small sample, and it moves around a lot.
- Check what the game actually does. Developers sometimes use systems that differ from a simple fixed-chance model, so treat your assumptions as provisional.
What it will not do
Knowing the odds does not remove luck. You will still miss the 90 percent shot sometimes, and still land the unlikely one. The benefit is not in avoiding bad luck, it is in making choices whose logic holds up when you look back at them. Because chance in outcomes stays real in any single moment, the realistic goal is steady, well-informed choices that tend to hold up over many matches.