A
Alerith
Guest
Fact or Fiction: Using Provoke to pull a mob generates massive hate on you to the point where its really really hard to get it off the puller?
Alerith said:Fact or Fiction: Using Provoke to pull a mob generates massive hate on you to the point where its really really hard to get it off the puller?
Raziella said:My hate guide
After you effect a mob (heal another player or attempt to strike), you end up on it's hate list. Think of the hate a mob has for a player as a value that slowly ticks down but never gets to zero (as this would constitute no battle and thus no hate at all). Basically, whoever has the highest number among everyone on the hate list is the one who's going to get attacked.
This explains situations where the mob moves "frantically" because what is actually happening is you have 2 or more people with hate values that are ticking down VERY close to each other and constantly changing who has the highest hate level. You can see this in even a more profound way when a mandragora sleeps a party and it's constantly switching between targets even though no one is hitting it.
annabelle said:I like to have a single macro dedicated to this:
/target <bt>
/recast Provoke
/recast Boost
/recast Defender
etc.
It does a couple things. First, it targets your party's claimed mob. This can be useful if you're not pulling -- I hit this macro until I've targeted the mob, then I spam my Provoke macro until it fires from max range (which is why I don't put /p lines in the macro and make myself look silly). This helps to line up the mob and melee faster, enabling the THF to land SA earlier on.
Second, it gives you a status on your abilities whenever you call on it. You can use the CTRL-J window, but I've always liked this method instead.
As a WAR/MNK, try and arrange a pattern of Provoke - 8 secs - Boost - 15 secs - Boost - 7 secs - Provoke again. You can throw a /recast Boost in your Provoke macro and a /recast Provoke in your Boost macro just to keep you updated, but use the /wait #, /echo Use Ability! lines as well.
Good luck!
Never ever ever have provoke <bt> macro. It can fuck fuck you up when trying to voke a link and leave you with a dead mage.annabelle said:I like to have a single macro dedicated to this:
/target <bt>
/recast Provoke
/recast Boost
/recast Defender
etc.
It does a couple things. First, it targets your party's claimed mob. This can be useful if you're not pulling -- I hit this macro until I've targeted the mob, then I spam my Provoke macro until it fires from max range (which is why I don't put /p lines in the macro and make myself look silly). This helps to line up the mob and melee faster, enabling the THF to land SA earlier on.
Second, it gives you a status on your abilities whenever you call on it. You can use the CTRL-J window, but I've always liked this method instead.
As a WAR/MNK, try and arrange a pattern of Provoke - 8 secs - Boost - 15 secs - Boost - 7 secs - Provoke again. You can throw a /recast Boost in your Provoke macro and a /recast Provoke in your Boost macro just to keep you updated, but use the /wait #, /echo Use Ability! lines as well.
Good luck!
If its for personal knowledge, then use /echoRambaldi said:Parties with more than 1 tank would beg to differ. Also, some people will use certain abilities or spells and time it so Provoke is ready right after their usage. Kinda hard to know when Provoke is ready if there is no party line giving at leats the 15 second warning.
I use:
/ja "Provoke" <t>
/wait 15
/p Provoke in 15!
/wait 15
/echo Provoke Ready!