Reply to thread

Message: <blockquote data-quote="NotAYakk" data-source="post: 9367064" data-attributes="member: 72555">You have turned a Skill check from a success/failure flip to a success-and-magnitude.  I think that is good; it is why D&D combat often works better than D&D skill checks.What you have failed to do is make the magnitude scale very well.  I get that you are mimicing weapon damage, but compare how attack damage scales to  how your system scales.L1 fighter with 16 strength does 28.5 damage over 3 rounds with +5 accuracy.L4 fighter with 18 strength does 42 damage over 3 rounds with +6 accuracyL5 fighter with 18 strength does 84 damage over 3 rounds with +7 accuracyL8 fighter with 20 strength and a +1 weapon does 100 damage over 3 rounds with +9 accuracyL11 fighter with 20 strength and a +1 weapon does 150 damage over 3 rounds with +10 accuracyL17 fighter with 20 strength and a +2 weapon does 202.5 damage over 3 rounds with +13 accuracyL20 fighter with 25 strength and a +3 weapon does 330 damage over 3 rounds with +16 accuracyDamage (the magnitude of the success) scales with roughly (L+1)*(10 to 15); accuracy scales roughly with 5+level/2.L1 rogue with 16 dex and expertise does 7.5 progress with +7 skillL5 rogue with 18 dex and expertise does 8.5 progress with +10 skillL11 rogue with 20 dex and expertise and good tools does 10.5 progress with +13 skill and a min roll of 23.L20 rogue with 22 dex and expertise and legendary tools does 12.5 progress with +18 skill and a min roll of 28.Progress scales at 7+level/4; accuracy (with expertise) scales with 7+level/2.The second problem that your system lacks is that your problems aren't "hitting back".  Not literally, but I mean in the sense that harder problems are just slower and take longer.  Problems above a certain magnitude/difficulty should be impossible to solve by simply grinding away at them.What I'd suggest is:1. Make the magnitude portion scale faster.  Level 20 PCs should be many many times "faster" than L 1 PCs.2. Tasks should spawn complications.  These can be adventure hooks - "if you want to make more progress, you need to do X" for example.  They could be costs - "you can get a map to the bedroom of the queen's concubine, but it means you have to burn your fence contact and turn them over to the cops".  (solving that problem is optional)Complications are not dependent on failure, but on progress (or sometimes on time) - just like monsters attack back not only when you miss, but just because you engaged them.Complications need not be narratively heavy, at least on average.  Ie, imagine a 1 in 6 chance of a complication; now the narrative weight of the complications is 6 times smaller.The existence of complications means that the rate of progress is no longer just a timer - instead, it determines how many complications you run into (on average), and such complications could prevent further progress (especially if you aren't, say, an adventurer!)</blockquote>

Verification