![]() This goes for Mongoose enchant's proc as well btw. ![]() But if the main handed Cruader procs twice, it will only have 1 Holy Strength buff, the second proc will only refesh the buff to 15 seconds. Then the second weapon w/ Crusader procs, you now have 2 +100 Str Holy Strengths. If the first 1h, lets say that is the main handed one, procs. ![]() BUT, having two 1hs w/ Crusader enchants on them can stack, but still to a point. Having a 2h w/ Cruader enchant can proc, then any other procs when the first is still up, refreshes the proc. Next, Crusader proc CAN stack, to a point. So this cannont be enchanted w/ any 35+ enchant. ![]() Enchanted Kodo Bracers, level req 34 BoE blue leather bracers, this might have an item level of 37 or 38 but the item req is only 34. For example, Fiery War Ax, item req 35, level 35 Epic 2h ax BoE. If that happened, you could quite often have 120 agility and 2% speed increase for 14 seconds and then 240 agility and 4% attack speed increase for a further 15 seconds if your secondary mongoose procced during the last second of your first mongooses' proc.Ĭomment by ThottbotK, to clear a few things up įirst, any enchant that says "Required item level 35 and up". The only reason they don't share the same buff slot on your character is because blizzard didn't want a mongoose proccing and refreshing the existing buff from your first mongoose. If one triggers within 15 seconds of the other you will certainly gain the effect twice over for a total 240 agility and 4% attack speed bonus, regardless of the fact that they use two different buff slots. If they didn't stack, they would only provide 120 agility and 2% attack speed increase even if both procced at the same time.ĭo not think that just because the two different enchants have two different buff icons that they do not "stack". If you have two mongooses and both proc and give you 4% attack speed and 240 agility then yes, they are indeed stacking. ![]() "Stack" is used to determine the ability of an item to pile-up upon itself. Comment by 35014No, it's not a bad use of terminology. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |