Mob difficulty isnt scaling with character

[Cowboy6534]

And yes you want green mobs hitting for minimum almost always except for raid mobs.

Unless you have gray con on your server then gray can be made the default and green can adjusted accordingly.

[Cowboy6534]

The code below this.

		//check if we're hitting above our max or below it.
		if((min_dmg+eleBane) != 0 && damage < (min_dmg+eleBane)) {
			mlog(COMBAT__DAMAGE, "Damage (%d) is below min (%d). Setting to min.", damage, (min_dmg+eleBane));
		    damage = (min_dmg+eleBane);
		}
		if((max_dmg+eleBane) != 0 && damage > (max_dmg+eleBane)) {
			mlog(COMBAT__DAMAGE, "Damage (%d) is above max (%d). Setting to max.", damage, (max_dmg+eleBane));
		    damage = (max_dmg+eleBane);
		}

Can be adjusted so that it falls into the fall /3.5

And actually this calculation can just be added into the end of the if statements in the switch case.

[Cowboy6534]

But I believe that even if it reverts to a default of 50 unmitigated it will still be fine since by the time you run into a mob with a min or 50 your ac calculations will take over and it should still keep the same curve.

What do you think cavedude? Honestly so far I haven't had any problems but that doesn't mean there aren't any.

[jsr]

Although it affects mobs with a lower ratio to a lesser degree, it's still a significant degree. It's also not part of your design and works against the concept of having brackets which you set. I only chose the green example because it had the most brackets. The figures look bad for other /con's as well.
At the 50% ratio: (over 4400 mobs)
yellow mobs hit minimum 50% of the time.
white mobs hit for minimum 70% of the time.

At 40% ratio, these figures drop by a few % rather than a lot of %.


I /coded over 4000 examples of mobs that have a 50% or higher ratio of mindmg to maxdmg, but edited them out on second thought Over 14,000 mobs have 30% or higher ratios.. this is not an insignificant number.

Don't let it stop you tinkering, but you might want to rethink the solution.

[jsr]

You misunderstand me - it reverts to min_hit AFTER the mitigation from AC.

[Cowboy6534]

Originally Posted by jsr

You misunderstand me - it reverts to min_hit AFTER the mitigation from AC.

Where is that in the attack.cpp?

[jsr]

Originally Posted by Cowboy6534

Where is that in the attack.cpp?

Search for meleemitigation. IMO it's where you should be looking if you want to tweak mitigation code. Not to discourage you, but what you're doing at the moment is called a hack job :)

[jsr]

use this query to get the ratio's;

select id, name, maxdmg, mindmg, mindmg/maxdmg as ratio from npc_types where (mindmg/maxdmg) > 0.2

You can change 0.2 to whatever suits.

[Cowboy6534]

If you remove my code and go with standard and you have a green mob that hits your for min and then you mitigated that down to below the min and then some other check say well its below min so just bring it back up doesnt that defeat the purpose of the ac check?

[jsr]

No, the way it works is that a mob hits for maxdmg, and then AC and other mitigation factors are pitted against attack to push damage down towards minimum. There are 20 different values that a mob can hit for on live, so the function looks at mindmg and maxdmg of a mob, works out the 18 values in between, and then the outcome of mitigation vs attack determines which of the 20 possible values is the final damage outcome.

[jsr]

FYI it appears that there are now at least 30 values on live.

[Furniture]

Any word on a fix for this or if Cowboy's code is good enough?

[lerxst2112]

Originally Posted by Furniture

Any word on a fix for this or if Cowboy's code is good enough?

You are free to apply any patches to your own server if you like.

[Furniture]

I also have an issue that it seems npc's arent ever missing swings.

[game]

This issue has been resolved on the Sleeper server - tests have shown AC to play a much larger role in overall combat damage.

http://epicemu.com/forum/ac-new-dama...ing-code-tests