Healing with mouseover macros?

[ObsidianFire]

The other thing you can do is just have the fallowing macro up and always have the Party list visible (the option is buried somewhere in options) and heal yourself by mousing over your spot in the Party list.

/ac Cure <mo>
/micon Cure

As a general rule, the less lines of code are in a macro the better

[Makeda]

As a general rule, the less lines of code are in a macro the better

Excess lines simply error out or don't execute without added delay.

Thus why I'm preferring:

/micon Cure
/ac Cure <mo>
/ac Cure <mo>
/ac Cure <tt>
/ac Cure <t>
/ac Cure <me>

First 'ac' can either trigger of fail from a GCD, second will then trigger if condition met, if not the 'tt' will cause it to hit my target's target - most likely the tank with agro. If that is an enemy, it was likely because I had a party member targeted, so the <t> fires... and if nothing was valid, it hits me.

This appears to be working now in the runs thus far. But will be keeping an eye on it just to be sure my results thus far are not luck.

[Rongway]

Excess lines simply error out or don't execute without added delay.

Thus why I'm preferring:

/micon Cure
/ac Cure <mo>
/ac Cure <mo>
/ac Cure <tt>
/ac Cure <t>
/ac Cure <me>

First 'ac' can either trigger of fail from a GCD, second will then trigger if condition met, if not the 'tt' will cause it to hit my target's target - most likely the tank with agro. If that is an enemy, it was likely because I had a party member targeted, so the <t> fires... and if nothing was valid, it hits me.

The <t> line will never fire in a realistic situation. Your target should, in all practical scenarios, have a target, and so either the <tt> line will work on target of target, or the <tt> line will implicit-target heal yourself. The <me> line will also not fire except when out of combat, since when you are in combat you will presumably be targetting something, and therefore the <tt> line will activate.

You're overcomplicating this. Just use <mo> and get used to resting your mouse over your party frame when soloing.

[ObsidianFire]

Excess lines simply error out or don't execute without added delay.

They actually do get read/executed by the computer, you just don't see the computer try to read/execute them, usually because you are preforming an action. The more lines of code before a "valid" option happens and the action goes off, the more the action is delayed. And the more the action is delayed, the more chances there are for another action to happen (from elsewhere in the fight) that will cancel that action out.

This is also why you want to put the "/micon Cure" line at the end of the macro. The computer has to "read" that line in addition to the "/ac" lines and that adds more delay. If you stick the "/micon" line at the end of the macro though, the computer doesn't have to read it before reading the "/ac" line so that the action goes off immediately.

A good example of how this delay works is with a Swiftcast/Raise macro. You can't just do something like this:

/ac Swiftcast
/ac Raise <mo>
/micon Raise

If you do, the computer won't be able to execute the "/ac Raise" because it's still executing the "/ac Swiftcast" line. Instead you have to put in a manual wait between the "/ac Swiftcast" line and the "/ac Raise" line like this:

/ac Swiftcast
/wait 3
/ac Raise <mo>
/micon Raise

That gives you time to finish casting Swiftcast before the computer tries to execute the "Raise" (adjust the wait time based on ping).

The only exception I can think of is when you are making a macro of an AoE ability so that it's a targetable ability (Salted Earth, Earthly Star, Shadow Flare). Then you want the computer to execute the same action as many times as it can until it sticks. So you end up with something like this:

/ac "Shadow Flare" <t>
/ac "Shadow Flare" <t>
/ac "Shadow Flare" <t>
/ac "Shadow Flare" <t>
/ac "Shadow Flare" <t>
/micion "Shadow Flare"

And here i just practiced using F1-8 while healing and switching targets once the cast begins rather than between casts.

This can be a problem if you have small hands. I can barely reach the "5" key on my keyboard without taking my fingers off my hotkeys. Reaching any of the Function keys (esspecially anything greater then F4) requires moving my entire hand off the keyboard and by the time I have to cast the next spell my fingers aren't anywhere near those hotkeys.

Given that Tab-targeting in this games sucks, using a bunch of <mo> macros to switch targets often can often be the fastest way to do it without sacrificing something else. In my case, casting the right ability when I need to.