I was under the impression that the base rulesets didn't include house rules.
It is disabling automation because when the option is turned off the automation of the confirm roll does not happen. I wasn't referring to the automation of the critical damage. My believe is that, in Pathfinder, if there is no confirmation roll made, there should be no forced critical damage as FG simply doesn't know if the attack was a critical hit or not. If toggling the confirm automation off symbolized the automatic criticals (such as in 5e), then that is fine. But in that case, having the untargeted automated confirmation rolls always count as a critical hit is a bug since FG has no way of determining if the confirmation roll was successful. The confirmation roll is irrelevant even with the option turned no. (This is not the case for targeted attacks, but we are talking about the new functionality, not the old.)
Also, for the record, I'm not referring to critical hits on a natural roll of a 20. Most of the attacks that caused problems in my game were rolls of 19 for shortswords and longswords. FG was automating critical damage without knowing if the attack even hit. Granted, if the player is rolling damage, it most likely hit.
Exactly what am I applying this effect to? The context of this new change to FG is that there is no target for FG to check effects on.
Also, how do I apply an effect for fortification, say 20% immunity to crits?Quote:
[5E/4E/PFRPG/3.5E] Attack critical state tracking added for untargeted attack and damage rolls.