Marco

[Rosess]

Sooo I guess you can say im new to this. After soloing my war to lvl 11 I got into my first group.. And I guess I had a lack of commands to help the grp.

Here's where the question comes in..

Is there any sets of marco commands I should make?

Opinons/comments wanted~


A horrible noob

[greysenn]

Polo!

[greysenn]

On a more serious note..

You want some sort of a provoke macro
/ja "Provoke" <t>

Some sort of incoming macro..
/p Incoming <t>

Something for TP reporting..
/p TP = <tpp>

Probably something for berserk later..
/ja "Berserk" <me>

And some weaponskills..
/ws "Weaponskillname" <t>

Those are mostly what I use, as you get more later depending on your subjob, and should be using alt/cont +A for attack, and +D for ranged attack

[Brennon]

heh. . . don't forget to add lines to inform your party of what you're doing also

my provoke macro looks like this

/p "Hey, <t>, over here!"
/ja "Provoke" <t>
/wait 15
/p Provoke ready in 15 seconds!
/wait 15
/p Provoke ready! <call10>

I also have a macro to let my party know if my provoke is NOT charged and i lose aggro, and moster goes for mage. it lookes like this

/p "!!!!!!!!!!!!PROVOKE NOT READY!!!!!!!!!!!! <call>

and one of the backup tanks knows to provoke then. very useful, this one, especially when i'm playing with newer players that don't watch my voke messages, or for some other reason that ppl don't notice, battle spam, whatever. . .

those are the two most important macros for warriors, for sure. . . but make macros for your weapons skills, and other job abilities also. practice using them, so you don't have to look and can hit keys fast and accurately.

[greysenn]

Whoops.

Yeah, I can see adding a
/p Using Weaponskillname on <t>
line to the weapon macros.

Personally I hate the spam those provoke macro's generate, I guess it would be useful in a group where you're free for all tanking.. but eh :/

[ichnob]

I agree, though i do have a "/p random line stating i'm using provoke" just because, I have found that most people dislike having the

/p Voke is ready in 15 seconds!

line continually spamming the chat log. I usually am a good judge at when to use my Voke, so you'll maybe see me slip once every now and then, and follow it with a "/p bleh, 5 seconds left" line or something.

Also as a paladin (and maybe even future warriors), there's no need to have a voke timer for your voke macro later on in the game when you're using other macros right after provoke.

The usefulness of

/p Using <insert weapon skill> in 2 seconds
/wait 2
/ws "Name of Weapon Skill" <t>

cannot be denied though.

[bside]

Originally posted by ichnob
The usefulness of

/p Using <insert weapon skill> in 2 seconds
/wait 2
/ws "Name of Weapon Skill" <t>

cannot be denied though.

i strongly recommend that u to get rid of the "/wait 2" line, and learn the timing. the reason for that line must be that "if i hit this macro when i see the renkei graphics, it chains." don't be lazy, learn the timing, and don't let the lag or another macro interrupt the WS from being used.

[Armando]

I agree, though i do have a "/p random line stating i'm using provoke" just because, I have found that most people dislike having the

/p Voke is ready in 15 seconds!

line continually spamming the chat log. I usually am a good judge at when to use my Voke, so you'll maybe see me slip once every now and then, and follow it with a "/p bleh, 5 seconds left" line or something.

It's true that Provoke macros such as those tend to spam up the chat log...but just lately, while checking out the Paladin Forum, I found a way to make Provoke spam more useful - by telling what's your TP after each message. Some of you might find it useless, but it makes perfect sense to me...it keeps all the melees informed on what's your TP on a regular basis, so it reduces the chances of someone starting off the renkei when you're not ready.

My Provoke macro is:
/p [<Provoke> >> <t>] [TP:<tp>]
/ja "Provoke" <t>
/wait 15
/p [<Provoke> will be ready in 15 seconds.] [TP:<tp>]
/wait 15
/p [<Provoke> <Ready!>] [TP:<tp>]

*Note: The <>'s (with the exception of <tp>, of course) are terms from the auto-translate function. I like to stay JP party-friendly.

i strongly recommend that u to get rid of the "/wait 2" line, and learn the timing. the reason for that line must be that "if i hit this macro when i see the renkei graphics, it chains." don't be lazy, learn the timing, and don't let the lag or another macro interrupt the WS from being used.

Well, yes, and no...For one thing, it's the ideal way to start the chain - it gives a heads up to everyone AHEAD of time. (I can't count how many times people have just gone and fired their WS's mid-battle just 'cuz they felt like it, or without checking with the other melees if they have TP for the renkei ><) Also, the message is more visible and other people have less chance of missing your WS. I have to agree with bside, though, that you should try to keep things as manual as possible. One of the main reasons is the one stated above, that macros can fail...the system can't do two things at once, you know, and that applies especially to its timer...the problem doesn't just lie in the WS macro being interrupted, but also that the /wait command in the renkei macro will interrupt other /wait commands from a previous macro, like, say, the Provoke one, and cause you to not recieve the "Provoke is ready!" message you might rely on. Another good reason is that if you over-rely on macros, and someone fires off a different WS than what was planned for whatever reason, you might not be fast enough or accustomed enough to the menus to use a different WS yourself that can chain off his. A different renkei is better than no renkei at all, (unless you can do something stronger with someone else that is, but that's besides the point.) Do try to manually activate your WS's and other miscellaneous abilities that don't require the party knowing, like Boost, whenever possible.

The bottom line - Use macros wisely, but don't rely on them. A truly skilled player knows when to use them and when it's best to do without them ^^

[Rico]

Originally posted by Armando
My Provoke macro is:
/p [<Provoke> >> <t>] [TP:<tp>]
/ja "Provoke" <t>
/wait 15
/p [<Provoke> will be ready in 15 seconds.] [TP:<tp>]
/wait 15
/p [<Provoke> <Ready!>] [TP:<tp>]

You took my Macro style D:

Mines

/p (|Provoke|) >> (|Target|) >> [<t>] TP >> [<t>]
/ja Provoke <t>

:p

[Valcarde]

Only thing I ask is...

Please don't make some stupid message for your Provoke message >.<

If I see one more person doing something dumb like, "Soandso uses <Provoke> by telling the monster "I did yo mama!" " I'm gonna go postal >.<

[Nodoka]

Please please please use a 'Using WS in 3 seconds' in your macro.

My spells are so long now that I have to rely on stuff like that. If I start casting from the text saying it started, I will miss the burst. And just guessing never works because sometimes the melee like to end the chain quickly, and sometimes they take their time. ~.~ Please use "Using xyz in 3 seconds" because it really, really helps.