View Full Version : 4x Warriors and 1 paladin set up
Darknife
09-20-2019, 08:26 AM
At level 12 I can kill pretty much 5 levels higher then my current level, its fun as hell; however, is the normal set up 4 Arms warriors? I have seen a video where there is 1 prot, 2 fury and 1 arms?
I want to be able to solo most dungeons with this crew, if thats even possible (Classic).
Thoughts?
nodoze
09-24-2019, 03:48 AM
At level 12 I can kill pretty much 5 levels higher then my current level, its fun as hell; however, is the normal set up 4 Arms warriors? I have seen a video where there is 1 prot, 2 fury and 1 arms?
I want to be able to solo most dungeons with this crew, if thats even possible (Classic).
Thoughts?Sorry I missed this till now. Right now the general thought is prioritizing Arms with Sweeping Strikes is overall best. Additionally Arms has better passive Rage benefits (some are not documented in the talent points) and Arms is more flexible for retaining rage when stance-dancing which is hard to optimize (especially on slaves)...
Multiple people have reported that and I have done some testing and Arms seems higher for me as well. From 31-33 I have tried to funnel incoming damage to my single Fury Warrior but often my other Arms Warriors take the aggro when they pop Sweeping strikes so I am not sold on the idea of funneling the bulk of incoming damage to a lone Fury warrior (and letting the other Arms Warriors get the rest). I will likely focus on it again at 36 when I get WhirlWind on all my Warriors and try to report back then...
On a related note, Arms is also highly recommended over Fury on PVP servers...
Mercbeast
09-25-2019, 12:32 AM
The only way to make a tank work, reliably, is going to be to let your other warriors sit passively auto attacking for 5-10s at best.
My recommendation is, this is not a good system to plan for. You have zero CC. You are face tanking everything. This means that for example, when you go into BRD, if you decide you want to farm Bael'Gar, enjoy the 5 elite packs. These fights even at 57-58 are straight up DPS races, and if you're fiddling with trying to manage agro for 10s, you're going to die. So, you don't wait to build threat and you go ham, and your tank MIGHT get threat, but it might not, and if it doesn't, then you're really just down a DPSing warrior and those DPSing warriors are tanking anyways.
nodoze
09-25-2019, 05:12 PM
The only way to make a tank work, reliably, is going to be to let your other warriors sit passively auto attacking for 5-10s at best.
My recommendation is, this is not a good system to plan for. You have zero CC. You are face tanking everything. This means that for example, when you go into BRD, if you decide you want to farm Bael'Gar, enjoy the 5 elite packs. These fights even at 57-58 are straight up DPS races, and if you're fiddling with trying to manage agro for 10s, you're going to die. So, you don't wait to build threat and you go ham, and your tank MIGHT get threat, but it might not, and if it doesn't, then you're really just down a DPSing warrior and those DPSing warriors are tanking anyways.I think you are correct and for Horde it may not be viable.
An Alliance team with a Paladin can give the 3 Arms Warriors -30% Threat and give a single Fury Warrior a strong chance to be the one to typically SnowBall. It hasn't proven out to be consistent in practice at 31-33 as Sweeping-Strikes by themselves is just too much but hopefully at Level 36+ when all get WhirlWind the DPS will be close enough that a Fury Warrior with a relative +30% Threat can keep the aggro (especially if he is charging in first getting initial "sight aggro" and is the only one shouting initially and thus getting all the initial hits). In that approach you shouldn't really need to wait 5-10 seconds...
Mercbeast
09-25-2019, 10:46 PM
If you make it work, lemme know. My experience is, all it takes is one crit and anyone not the tank has threat :)
Apatheist
09-26-2019, 03:11 PM
Half the point of having two paladin healers is that it doesn't really matter which warrior takes agro. Warriors should all have around the same gear/mitigation level. Even when mobs are cleaving it doesn't matter all that much with two paladins unless you've pulled a ton of mobs. You just outheal everything.
Using sanctuary on your DPS is also kind of a waste. I use light/might on warriors to maximize DPS/HPS and kings/wisdom on the paladins. I stop to drink on one of my paladins when it gets to about 1/3 mana, continue pulling while healing with the other so it's just non stop pushing forward.
nodoze
09-26-2019, 05:24 PM
Half the point of having two paladin healers is that it doesn't really matter which warrior takes agro. Warriors should all have around the same gear/mitigation level. Even when mobs are cleaving it doesn't matter all that much with two paladins unless you've pulled a ton of mobs. You just outheal everything.
Using sanctuary on your DPS is also kind of a waste. I use light/might on warriors to maximize DPS/HPS and kings/wisdom on the paladins. I stop to drink on one of my paladins when it gets to about 1/3 mana, continue pulling while healing with the other so it's just non stop pushing forward.Understood and overall agreed especially if all are essentially the same spec/gear.
Once they get to cap this is somewhat less of a factor as they can have up-to 20 points in either tree and thus have benefits from both but when leveling generally you really need to pick one tree and Arms has generally been better (especially when you can't control who gets aggro).
With the observation that one tends to randomly take aggro and then go turbo on DPS the idea was/is whether a Fury Warrior could maybe get more DPS output from the incoming damage than the others (if you could control the aggro). This testing isn't really about worries about healing output being sufficient nor about trying to limit or mitigate incoming damage but rather is about trying to do more damage output from the incoming damage. It may or may not work out...
For me at least learning new things and trying different approaches/ideas is one of the main things I like about classic specs & group compositions. At this point some of us don't even have Kings nor Light yet so why not try to see if channeling Fury could help? With me going 31 Holy first on both of my Paladins I won't even have Kings till around Level 50... If this doesn't pan out I will respec my one remaining Fury Warrior to Arms.
Mercbeast
09-26-2019, 05:28 PM
Half the point of having two paladin healers is that it doesn't really matter which warrior takes agro. Warriors should all have around the same gear/mitigation level. Even when mobs are cleaving it doesn't matter all that much with two paladins unless you've pulled a ton of mobs. You just outheal everything.
Using sanctuary on your DPS is also kind of a waste. I use light/might on warriors to maximize DPS/HPS and kings/wisdom on the paladins. I stop to drink on one of my paladins when it gets to about 1/3 mana, continue pulling while healing with the other so it's just non stop pushing forward.
This is fine when you're able to plow the content. However, there are some areas you may want to do, where there is just A LOT of incoming damage. The Bael Gar area is one example. It's 5 elite packs, you have no real CC. Once they focus on whoever the front running warrior is, things can get messy in a hurry. Two healers would probably comfortably mitigate this, probably. For a solo healer though, it's very easy to get behind on heals, pull threat even with fade, and then its a scramble to piercing howl kite to the instance entrance and escape :)
Nandus
10-09-2019, 12:46 PM
For those who are going with 2 paladins and 3 warriors- both are holy paladins and staying in the back and heal? Or one paladin also retribution ?
MiRai
10-12-2019, 11:28 PM
For those who are going with 2 paladins and 3 warriors- both are holy paladins and staying in the back and heal? Or one paladin also retribution ?
I would assume the two Paladins fill both the tank and healer roles, while the Warriors take care of the DPS.
vBulletin® v4.2.2, Copyright ©2000-2025, Jelsoft Enterprises Ltd.