Dungeons and Dragons represents success and failure as binary values. There is no “failure with stuff” or “success with complications” written into the game, and failing by 1 or failing by 10 is usually the same result. Increasing your successes and minimizing failures is the primary goal of character optimization, but without understanding of 5e’s fundamental math it’s difficult to know what we need to target numerically to make an effective character.

For the purposes of this article, we can make some specific assertions about what makes a character “effective”. 5e’s math assumes that a character attempting to do something which they are good at should succeed 65% of the time, which gives us a perfect metric for how we should build characters. If you can’t hit that 65% mark, your character is less effective than intended, and if you’re above the 65% mark you’re more effective than the game assumes (which is what we want).

Where does the 65% number come from?

Take a look at this table. You may notice that the right-most column never changes.

PC Attack BonusMonster
Level/CRAblProf.TotalAC1Hit %
Attack vs. AC Progression
  1. Taken from the Monster Statistics by Challenge Rating table, DMG 274
  2. Assumes an ability increase resulting in the PC’s ability modifier increasing from 3 to 4 at 4th level
  3. Assumes an ability increase resulting in the PC’s ability modifier increasing from 4 to 5 at 8th level
  4. This level is an anomaly. Proficiency Bonuses increase, but expected monster AC does not.

This tells us a great deal. First, it solidifies the 65% target. Second, it highlights the fact that 5e was written to be work without feats; instead, it assumes that your first two ability score increases will go into the ability score which you’re using to attack. Third, it assumes that you’re getting Ability Score Increases at levels 4 and 8 to raise your primary ability score to 20.

What do I do with this information?

That’s really up to you. Any time that you fall below the 65% mark, it should be a trade. Whatever you get needs to be good enough to justify what you lose.

Feats are popular, especially among character optimization enthusiasts, but the above math makes the cost of feats abundantly clear. One feat will make you 5% less effective offensively until you get enough ability score increases to get up to 20. If you can mitigate this with things like spells or magic items, it will reduce the impact. Even Bless, a 1st-level spell, will provide a large enough bonus to offset taking 2 feats with an average roll of 2.5.

Perhaps more importantly, this stresses the importance of starting at 1st level with a 16 in your primary ability score. At 1st level when missing an attack by 1 frequently means an early death, there is little room for error, and you really need to squeeze every bit of effectiveness out of your character just to stay alive. Casters may have things a little better because they can rely on indirect options like support spells and spells which don’t require attack rolls or saving throws, but I would think long and hard before walking into a game with a 1st-level fighter that doesn’t have 16 Strength or Dexterity.

Let’s Talk Damage

Perhaps the most important reason to stay on the fundamental math is to maintain your damage output in combat. If you can’t hit, you won’t do damage. As your attack bonus lags, so will your damage per round (DPR).

With the introduction of the DPR Calculator, we’ve started including DPR in many of our example builds. While this certainly isn’t a perfect measure of effectiveness (save or suck spells and support spells affect DPR indirectly through multipliers on our party’s individual DPRs or by outright removing enemies), DPR is still a helpful measure for many characters whose primary offensive contribution is damage output.

But how much DPR do you need? What constitutes “good” dpr?

Finding the answer is surprisingly simple. The same rules that we use to find the fundamental math progression for attack bonuses also give us an hp progression for monsters. If we assume a party of 4 and 3-round encounters like the CR calculation rules do, we can divide the top end of the hp progression by 12 to get our target DPR. If your party’s average DPR is roughly that high, you’re doing okay.

I’ve chosen to include four columns of DPR:

  • Low DPR: If you’re above this number but below Target DPR, you’re not doing quite as much damage as the game expects on average. If your character is primarily doing other things (support spells, area control, save or suck spells, etc.) this might be perfectly fine. 
  • Target DPR: The sweet spot. If you’re at least this high, you’re doing fine. If you absolutely can’t get above this number, ensure that whatever you’re doing in combat boosts your party’s total DPR to compensate.
  • High DPR: If you’re above this number, you’re doing two people worth of work. You might be your party’s Striker, and in combat you’re the scariest thing that isn’t a save or suck.
  • Dude Stop: If you’re above this number, you’re dealing enough damage to feasibly solo encounters. Your DM may need to make significant adjustments to the difficulty of encounters to provide you with an adequate challenge. In effect, you’ve won character optimization. Stamp four stars on your character sheet in blue ink and send me a picture on twitter so I can revel in your success.
  • Warlock: A very simple warlock using Eldritch Blast, Hex, and Agonizing Blast with an ASI in Charisma at levels 4 and 8. This can be helpful as a baseline character to compare yourself to if the Target DPR numbers feel too abstract.
CR or LevelMax Expected HPLow DPRTarget DPRHigh DPRDude StopWarlock
20400 16.733.366.7133.338.2

The Power of Teamwork

While the DPR for attacks is straightforward and easy to calculate with our DPR Calculator, how do we determine the numerical DPR of indirect help? This is less straightforward, but still a simple calculation.

Using Bless as a simple example, calculate the normal DPR of your targets, then assume the average of +2.5 and calculate the new DPR. The difference between these two DPRs is the DPR of that Bless spell. As all parties will be different, the DPR of any given Bless spell can be all over the place.

This same kind of calculation can be done with several kinds of spells that don’t directly do damage, such as Web imposing Restrained, which in turn grants Advantage to attackers or Hold Person imposing Paralysis which both grants Advantage as well as automatic critical hits to attackers within 5 feet. You may find that your “Assist DPR “ is still hitting or exceeding Target DPR in addition to the defensive benefits these crowd control and buffing spells have.