[SCH] Macro and Targeting Issues

[giantslayer]

Putting "/micon" on the first line is nothing but a waste of time.

Whoa. I had never thought of that. I'm gonna have to see if I can confirm the difference in execution speed. If that is correct, then I will be in your debt.

[Spoekes]

Because it takes 0.05-0.1 sec between Physick and Embrace in your macro (16.7-33.3 ms/line). I suppose the following is better.
/pac "Embrace" <t>
/ac "Physick" <t>
/pac "Embrace" <me>
/ac "Physick" <me>
/micon "Physick"

Basically <t> and <tt> can't be combined on the same macro.
Putting "/micon" on the first line is nothing but a waste of time.

Combining <t> and <me> in one macro seems pointless for me.
To my understanding you usually macro <t> to stop the fallback on <me>, which happens automatically if you don't add any target variable.

/pac "Embrace"
/ac "Physick"

will do just the same thing in 2 lines, won't it?

<t> and <tt> can be combined on damage spells, E4E etc. just fine, where as <t> on a healing spell defaults to <me> if an enemy is targeted.

This is the first time I hear of /micon and other macro-lines adding macro time and I don't believe thats how it works at all.

[Mikoko_Miko]

Combining <t> and <me> in one macro seems pointless for me.

They differ only when you target nothing. <t> & <me> heals <me> and <t> heals no one.

Sorry for my lack of explanation. My intention was <t> and <tt> can't be combined in healing spells. Once I tried to combine <t> and <tt> and got this ugly macro.

The difference in execution speed by "/micon" is very slight (about 16.7-33.3 milliseconds, depends on frame rate). It might be realized by comparing these macros.

/ac "Physick"
/micon "Physick"
...
/micon "Physick"

and

/micon "Physick"
...
/micon "Physick"
/ac "Physick"

[Mikoko_Miko]

/pac "Embrace"
/ac "Physick"

will do just the same thing in 2 lines, won't it?

Thank you for useful information. When I target nothing, yours did the same thing with Physick but did not with Embrace (it healed Fairy instead of me). So I update my macro.
/pac "Embrace" <t>
/ac "Physick"
/pac "Embrace" <me>
/micon "Physick"

As for macro execution speed, I could find information only in Japanese language and is not officially confirmed. According to it, macro executions are synchronized with frame rate. If you are in 30 fps it takes 33.3 ms per line and in 60 fps it takes 16.7 ms per line. It seems correct for me after several attempts.

[Rawrz]

I would forego the whole /pac Embrace <me>. The frequency of you manually having to heal yourself at above 80% is very low. Your fairy will always prioritize your life over anyone else's. Plus, you could just hit F1/Press down on the D-pad to target yourself. >:O! Just a thought!

[giantslayer]

I just tested it out. It is difficult to tell the difference with just one micon line, but if you stick a bunch of them, it is easy to feel the lag. The one place where I could really notice the difference is in looking at the icon. When you hit a button, it makes a little circular animation on the button every time you press that button, and then the skill darkens for GCD. I noticed I could see more of that circular button press animation on the one micon at the end, meaning that because of the slight delay in the GCD being executed, a split second less of the button press animation was visible.

Hopefully that wasn't too confusing. Bottom line is Mikoko is correct about the micon taking time just as any other macro line.

[Spoekes]

wow if this is really the case... shame on the intern that coded this one..

The macro system is weak to begin with, but I would have never thought it's so broken that the /micon line takes macro time.

[tjw]

To be fair, if it's part of the lines in a macro, it's going to be read and executed regardless, so complaining about a /micon line taking time is about as useful as complaining about /echo lines also taking up time (Hint: they do). Any lines you put into a macro will have macro time. To expect a /micon to not have macro time is just foolishness.

And in any case, it's only 30ms or so. Not game-breaking enough to be a real big difference.

[Ravenholme]

I play on PC mouse and key board so I don't use the Circle Type Targeting used when executed with a controller. That being said I think the circle type target is seen in game as a mouse over. It could be worthwhile to try using the <mo> target placeholder and see if that does what you need.