who would have ever expected there is no avoidance cap.P.S. Avoidences are capped at 75%, if you see more than 75% you are clearly high
*Surprised Pikachu face*
who would have ever expected there is no avoidance cap.P.S. Avoidences are capped at 75%, if you see more than 75% you are clearly high
There's no argument. I only have parry stacking gear on my SM, and I'd gladly show you my combat logs of how I eat melee guard damage via parry better than a snb tank would. Then you can factor in this is what is was like before guard changes was patched. I might even be able to dig up some old screenshots also. A snb tank in full defensive sov wouldn't come close.sharpblader wrote: ↑Wed Jan 13, 2021 8:55 pmObviously! Duh! Organized WBs are now accepting SnB classes as guard bots again thank god!detrap wrote: ↑Wed Jan 13, 2021 11:35 amBecause you make it seem like 2h was so powerful at guarding that SnB was completely obsolete. If that was true, no organized wb would take a SnB chosen, IB, BG, or SM.
If SM was so OP as a champ guard the problem lies with SM avoidance. NOT the entire system of how guard works.
It was a lot more powerful before than it is now obviously. The 2H SM wasn't OP with guard, it is just the equivalent of the BO block channel. The BO variant is better, but balanced out because they have to spec for it and it gets a movement speed penalty. I used the SM as a clear example seeing that they can channel 100% parry on demand.
Where are you taking the argument? Why are you still avoiding my question? Your clear example does not warrant that every 2h tank with high parry was guarding better than any SnB tank.
You know what? Ill take the advice of someone who posted earlier to stop arguing with you. Because it is clear that you are in over your head. Let someone else take the headache. To them I wish good luck.
Well, I guess I deserve it
I'd say not.
Still is a cap of 75% it's apparently just from INIT/WP/WS vs BS/INT/STR and doesn't take into consideration added avoidance from renown/gear/proccs.nocturnalguest wrote: ↑Wed Jan 13, 2021 10:08 pmI'd say not.
There was a cap.
And this is the actual post after that it was no longer:
viewtopic.php?f=8&t=31055&start=40#p352017
No patchnotes accounted that.
Patchnotes with dalen saying that its now different (=exact official guard change) was nothing new. Dalen confirmed it was there even before he put it into patchnotes.
You are quite persistent about wods being an issue. Maybe wods should be looked at if you feel so strongly. Other 2h tanks such as kobs really suffer now having no way or very little to get dodge disrupt and parry all above 40%. You can’t possibly believe knights deserve that just because sm has it good. But honestly sm sacrifices damage to channel wods so it still evens out IMO. Eating guard damage is the class mechanic 2h or not. In literally no universe was 2h avoiding more guard damage or even close to snb with exception to maybe sm in low gear vs snb. You clearly aren’t knowledgeable enough to know the difference. Chosen gets 25% parry on block so you really think a 2h chosen eats as much guard damage? Not on your life man.detrap wrote: ↑Wed Jan 13, 2021 9:41 pmThere's no argument. I only have parry stacking gear on my SM, and I'd gladly show you my combat logs of how I eat melee guard damage via parry better than a snb tank would. Then you can factor in this is what is was like before guard changes was patched. I might even be able to dig up some old screenshots also. A snb tank in full defensive sov wouldn't come close.sharpblader wrote: ↑Wed Jan 13, 2021 8:55 pmObviously! Duh! Organized WBs are now accepting SnB classes as guard bots again thank god!detrap wrote: ↑Wed Jan 13, 2021 11:35 am
It was a lot more powerful before than it is now obviously. The 2H SM wasn't OP with guard, it is just the equivalent of the BO block channel. The BO variant is better, but balanced out because they have to spec for it and it gets a movement speed penalty. I used the SM as a clear example seeing that they can channel 100% parry on demand.
Where are you taking the argument? Why are you still avoiding my question? Your clear example does not warrant that every 2h tank with high parry was guarding better than any SnB tank.
You know what? Ill take the advice of someone who posted earlier to stop arguing with you. Because it is clear that you are in over your head. Let someone else take the headache. To them I wish good luck.
Wods doesn't need looking at because it's the equivalent to the BO block channel, each with their pros and cons. Guard damage has been a nerf for every 2H tank, not just the knight. Wods is a means to reduce guard damage when under pressure. An SM didn't need sov/warlord/invader to out shine any snb tank apart from the BO when it came avoiding guard damage pre patch.ashton007 wrote: ↑Thu Jan 14, 2021 3:02 amYou are quite persistent about wods being an issue. Maybe wods should be looked at if you feel so strongly. Other 2h tanks such as kobs really suffer now having no way or very little to get dodge disrupt and parry all above 40%. You can’t possibly believe knights deserve that just because sm has it good. But honestly sm sacrifices damage to channel wods so it still evens out IMO. Eating guard damage is the class mechanic 2h or not. In literally no universe was 2h avoiding more guard damage or even close to snb with exception to maybe sm in low gear vs snb. You clearly aren’t knowledgeable enough to know the difference. Chosen gets 25% parry on block so you really think a 2h chosen eats as much guard damage? Not on your life man.detrap wrote: ↑Wed Jan 13, 2021 9:41 pmThere's no argument. I only have parry stacking gear on my SM, and I'd gladly show you my combat logs of how I eat melee guard damage via parry better than a snb tank would. Then you can factor in this is what is was like before guard changes was patched. I might even be able to dig up some old screenshots also. A snb tank in full defensive sov wouldn't come close.sharpblader wrote: ↑Wed Jan 13, 2021 8:55 pm
Obviously! Duh! Organized WBs are now accepting SnB classes as guard bots again thank god!
Where are you taking the argument? Why are you still avoiding my question? Your clear example does not warrant that every 2h tank with high parry was guarding better than any SnB tank.
You know what? Ill take the advice of someone who posted earlier to stop arguing with you. Because it is clear that you are in over your head. Let someone else take the headache. To them I wish good luck.
No.Rapzel wrote: ↑Wed Jan 13, 2021 11:18 pmStill is a cap of 75% it's apparently just from INIT/WP/WS vs BS/INT/STR and doesn't take into consideration added avoidance from renown/gear/proccs.nocturnalguest wrote: ↑Wed Jan 13, 2021 10:08 pmI'd say not.
There was a cap.
And this is the actual post after that it was no longer:
viewtopic.php?f=8&t=31055&start=40#p352017
No patchnotes accounted that.
Patchnotes with dalen saying that its now different (=exact official guard change) was nothing new. Dalen confirmed it was there even before he put it into patchnotes.
Code: Select all
// If wearing a shield
int Block = 0;
if (Target.ItmInterface.GetItemInSlot((UInt16)EquipSlot.MAIN_GAUCHE) != null && Target.ItmInterface.GetItemInSlot((UInt16)EquipSlot.MAIN_GAUCHE).Info.Type == 5)
{
Block = (int)(((double)((float)Target.ItmInterface.GetItemInSlot((UInt16)EquipSlot.MAIN_GAUCHE).Info.Armor / OffensiveStat) * 0.2) * 100);
}
if (Block > 50)
Block = 50;
Log.Info("Block rate", "" + Block);
Log.Info("GameData Block", "" +GameData.BonusTypes.BONUSTYPES_EBONUS_BLOCK);
if (RandomMgr.Next(100) < (Block + (Target.StsInterface.GetTotalStat((byte)GameData.BonusTypes.BONUSTYPES_EBONUS_BLOCK) - Ab.Caster.StsInterface.GetTotalStat((byte)GameData.BonusTypes.BONUSTYPES_EBONUS_BLOCK_STRIKETHROUGH))))
return GameData.AbilityResult.ABILITYRESULT_BLOCK;
uint AttackType = 0;
if (Ab.Info.Info.MaxRange <= 5)
AttackType = 0; // Melee
else
AttackType = 1; // Ranged
int SecondaryDefense = (int)((((double)DefensiveStat / OffensiveStat * 0.075) * 100));
if (SecondaryDefense > 25)
SecondaryDefense = 25;
And detrap's conformism. Man, you spinning like a slug in salt. Have some dignity.
Users browsing this forum: No registered users and 91 guests