Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="ObsidianCrane" data-source="post: 4920413" data-attributes="member: 54918">Actually it is, the Crit rules specifically allow you to roll a result that would be a Crit if it Hit, but not hit and thus not be a Crit.Critical Hit Rules work like this;Attack{Hit= a d20 roll + modifiers = > targeted defence of target.Nat20 = the d20 shows a 20Precision = the d20 shows a number other than 20 that you can score a Crit withCritChance = a Nat20 or PrecisionMiss = a d20 roll + modifiers < targeted defence of target.Crit = Maximum damage and other effects requiring a Critical HitDamage = Normal damage of the Attack.If (Hit AND CritChance) Then Crit; Else (If (Nat20) then Do(Damage); Else Miss);}The argument of Artoomis is fundamentally that because Holy Ardor uses "rolled a double" that it creates this situation:Attack{Hit= a d20 roll + modifiers = > targeted defence of target.Nat20 = the d20 shows a 20Precision = the d20 shows a number other than 20 that you can score a Crit withHolyArdor = you roll doubles other than double 1 using Oath of Enmity on d20 as part of an AttackCritChance = a Nat20 or PrecisionMiss = a d20 roll + modifiers < targeted defence of target.Crit = Maximum damage and other effects requiring a Critical HitDamage = Normal damage of the Attack.If ((Hit AND CritChance) OR HolyArdor) Then Crit; Else (If (Nat20) then Do(Damage); Else Miss);}The problem is that this requires that Holy Ardor not roll a number on a d20 as part of an attack roll to not invoke Precision. But Holy Ardor does roll a number on a d20 on an attack roll, leaving that as false. You cannot ignore the underlying rules unless explicitly told to do so in exception based design.</blockquote>

Verification