D&D 5E Rethinking Ability Scores and Skills

DonAdam

Explorer
I have a half-baked idea about how to handle ability scores and skills for both the basic version of Next (sans skills) and the advanced module with skills. It partly (or largely) divorces skill levels from experience and ties them to ability scores more closely to make the two versions closer to one another.

A few things inspired it:
  • I worry about DC's having to change if skills are optional. Ideally, basic and advanced characters could be run at the same table without too much difference in competence.
  • I liked the idea, floated on message boards early on, that your ability scores are your auto-success numbers for most tasks. So if you had a 14 Str, you can auto-succeed on most DC 14 tasks.
  • It's not a big concern but I worry just a bit about odd ability scores and feats being +1 to an ability score. Ideally you would "get something" for every bump to an ability score.
I'm taking the way of calculating ability modifiers (half of [score - 10]) as given.

Here's what I came up with:

Code:
Score          Modifier           Proficiency
  6-7              -2                     --
  8-9              -1                     --
  10               +0                     --
  11               +0                     d4
  12               +1                     d4
  13               +1                     d6
  14               +2                     d6
  15               +2                     d8
  16               +3                     d8
  17               +3                     d10
  18               +4                     d10
  19               +4                     d12
  20               +5                     d12

Modifier: The modifier works as normal.

Proficiency Die: The proficiency die is added to some skill checks (any non-attack, non-saving throw check to do stuff) in addition to the modifier.

When you add the proficiency die works differently in basic (no skills) or advanced (with skills):
  • Basic: Each class one or two Prime ability scores (or a choice of one or two off a small list). Any time you make a skill check for those abilities you add your proficiency die. So a Fighter might choose between Str, Dex, or Con. A Rogue might get Dex or Cha plus another Prime score depending on subclass.
  • Advanced: You have a skill list. When you make a skill check you add an appropriate ability modifier (which ability you use could be baked into the skills or based on the type of action you take). If you are trained in the relevant skill, you add the proficiency die for the relevant score to your skill checks.

So a proficient character with a 15 Str rolls 1d20 + 1d8 + 2 for skill checks involving Strength (in basic) or with trained Strength skills (in advanced).

Auto-Success: In either version, if you are proficient you can auto-succeed ("take 10") on tasks with a DC equal to or lower than your ability score. Otherwise, you only auto-succeed on tasks with a DC of 10 or less.

The table above means that your average roll with the proficiency die always exceeds your auto-success number by 2.



Every time you increase an ability score, your average proficient skill check goes up by 1: the modifier goes up by 1 on even scores, the proficiency die steps up a size on odd scores.

There are two obvious disadvantages:
  1. As stated above, the connection between level and skills is far more tenuous here. This will bother folks who like a steep increase in character aptitude with experience levels.
  2. For those of you that like symmetry, the table is asymmetric. The same trick for generating the "take 10" results does not work for ability scores below 10. I'm perfectly okay with that but it might bother some.

I think #1 is the only real concern, but it can be addressed several ways with feats:
  • Ability scores and thus skill bonuses will tend to rise with level if 1 feat = +1 ability score.
  • Feats can boost skills in various ways: giving Advantage on a given skill check, rolling twice/getting some minimum result on the proficiency die, or increasing the die size by one step.
  • Particular feats could be designed for each skill that enhance functionality (e.g., move at full speed while sneaking).

These would be small bonuses but that fits with flat math. Any such feats that aren't powerful enough can be tweaked by increasing the number of skills affected.

Tying proficiency die size to ability score also allows low-level NPC's to have expertise in certain skills. Kings don't need to be high level to be good at diplomacy. You can even imagine community statblocks that list the maximum die size for certain skills based on the size and nature of the community.

One can also imagine feats that offer patches to those with a mismatch between ability scores and desired skills:
  • Unexpected Talent: Pick a skill. You become trained in it and your proficiency die becomes a d8.
  • Intimidating Strength: use your Strength modifier and proficiency die to intimidate. You are trained in intimidate.

And of course there are a few possible variations:
  • Characters with scores lower than 10 might lower their auto-success number by their modifier.
  • The proficiency die might start at d4 for a 13 and go to d10, saving the d12 for someone with a 20 and some sort of Skill Focus. The auto-success numbers still work for that.
  • The advanced version might base the proficiency die on character level instead, but then you lose the nice math on auto-success.

What do ya'll think?
 
Last edited:

log in or register to remove this ad

Li Shenron

Legend
Auto-Success: In either version, if you are proficient you can auto-succeed ("take 10") on tasks with a DC equal to or lower than your ability score.

I like this part ^

Overall the idea is not bad, but I am not a fan at all of having skills rigidly linked to ability scores like in 3e, and this system links them even more strongly.

I wouldn't have a problem with skills not being level-based tho.
 

DonAdam

Explorer
Overall the idea is not bad, but I am not a fan at all of having skills rigidly linked to ability scores like in 3e, and this system links them even more strongly.

That is a cost. But I figure the design is headed that direction anyway.

In principle, though, you don't have to assign abilities to skills. You could make the call about which ability is relevant when you describe the action and make the check. The ability score determines the size of the proficiency die, but whether you get it depends on training.
 

Kavon

Explorer
I like it. It solves the 'dead ability score increase' problem quite nicely, I'd say.

In principle, though, you don't have to assign abilities to skills. You could make the call about which ability is relevant when you describe the action and make the check. The ability score determines the size of the proficiency die, but whether you get it depends on training.
Yeah, I don't really see how this idea has to force anyone to use a certain skill with a specific ability score.


If people think the die addition increases the results too much, I suppose you could have it start at d2 and end at d10 (also creates a little symmetry with the average of the die and the normal score modifier).
 

Remove ads

AD6_gamerati_skyscraper

Remove ads

Recent & Upcoming Releases

Top