Forum Settings
       
Reply To Thread

Pulling MacroFollow

#1 Jan 13 2004 at 12:32 PM Rating: Decent

I had a puller in my group the other day that had a macro that said the mane of the critter that was being pulled and also made a whisle sound. Anybody know how to do this macro?

Thanks-kurru
#2 Jan 13 2004 at 12:36 PM Rating: Decent
*
182 posts
I assume you mean "name" when you say "mane."

The name of the target is <t>. Sounds are <call1>, <call2>, etc. For instance:

/p Pulling <t>! <call11>

yurik (Unicorn) MNK/20 WAR/10 -- Windurst
#3 Jan 13 2004 at 12:37 PM Rating: Decent
Unless your group is having a hard time paying attention, I think the whistle would be annoying. Anyhow...

/p Pulling that <t>
/p <call1>

<t> is target, <call1> is the whistle... the number can be changed for different whistles.
#4 Jan 13 2004 at 12:38 PM Rating: Decent
*
133 posts
/p Provoking <t> !! <call1>
/ja "Provoke" <t>
/wait 20 seconds
/p Provoke will be ready in 10 seconds.<call##>

there're many different types of calls, from <call1>-<call25> i think.
#5 Jan 13 2004 at 12:39 PM Rating: Decent
*
133 posts
lol 3 of us replied at the same time ;p
#6 Jan 13 2004 at 12:48 PM Rating: Decent
*
183 posts
I have three, actually.

Crtl1 (For when a mob pops close, this will provoke and attack in one move):
/p Pulling a <t>!
/ja "Provoke" <t>
/wait 1
/attack <t>
/wait 20
/echo Provoke ready in 10.

Crtl2 (For when I want to **** off a mob and run it in):
/p Incoming, <t>!
/ja "Provoke" <t>
/wait 15
/echo Provoke ready in 15.
/wait 15
/echo Provoke ready.

Crtl3 (For long distance pulls with a ranged weapon like a boomerang):
/p I just 'ranged me a <t>, incoming!
/ra <t>

#7 Jan 13 2004 at 12:54 PM Rating: Decent
tyvm
#8 Jan 13 2004 at 1:09 PM Rating: Decent
**
805 posts
Pulling without a warning macro can be dangerous. I use it to not only wake people up (some pulls can be a long run back) but also as a warning to jittery newbs not to attack something.

I don't like to combine the attack macro with the warning macro as on a long pull, I might wait until I'm closer to camp before sending the warning.
#9 Jan 13 2004 at 1:14 PM Rating: Decent
**
364 posts
Those pulling Macros are great information, whether I am drawing something in or making sure that others know I am coming with Death on my coattails..:) Unforunately, sometimes you do not get the <call> audiable (sp) because of the battle, spell casting, screams of people running by you, etc. I just hope people are keeping a decent eye on their Text window....
#10 Jan 13 2004 at 1:18 PM Rating: Decent
**
389 posts
If you have JPN players in your group then you may want to put translator phrases in your pulling macro.

I use:
/p {Found it!} <t> <call2>
and
/p {Lock on} <t> <call2>

In would be nice in "Incoming" or "Pulling" was in the translator but, alas, it is not to be.
#11 Jan 13 2004 at 1:19 PM Rating: Decent
40 posts
I like to do this...

/shoot <t>
/wait 10
/p Incoming <t>, wake up <call1>!


The "/wait 10" works out very well for those annoying situations when the target may be out of range and you need to keep readjusting yourself and buys you 10 seconds before the call message goes out. 10 seconds seems to be very good on timing, as that is enough time to actually shoot, aggro the target, turn around and actually be running back to the group before the message always goes out. I try to keep a blank macro on each bar as a cancel button. If I need to cancel a macro with a /wait statement I hit that and all is good.
Reply To Thread

Colors Smileys Quote OriginalQuote Checked Help

 

Recent Visitors: 808 All times are in CST
Anonymous Guests (808)