There's so few skills in 5E that this makes a lot of sense. The complexity it would add is very low.Skillpoints.
Profiency doesn't do it for me.
Seems like this could be simple house rule. You get the same number of points as proficiency would give you and let people spread them around however they want. I'd probably limit points you can spend on any single skill to double your proficiency for balance.Skillpoints.
Profiency doesn't do it for me.
but with great risk for example boons which do not really help, things that disagree with the characters, the dm flat out not giving sufficient numbers of them or even giving too many to one player.Yea, but I read @jgsugden's post as advocating for getting a specifically GM-chosen boon in place of feats, based on the narrative of the game. Personally, I love that idea; it moves character growth out of the metagame and into the narrative space, which I think is very rewarding.
It needn't be edgy, though its a common trope. It would be similar to the necromancer, dealing with forces people usually aren't comfortable with for obvious reasons.it would also need lots of blood themed spells, I would put money on it ending up the edgy caster.
Let's assume people are able to write down with the math on both sides instead of the example you gave where that was reserved for THAC0. With that both cases are rolling a die and working out a number. But one is addition and uses the intuitive case of higher AC = better, much like everything else, and a unified mechanic of d20+mod >= DC, and the other uses subtraction including to negative numbers (slower than addition), a non-intuitive lower=better that doesn't match anything, and does nto follow aunified mechanic.No. Especially since character sheets had what the number was next to each weapon. So it was really easy. If you rolled a 15, and your THAC0 for that weapon (which had already factored in any modifiers) was 14, then you hit AC -1. It wasn't any more math, since the math was done up front to get the individual THAC0 for that weapon type. The only math was subtracting your roll from the THAC0 number. That's it. You didn't have the "I rolled a 14, +2 for strength, +1 for weapon, +4 for BAB, so I hit.....(14+2+1+4 is 21)...AC 21!"
We can't have a discussion if you ignore all those other things I said, like how THAC0 was capped in a 20 digit range and ascending AC isn't, for example. Another example is that one step of subtraction is generally easier than four or more steps of addition. It does not "lose in every difference". It's contextual. Sometimes it's easier, sometimes it's not. I already listed out in detail several examples. If you choose to ignore that part it's not my fault.Let's assume people are able to write down with the math on both sides instead of the example you gave where that was reserved for THAC0. With that both cases are rolling a die and working out a number. But one is addition and uses the intuitive case of higher AC = better, much like everything else, and a unified mechanic of d20+mod >= DC, and the other uses subtraction including to negative numbers (slower than addition), a non-intuitive lower=better that doesn't match anything, and does nto follow aunified mechanic.
Sorry, THAC0 loses by every difference there.
Here's an study (and there are plenty) about addition being easier than subtraction.
![]()
Fluency in subtraction compared with addition
Two studies were conducted to understand why subtraction with fluency is harder than addition. In Study I, 33 kindergartners were individually asked t…www.sciencedirect.com
None of your complaints about ascending AC are universal to that method though - in fact, none of them apply to 5e near as I can tell. (AC's stop at 25, you only need to add once, the only difference is addition vs subtraction.)We can't have a discussion if you ignore all those other things I said, like how THAC0 was capped in a 20 digit range and ascending AC isn't, for example. Another example is that one step of subtraction is generally easier than four or more steps of addition. It does not "lose in every difference". It's contextual. Sometimes it's easier, sometimes it's not. I already listed out in detail several examples. If you choose to ignore that part it's not my fault.