Interesting. I'll have to try some out on a target dummy, but I have read that you can use .5 with the wait macro. Either way, I'll experiment with how long it takes and how long it takes me to do it manually.There is a lose in DPS. It really depends what you use the macro for. The /wait action is always a whole number, so 1,2,3, etc.
For example, as a ninja with high skill speed, with Huton active, GCDs drop to about 2.1 secs or so, give or take. If I were to have a macro for Dancing Edge it would be something like this"
/ac "Spinning Edge"
/wait 3
/ac "Gust Slash"
/wait 3
/ac "Dancing Edge"
Total this would take about 6 seconds before Dancing Edge can be cast.
With no macro and say a GCD of 2.2 secs that combo would take 4.4ish seconds to cast Dancing Edge.
Macro's for skill combos become worse and worse the more skill speed you get.
You can use /wait .5 but it will always round up. So basically /wait .5 = /wait 1, /wait 1.5 = /wait 2 and so forth. It's been tested and proven numerous times. Sucks though. :/
These are the most useful macros on Ninja.
/ac "Shadewalker" <1>
/ac "Goad" <4>
These macros will help you use these skills on these targets without interrupting your DPS. Just sort the party list and change the numbers in the macro as you see fit.
Be aware, that if you hit another macro BEFORE the Trick Attack actually fires, Trick Attack will not activate.If I make a Macro that has that as an icon for Ninjutsu, will it only display the ninjutsu icon or will it still change to show which ninjutsu can be cast once I input mudras?
For example i wanna do something like this:
/micon "Ninjutsu"
/ac "Ninjutsu"
/wait
/ac "Trick Attack"
This is so i can free up a slot for hotbar space (PS4) and it will attempt to cast TA if applicable. But if the Ninjutsu icon doesn't change during mudra input then it defeats the purpose. XD
Also, I THINK it would normally work, but it requires you to know the mob you're fighting. Would be a total waste of the TA if the mob turn at the wrong time. My NIN only have a few macros:
I keep these together to free up space. I use "DWaD" every time it's ready, and Assassinate for obvious reasons.
/macroicon "Dream Within a Dream"
/ac "Assassinate" <t>
/ac "Dream Within a Dream" <t>
This macro informs the group that Trick Attack is on the way:
/macroicon "Suiton"
/em is setting up {Trick Attack}.
After that initial macro, I then use the non-macro'd Chi > Jin > Ninjutsu.
This macro is for my strong offensive buffs:
/macroicon "Blood for Blood"
/ac "Blood for Blood" <me>
/ac "Internal Release" <me>
BFB is first because I need it to be first for my Duality > Aeolian Edge combo early in the fight (because using IR > AE give a lose of the IR potential crit).
Last edited by Jim_Berry; 01-02-2016 at 07:46 AM.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
{http://na.finalfantasyxiv.com/lodestone/character/3089119/}
I'm only against this macro because I spam all my abilities almost. For example, if Trick Attack is ready, I chose to prioritze that if all my other dots are still active and Huton is not wearing off. That said, if Trick Attack is ready but this macro only made it to "Gust Slash", then "Dancing Edge will never active. I'll be hitting your macros again, which will start over the combo, and I never applied Dancing Edge.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
{http://na.finalfantasyxiv.com/lodestone/character/3089119/}
I'm not NIN but I'm interested in macros. As for /wait, since every macro line is executed per frame, "/wait 0.5" and "/wait 1" actually takes 1033.3ms in 30 fps and 1016.7ms in 60 fps. The following macro will work if GCD is 2.1secs in 60 fps or GCD is 2.2secs in 30fps. I don't like this sort of macros because of missed skills, though.
/ac "Spinning Edge" <wait.2>
/wait 0
/wait 0
/wait 0
/wait 0
/wait 0
/wait 0
/ac "Gust Slash" <wait.2>
/wait 0
/wait 0
/wait 0
/wait 0
/wait 0
/wait 0
/ac "Dancing Edge"
If you don't want to delay actions, /micon should be on the last line.
macros is the worst think you can make for a melee dps in active skills, the only macro you can make is one for shadewalker to you maintank.
I don't use this macro. It was just an example of what can be done in relation to wait.I'm only against this macro because I spam all my abilities almost. For example, if Trick Attack is ready, I chose to prioritze that if all my other dots are still active and Huton is not wearing off. That said, if Trick Attack is ready but this macro only made it to "Gust Slash", then "Dancing Edge will never active. I'll be hitting your macros again, which will start over the combo, and I never applied Dancing Edge.
Wait, what does /micon being on the first vs. the last line do for a macro? That's kind of interesting.I'm not NIN but I'm interested in macros. As for /wait, since every macro line is executed per frame, "/wait 0.5" and "/wait 1" actually takes 1033.3ms in 30 fps and 1016.7ms in 60 fps. The following macro will work if GCD is 2.1secs in 60 fps or GCD is 2.2secs in 30fps. I don't like this sort of macros because of missed skills, though.
/ac "Spinning Edge" <wait.2>
/wait 0
/wait 0
/wait 0
/wait 0
/wait 0
/wait 0
/ac "Gust Slash" <wait.2>
/wait 0
/wait 0
/wait 0
/wait 0
/wait 0
/wait 0
/ac "Dancing Edge"
If you don't want to delay actions, /micon should be on the last line.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.