Yea, you're giving up your +1 enmity generator (regardless of how much more enmity the other target pulled on the enemy) with a good long range to start a pull, that almost no enemy is too far away for you to pull safely with shield lob/tomahawk. A stray enemy will not necessarily be regained by a shield lob. A provoke + shield lob, will no doubt get you enmity back so you don't have to move your position and drag an entire mob with you to do so.
I'm referring to the OP saying that people shouldn't pull initial mobs with provoke. The only reason to do so is because you're too scared to move a bit closer to shield lob (i'm a paladin, so i'm just using my ranged attack as example). It's not like you can't move after your shield lob. Just grab and pull backwards if you really need to position, it's not that hard. Shield lob is on your GcD, Provoke is not. If you can't wait the 2.5 seconds it takes for a GcD for the start of a pull, then you did something wrong along the way (and I honestly wouldn't know what in the world could even prevent you from using your ranged attack on an initial pull).
All other situations can be done case by case. But I see zero reason to START a pull with provoke. Grabbing another mob that's farther away while continuing to hold a current mob is an ok scenario. That is NOT an initial pull though. That is a continued pull.
And even with that being the case, it's really not THAT hard to simply move a few feet in said direction (and drag the dang mob with you) and use shield lob. If DPS have an AoE and it won't reach, then sure. Use provoke. But not to start a pull when there's absolutely nothing on you to begin with.


Reply With Quote

