Thank you.
I agree the attack code is confusiing. Since you asked for a specific example ill give you one with the level 50 scenario above. The example below ASSUMES i know what the code is doing. I am going to leave ATK values out of it because im not sure what is being calced here.
Mob is level 50 Froglok Dar Knight from sebilis who has an AC of 429 in DB.
Level 50 Merc attack the Froglok. Merc has str of 267, and warrior for that level has offense of 210. Running that through formuyla listed above WIHTOUT the ATK added onto it gives you 463 for attack RATING.
Froglok is an NPC so the NPCACfactor rule is 2.25 by default.
Code:
else if(IsNPC())
{
armor = CastToNPC()->GetRawAC();
if(!IsPet())
{
armor = (armor / RuleR(Combat, NPCACFactor));
}
armor += spellbonuses.AC + itembonuses.AC + 1;
}
so the Frogloks armor is AC/2.25 + spells and item bonuses which means his AC before class armor caps is 190.
You can see the problem is that the attack rating is already over 2 times the AC to begin with. Now if you add (im working from memory) several hundred or thousand ATK once or twice you can see that the attack rating to AC ratio is someplace from 3x to 20x.
To be fair , you are remarkably close on your AC settings for mercs tanking NPCs.
Threaded Mode
