- Joined
- Apr 25, 2004
- Messages
- 1,690
- Age
- 44
- Location
- Vermont, US
- Main Job

- Secondary Job

- Third Job

- Server
- Quetzalcoatl
- Linkshell
- OwMyFace
- FFXI
- Vilurum
What's wrong with an attack macro? "/a <bt>" I use it all the fucking time and hit flash and provoke simultaneously (Yes, you can do both at the same time if you know which to hit first.)saving me about 3 secs which I could use for provoking again. That's just me on my PLD, and that's what makes me a good one.
Oh and yes, I do pay attention. It also helps in places like Crawler's next where you don't know which tunnel the mob will come from. Not to mention that huge nutsack hanging from the ceiling blocking your view.
As for that bio + stun that he has on his macro, I bet the JPs were pissed because he would stand there so that those spells would be able to go off. You should make seperate macros for those spells.
That is all >>
I explained the problems with using <bt> for anything except *maybe* a /target macro, in my previous post. It basically can really muck stuff up when you've got two or more mobs at camp (such as a pop, a link, or an aggro, one of them hopefully napping). There's no real consistency in whether <bt> picks one claimed mob or another, so some of the time it'll have you going after the sleeping mob instead of the mob you're supposed to be fighting.
This becomes increasingly common the more fast-paced your party style is, because eventually the idea will be to have the next mob cheerfully napping at camp when the first mob dies. Ultimately you never want any macro to have you do *anything* to a <bt>, except possibly target it. But definitely not anything that could damage it, such as pulling out your weapon.
As for putting other stuff into the macro, it's not *quite* so bad with an "/attack, Flash, voke" macro on PLD as with Helius's macro (since Stun is more situational and he has no need to get the hate from it, and Bio just plain sucks), but it's still got concerns. Mainly having to do with the respective ranges. You can pull out your weapon when the mob is 30 distance away, you can Flash it at about 21 distance, and you can voke it at about 16 distance.
Which means you'll probably need a few pauses in the macro to get the timing right (if you hit it when the mob is 30 distance), and if by some chance - say, a helpful RDM using gravity, or the mob taking stupidly circuitous routes to camp - it's not getting to camp as fast as expected, then the pauses in the macro don't work out either. (You definitely don't want to wait until it's *at* camp to be doing any of those things, since you can and should do them as it's approaching. So it arrives at camp and promptly wants to eat your face without first going after anyone else, which is the desirable outcome for a PLD.)
Therefore, it's easiest and most consistent to make separate macros for each, especially since you'll be wanting to be able to use Flash and voke independently (when voke's timer is up, and either when Flash's timer is up or when you need the mob to whiff for whatever reason) and not simply on incoming pulls. Then just hit the macros at appropriate times. (Even if you don't use Windower Distance, it's easy enough to learn the ranges and be able to eyeball it.)
Yes, it requires paying a bit more attention. No, it is *not* hard.