[SCH] Macro and Targeting Issues

[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.