[GUIDE] Warrior: Skill Intensive Tanking

[Marxam]

Another helpful tip for macros is /micon "Ability Name" It displays the cd timer similar to if you weren't using a macro. I find it useful since it visually tells me when the next line is going to be queued.

Example:

/micon "Skull Sunder"
/ac "Skull Sunder" <t>
/wait 2.5
/ac "Butcher's Block" <t>

I must be stupid because I can't seem to get the lines to work without using /wait. In an earlier post you mention due to the fact that both skull and butcher share the same gcd that they simultaneously become available thus can be executed at the same time but that cannot happen. You also mentioned the /aq macro but I can't seem to get it to work. Is it put after the /ac line? If you could give an example that would be appreciated since I'm more of a visual learner and still pretty new to macros. Idc about one button presses as I do love a good challenge, hence why I'm sticking with war to the end but real-estate on the PS3 is seriously lacking and I have to hotkey my actions wisely. But thanks to this guide I was able to free up 4 slots and reduce all main threat rotations to just 4 so I'm loving it atm.

[Exrage]

It's not just a 10% crit rate buff, it's also a 15% extra healing received buff...

...you have to add a /wait 0.5. Otherwise, it will only activate Infuriate and miss the other actions entirely.

Again, within 9 seconds after your DPS/Combo macro you're back at 9% healing increased in addition to the damage/heal/enmity that comes along with spamming it. We're turning the difference on a heal for 500 between 575 and 545- really not that huge of a difference considering the heal that comes from inner beast further padding the difference. Will it matter at the coils of Bahamut? Yes. Will it matter at Hardmode Ifrit? No. They need time to learn this on their own brudda.

Also the Burst macro I posted works just fine without waits, again you don't need to include a /wait because once infuriate is used the first time it becomes unavailable causing the macro logic to move on to the next ability or unchained in your example. You will spam that button repeatedly and the abilities will only fire in order regardless of putting in /wait.

[Exrage]

Another helpful tip for macros is /micon "Ability Name" It displays the cd timer similar to if you weren't using a macro. I find it useful since it visually tells me when the next line is going to be queued.

I must be stupid because I can't seem to get the lines to work without using /wait....

An excellent point on /micon. You're also not stupid, macro logic merely forbids two abilities that share the same GCD from being fired simultaneously without being told to wait- the key is making it wait just long enough for the second ability to become available. The problem is it isn't sure-fire, you may skull sunder instead of butcher's block depending on lag and when you hit that button, so I personally don't like depending on macros I can't guarantee will do exactly what I want when I push the button.

And thank you, it's really nice to hear that my guide was able to help someone even if it's only just a bit.

[Exrage]

An update on the /aq[on and /aq[off], it turns out it was nixed in beta 4 as the developers were content with keeping /wait and combining the line order of the macro with the priority feature of the action queue. So there you have it, my apologies for posting old/irrelevent data even if it was outside the guide.

[Exrage]

A note on the burst macro as I keep getting questions, putting unchained before berserk ensures you use your wrath V ability as the animation CD tends to lag a bit for those on PS3 in some fights(graphics slow down game, you can still spam the button to ensure it goes off but why spam a macro that doesn't attack when you could be spamming heavy strike or massive hits combo to start your damage instead?).

[Sakasa]

Question on the marking macros. I was wondering is there a way to use a different marker if one is already active. I use a <mo> but because of that macro is bound to a mouse button I was wondering if there is any type of cycle or if statement usage that can be rigged up so i can mark a whole group as fast are I mark the first one.

[Exrage]

Question on the marking macros. I was wondering is there a way to use a different marker if one is already active. I use a <mo> but because of that macro is bound to a mouse button I was wondering if there is any type of cycle or if statement usage that can be rigged up so i can mark a whole group as fast are I mark the first one.

Why yes there is:
/mk attack <mo>
Marks whatever you're mousing over with an "attack" mark and will move to the next number until all are used.

/mk ignore <mo>
and
/mk bind <mo>
Follow the same mechanics as with attack- enjoy!

Edit* Note*** You can only have one mark type per macro, you can't hit one button to mark one type then mark a second type unless you want it to mark 1 attack then 1 bind then 2 attack then 2 bind and so on.

[Sakasa]

Why yes there is:
/mk attack <mo>
Marks whatever you're mousing over with an "attack" mark and will move to the next number until all are used.

/mk ignore <mo>
and
/mk bind <mo>
Follow the same mechanics as with attack- enjoy!

Edit* Note*** You can only have one mark type per macro, you can't hit one button to mark one type then mark a second type unless you want it to mark 1 attack then 1 bind then 2 attack then 2 bind and so on.

Cool thx I will test it next dungeon run. You wouldnt happen to know what happens if you double click the macro would it just assign them the next number in que? Just wondering if I should make a demark macro as well since I use my ctrl and shift mouse clicks for potions and such so i have a free button.

[Exrage]

Cool thx I will test it next dungeon run. You wouldnt happen to know what happens if you double click the macro would it just assign them the next number in que? Just wondering if I should make a demark macro as well since I use my ctrl and shift mouse clicks for potions and such so i have a free button.

Yup, multiple clicks of the button put the next number in sequence.

[Maelwys]

Yup, multiple clicks of the button put the next number in sequence.

Test it in a dungeon run.
When I tried that on my MDR , it did indeed mark the first five foes with Attack1 - Attack5 markers... but even after killing them, I couldn't mark any more foes afterwards.
I had to redo my macros inside the dungeon and resort to specifying "/mk attack1 <t>" etc.

It does seem to work in the field (once foes die you can mark other foes again) just not in dungeons.