Galactus wrote:
Edoras, when calculating tohit/damage, the code already has to process it. Add in a flag for AoN, and bam, it doesn't add it. Or, could be just as easy to to reverse the process. (less lag to stop the code from happening then reverse it, but there might be limitations that would force the latter)
I suppose, but I still feel like this might be an oversimplification that would inevitably result in random things not being noticed. Ignoring GS for to-hit/damage against MR-only targets, for example, isn't just a simple calculation: If done accurately, the code would have to subtract the amount of strength that the GS spell is currently providing before factoring in the strength of the person in their own to-hit roll. Granted, I don't know what the code looks like, but as a developer myself, I understand that not everything is as simple to implement as it might seem. I would imagine that to-hit rolls and AC calculations are separate calculations, one from the attacker and one from the defender, and it might be incorrect to assume that everything can be easily gleaned about the attacker and defender in both circumstances.
I should say, that you are right. Without seeing the code, it could be from easy to WTF are you crazy? hard. Just trying to offer a balance, mostly in a vacuum.