Considering that an optimized (read: scimitar-using) WM will have an unenchanted base Threat Range of 12-20, that's a GUARANTEED 20.25% chance of a critical hit, and thus, forcing the creature to roll against instant death that often, even if its AC is 300.
Oh and Weebs, the DC for Dev Crit is 10+ 1/2 Char Levels + str ModSo a Level 30 Fgt/WM with 30 str is only 10 +15 +10, so 35. high, sure, but its no higher then a Mage with Focus in the right school casting Weird or Wail, I believe...
Hold the phone here chief. It's a guaranteed threat for a critical. If the critter has AC 300, you'll only force it to save vs. death on 20's.
To my understanding, (though the Bioware engine may make a liar of me on this,) you nail the Crit if you Threaten in both the initial roll and the confirming roll.E.g. a normal Rapier threatens on 18-20. You'd absolutely hit (and, thusly, score the crit) if you rolled Threat Roll: 19 + x = Y (Confirm: 18 + x = Z).
Even though I'm certain that your intentions are good Jan, you have to ponder on the timing and suggestion of all this... It looks a lot like lowering the prereqs for shortcomings of Barion. However I doubt it's the case, so on to the point.Restricting it to WMs is definitely not a good idea. Even though I understand your reasoning behind it, it would be too restrictive. Lowering the STR prereq isn't too good an idea either, since as it is, Dev. Crit is the pinnacle of the strength focusing melee path. Just like DR and poison/disease immunity is when you go high CON. Every focus has it's good and bad sides and I think it should stay as it is. Dev. Crit is a powerful ability for those that can actually get it, so let's keep it like that.Hold the phone here chief. It's a guaranteed threat for a critical. If the critter has AC 300, you'll only force it to save vs. death on 20's.
Dev.crit works like Quivering palm???Dc for dev. Crit 10+ half character lvl + str modifierDc for Quivering palm 10+half MONK lvl + wisdom modifier
You critical hit following this pattern:1. When an attack roll is successful (hits) and within the threat range, a threat roll is made. 2. If the threat roll succeeds (hits the target = surpasses AC or is a 20), the hit is critical, and damage is rolled a number of times equal to the multiplier.So your reasoning was good in your example, just the AC 300 was pushing it You can't crit what you can't hit...
Your estimation is basing on that dev crit only has a str req of 18 which is quite flawed