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)