Broken Macros? /wait not working?

Sigh.. I loved doubling up certain tank macros that were on the same CD timer like:

/micon Foresight
/ac "Foresight" <me>
/wait 1
/ac "Featherfoot" <me>

but, besides finally feeling the "2.2 lag" in DF today, now these wait macros don't work, I click it, do nothing and only the first ability goes off. Have to press it again and wait a second for the 2nd one to activate?

Take out the wait and just mash the button, or make it a longer wait. 1 is probably too short to be reliable.

ugh I just wish there was /castsequence like in WoW, I don't want to mash the button over and over, it WAS working before now it's not.

You probably have /wait set too low.
Try setting up the macro as such:

Code:

---

/micon "Foresight"
/ac "Foresight"
/ac "Featherfoot"

---

Tap the button twice to get both to activate

Or try

Code:

---

/micon "Foresight"
/ac "Foresight" <wait.2>
/ac "Featherfoot"

---

Since they added the new <wait> syntax I stopped using /wait all together. Gives more space and looks cleaner. On top of that with the way the battle system is paced, using any wait is discouraged as it wastes minor amounts of time. During that macro you have a chance to lose hate to a rambunctious DPS whereas you have more control of other skills with the first macro I presented

hmm I wonder if the new <wait> is better then /wait does it work the same way? <wait 1> = /wait 1 ?

It works the same way, just lets you use more lines in a single macro.

You're getting killer lag, I:
ac bloodbath
Wait .5
Ac berserk
Wait.5
Ac vengeance

And it goes fine. It's actually longer than that as far as how many abilities but .5 works for me except for when you hit super high lag in the new em dungeons

I've had a lot of people say they don't get off .5 ever which I never get, my Pali in macro can hit
Ac fast blade
Wait 1
Ac circle of scorn
Wait 1.5
Ac savage blade
Wait 1
Ac spirits within
Wait 1.5
Ac roh

Doesn't help in newer content but it still goes off

There is no point using decimals in wait commands as those are being ingnored / rounded up so your wait .5 is actually wait 1 and your wait 1.5 is actually wait 2

Quote:

---

Originally Posted by HEC

There is no point using decimals in wait commands as those are being ingnored / rounded up so your wait .5 is actually wait 1 and your wait 1.5 is actually wait 2

---

And this is the one inconsistency between /wait and <wait> (AFAIK). /wait rounds decimals (.5 and up go to the next whole second), while <wait> always truncates/rounds down. At least when I tested it right after they introduced <wait>.

I've found that any macros I made before, with /wait lines, the wait no longer works properly. I had to convert them all to <wait> to get them working again.

Quote:

---

Originally Posted by Bixby

And this is the one inconsistency between /wait and <wait> (AFAIK). /wait rounds decimals (.5 and up go to the next whole second), while <wait> always truncates/rounds down. At least when I tested it right after they introduced <wait>.

---

Well - it's was clearly mentioned in the patch notes that new <wait.n> (sub-)command doesnt support decimals - it also needs to have dot between wait and n number (0 -30 only) so whatever string you'd squeeze in after the fist digit or 2 would be at best case ignored (the "trimming") or at worst produce the error.

it certainly would be nice to have decimal support in our wait timers for macros again. it doesn't make much sense to me as of to why they removed it. especially with the default global cooldown set to 2.5seconds. it really doesn't make sense. other then performance related issues, there is no logic to the change.

Well - the "explanation" from SE's top brass was that they don't want to make macros too "precise" to put players who don't (want to / know how to) use them to dissadvantage, to be pressurised to used them or being abused by others for not using them ... which is IMO pretty LAME "excuse". This "PC" approach is simply wrong and results in nothing else than people using 3rd party precise scripting / macroing tools instead of the ones built-in directy in the game. It's lame at the same level as if they'd remove the chain combos with the claim it's to "difficult" and put those who're unable to (properly) use them to dissadvantage. SE - plase STOP baybisinting all the players and putting in silly limitations like this! ;(