I've done it! I've Discovered a new Recipe! For Mch

[Alchemii]

Ok, I threw this together, and tested it as best I can, this morning while having very limited time to do so. Thus it is in need of some fine tuning, but I felt I should go ahead and share it with others in the hopes of helping others with at least one of the mch problems.

What I give you is a macro. The idea is to set up a macro to set off hypercharge, then Overload, followed by redeploying the turret, without the player having to worry about it.

/macroicon "Hypercharge"
/merror off
/macrolock
/ac "Hypercharge" <wait.25>
/ac "Rook Overdrive" <t> <wait.1>
/ac "Rook Overdrive" <t> <wait.30>
/ac "Rook Autoturret" <0> <wait.1>
/ac "Rook Autoturret" <0> <wait.1>
/ac "Rook Autoturret" <0> <wait.1>
/ac "Rook Autoturret" <0>

The spamming during the macro is a just in case your pressed a button at the wrong time, and it conflicted with the either performing the Overdrive or redeploying the turret.

Now this macro isn't perfect, obviously if the turret fired at just the wrong time, your gonna loss that 1 auto-attack, but it's equally as good of odds that it won't and you'll have a dps gain. To top it off if you have a ninja in the party and the two of you were coordinating your trick attack and hypercharge. This could be adjusted to allow you to use Overdrive within the trick attack window and hypercharge window for a dps gain.

I did test it with a 26 second delay between Hypercharge and Overdrive to allow for every possible shot to go off as possible during the vulnerability period, and found that with the animation and command delay Overdrive would go off during the final second of the vulnerability delay, however that had me concerned that if the turrets shoots didn't line up just right you'd end up using it when there was any Vulnerability so I moved it back by 1 seconds.

Also it should be noted if Overdrive fires off with the second input rather than the first, the first entry of redeploying the turret will fail, as the time is too exact.

Remember if you are use another Macro before this one, then use this one, the first macro will be canceled.

The reason for the 1 and 30 second windows is because those are the minimum and maximum amount of time you can macro in game, at least from what I've heard if I am wrong please let me know.


Edit: Sorry was kind of on a time crunch when posted and didn't realize I forgot to Add this. This is not a catch all, and is mostly just a safety net in case the User either knows they are going to have trouble keeping track of the Vulnerability stack, or simply forgets to recast their turret. The macro is going to get cleaned up this afternoon with more details added to it.

Alternate idea, and the one I actually use since I play with a controller, I've made 2 macros one to use Rook Overdrive and the other to Deploy the turret. The reason for these macros are simple, they swap my Crossbars on use. So I use Rook Overdrive and it changes to a second set of crossbars that has Rook Autoturret in it's place and vice versa.

Marco #1
/macroicon "Rook Overdrive"
/ac "Rook Overdrive" <t>
/crosshotbar change "4"
/wait 27
/echo Deploy Turret in 3 seconds <se.4>
/wait 3
/echo Deploy Turret <se.4>

Macro #2
/macroicon "Rook Autoturret"
/ac "Rook Autoturret" <0>
/crosshotbar change "1"


The reason it's 1 and 4 is pretty simple. Crossbar 1 is my primary bar, 2 is mostly for AoE attacking, 3 is used when using the left and right triggers together to give me quick access to an additional bar, and 4 is the one to replace 1. (obviously)

[Fannah]

Hey, just to help

As far as I know, "/wait" doesn't count decimals and will rounded up. So "/wait 0.5" is the same than "/wait 1" (or tell me if they patched it and you see any difference). (and the limit is 60, not 30).
<me> is irrelevant in your macro for "Hypercharge".
We are limited to 15 lines, so just in case, you can write the same wait macro by adding <wait.X> at the end of each line to gain some.
Add "/merror off" to don't get any red messages if you happen to have a problem with the macro (for exemple when you're synced and you don't have "Rook Overdrive" anymore).
Change the /wait 30 in /wait 29 as you already used a /wait 1 after the first use of Overdrive (or let me know if it's not working because too accurate for the game in case of lag, then keep your 30sec).
Keep the /wait 1 and /wait 29 the way you did as you will have trouble if you don't have the skill because of low roulette content. --> If you don't have the skill because of sync, it will cancel the whole line, so the <wait.X> too. Which is why you want to still tell him to wait in another line to use the next skills the way you want.
You didn't write "Rook Autoturret" the same way everytime, so we can't just copy it and will have to change the spelling.
It will give something like :

/macroicon "Hypercharge"
/merror off
/ac "Hypercharge" <wait.25>
/ac "Rook Overdrive" <t>
/wait 1
/ac "Rook Overdrive" <t>
/wait 29
/ac "Rook Autoturret" <0> <wait.1>
/ac "Rook Autoturret" <0> <wait.1>
/ac "Rook Autoturret" <0> <wait.1>
/ac "Rook Autoturret" <0>

Knowing macros cancel other macros, you should warn people about it so they don't try to cross macros thinking both (or more) will work at the same time.

You also have something called "/macrolock" (or maybe "/macrolock on"?) to prevent another macro to run and cancel your current one.

[Petori]

I don't like multi-action macros for battle. They can fail due to lag or cause GCD clipping if an action goes off at a bad time, which can potentially mess up your flow.

[Fannah]

This is why he made actions repeating in the same macro. GCD are usually between 2.35-2.50s. So if his macro fail the 1rst time, it should work the second time just 1 sec later (if he doesn't use an oGCD meanwhile).

I believe it's a waste of time too, and I realized it's kinda clunky to feel like "yea, so my macro will arrive soon, I have to be sure I'm not using a GCD or oGCD during those few moments a skill should be landed".

But I still wanna let him try and see if it fits his way to play. I won't stop someone who is trying to experience things. And who knows, maybe it'll be good for him.

[Petori]

Yeah it might be helpful to some people so I'm not trying to discourage people from trying it out, but it's good to know about the risks too :P. Personally I use /echo <se.4> macro with overdrive so I don't forget to put Rook back out like when I'm doing mechanics and not keeping an eye out for the debuff.

[Elnidfse]

The real problem with this is that there are many, many, many times where you want to hold onto that turret for whatever reason or you can't play one at that moment for another reason. Funky situations like you need your OGCD spot so you can double weave something. I can see situations arise where it comes off of CD and you need to use your OGCD action command to levitate in catastrophe and your levitate gets eaten by Turret attempts.

[Alchemii]

-snip-

For your question about timing, my understanding is that it recognized 0.5 seconds as half a second, though I'm not sure if it recognizes any other decimal of a second. As for the wait 30, I actually did account for that. In my testing if you just used a 30 second wait, the macro would attempt to launch the first turret just before the 30 second timer stopping turrets from being launched would end, so for the macro you'd want a total wait of 30.5 seconds.

I wasn't aware of those macro commands I'll make sure to add them into the macro when I get home, and make sure everything gets cleaned up. Thank you. ^^

-snip-

I'm usually not a fan of them either. This is mostly in case the person using it forgets to throw them out. I would use the <se.4> and other such sounds, but I tend to run with tanks and healer that like to use those alot to notify resing and other big CD moves.

-snip-

As mentioned in the post, and by Fannah, that's the reason for the macro spamming the commands. However, as for your concern about Levitate, if a skill is on CD when a macro attempts to use it, it will simply come up with an error message rather than actually canceling any other skills your attempting to use. Further note, based off my experience with macros it seems that manual inputs always trump macro inputs unless the action is already underway, in which case there is clipping.

[Fannah]

That's clever Petori
And yea Elnidfse, so long macro definitely doesn't help with the importance of adapting to fights :/ I also clearly don't want to encourage him to keep them. It's that I just believe I could give him some macro help according to his current macro knowledge, so he could try other ones and more optimal ones.

On my side I took a skill bar to set it in 4*3 and I've set all the oGCD in it (which works as we have lot less of them now). So I can always get a quick view of all my oGCD.
I know there is also another macro to read in the chat your cooldowns (used to some synergy things, but I don't advise people to use it overall) :
It looks like (I picked random MCH skills) :
/p -------- CD's ----------
/p Rook Overdrive: <recast.Rook Overdrive>
/p Reload: <recast.Reload>
/p Ricochet: <recast.Ricochet>
/p Reassemble: <recast.Reassemble>

It can be just put in /e too, of course, if you find any use to it

[AmandaLashaquoa]

I have two macros too, I don't know if they're harmful and if they are I would please like to be notified!
I do use one to place the turret near me and another for Refresh that warns me that it will be up in 120,60 and ready to use, so it ticks 3 times, I haven't noticed if it does anything bad to my rotation, but if it does, please somebody tell meh!

[Alchemii]

-snip-

Once I get home I'll test it. I'll also be posting another set of macros I use with the controller, to swap the crossbars when using Overdrive and deploying the turret afterwords. That way they don't take up any extra spots.