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.

[Naryoril]

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

This. There is no time loss for selecting targets if you are planning ahead for what you are doing. You should basically always be casting, and while you are on global cooldown (e.g. because of your current heal or attack spell), you can already select the target of your next heal, you have over 2 seconds (your global cooldown) to do that. The only situation where you don't have spare time to select your next target is if you want to cast off global cooldown spells in succession on different targets, but i highly doubt you'd be faster with mouse over. Even so you still have about half a second due to the animation lock, which should be enough to select your next target. The loss of time due to not being able to queue on the other hand is there for every single cast, even if it isn't much (depending on your lag), it adds up.

[EaMett]

What I find a little difficult to understand is why you would want to heal anything other than your mo? Like, if you're trying to heal a specific person there's no point in healing someone else. Are there scenarios where you can't hover someone's name?

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

[Naryoril]

Who said they wanted to heal something else? Apart from the apparently iffy targeting, the main reasoning against mo heals is that you can't queue them, costing you time between heals, and to minimize that time loss you have to trigger the button to lose as little time as possible, which sounds extremely annoying.

But there even is a drawback concerning the mouse cursor: With mo, you have to be with the mouse over your target the moment you want to start casting your heal spell. If you work with targetting, you just have to select the target at some point in the 2 to 2.5 seconds before you have to cast the heal, so if you select early in that time frame for one spell, and late for the next spell, you have about 4 seconds to do something with your mouse. For example you could get a better overview about the battlefield by panning the camera around or something like that. You are simply more flexible with what to do with your mouse, even though in most cases it won't matter.

[Makeda]

Who said they wanted to heal something else? Apart from the apparently iffy targeting, the main reasoning against mo heals is that you can't queue them, costing you time between heals, and to minimize that time loss you have to trigger the button to lose as little time as possible, which sounds extremely annoying.

Significant time is lost in switching around targets.

Even more time would be lost if I were to use F1-F8 (keys not normally existent on my keyboard nor my Nostromo Orbweaver, so I would have to emulate them or rebind them onto my Nostromo, losing keys used for other actions. Besides I'm never using my keyboard when active anyway - I'm using the Orbweaver and the Mouse. The keyboard is just for out of combat chat and such). But even if I did plug in an external keyboard with Function keys on it, that is a wide spread to have one's fingers moving over - look into the ergonomics of that. Significant time and muscle strain would be wasted there.

With a mouse-over I can cast immediately on the needed target without interruption of other activities.

By having more than just <mo>, I can be fully fluid in how I select who gets a heal, and have plenty of fallbacks.

Essentially this allows me to heal faster, more like a blend between how I do in games like WoW, Wildstar, or Overwatch - avoiding the mess of 'targeting' - leaving that clunky old outdated gaming system to the DPS side of my actions (just as I have to do in WoW, which also uses to the outdated 'select a target' system).

The time loss of going through a short series of 'if-then statements' for software is in micro-seconds. Not worth noting.

[Mhaeric]

Significant time is lost in switching around targets.

Even more time would be lost if I were to use F1-F8 (keys not normally existent on my keyboard nor my Nostromo Orbweaver, so I would have to emulate them or rebind them onto my Nostromo, losing keys used for other actions. Besides I'm never using my keyboard when active anyway - I'm using the Orbweaver and the Mouse. The keyboard is just for out of combat chat and such). But even if I did plug in an external keyboard with Function keys on it, that is a wide spread to have one's fingers moving over - look into the ergonomics of that. Significant time and muscle strain would be wasted there.

With a mouse-over I can cast immediately on the needed target without interruption of other activities.

By having more than just <mo>, I can be fully fluid in how I select who gets a heal, and have plenty of fallbacks.

Essentially this allows me to heal faster, more like a blend between how I do in games like WoW, Wildstar, or Overwatch - avoiding the mess of 'targeting' - leaving that clunky old outdated gaming system to the DPS side of my actions (just as I have to do in WoW, which also uses to the outdated 'select a target' system).

The time loss of going through a short series of 'if-then statements' for software is in micro-seconds. Not worth noting.

I don't think you're understanding where they're saying the time is lost. Using function keys to select a target and heal without a macro lets you do it well before you have to actually cast the spell, even letting you hit the button to cast the spell before you are able to cast it and have it go off when it's ready and you can be using your mouse to do other actions like rotating the camera at the same time as doing this.

With a <mo> macro you can't pre-cast (just like with any macro) or pre-prepare your target. You have to both have the mouse over the target and press the button after, even if only by milliseconds, when the skill is already ready to cast. You can't press the <mo> macro button ahead of time, since macros don't allow queuing, and if you mouse over early to prepare the target early then you lose the capability to use the mouse for anything else at the time such as camera movement. I.e. With a <mo> macro (or any macro) you have to be really on the ball for timing or you lose GCD time. With function key targeting, you have a lot more leeway for when you can initiate actions and move without clipping into your GCD.

[ObsidianFire]

The use of using <mo> macros vs targeting with Function keys and the like is super-personal though. Everyone has a different keyboard+mouse set-up and a different way of setting up their UI which affects how easy it is do do <mo> healing (some people prefer clicking hot-keys with the mouse!). What works great for one person often doesn't work well for other people. If the OP really wants to use <mo> macros then don't just go trying to make them re-learn how to play the game just to suit what you feel is best.

What matters is if they play the game well enough to get though most content with the least amount of frustration for everyone they're playing with. And nine times out of ten that has nothing to do with how they set up controls on their end.