In most of my bindings I put mouseover first since that is the one I would want to have prioritized. However I tested it today and in a standard form with a mouseover / target scenario, the target was ALWAYS selected even if I had a valid mouseover target. (Like I had a mob targeted it would always try to hit with sunfire, even if I had a valid help mouseover (another toon, me)

Can you check into it or let me know how to prio one over the other since it's not clear? (I thought perhaps if its first in the listing of abilities it would do that but perhaps not.)

Maybe it's looking at them individually and not together (help,harm) ?

Ideal situation is to have it prio whatever you have first in the abilities but would hopefully be able to see that you have a mouseover help even though you have a target harm. My macros do this.

Attached screenie

Could you post the contents of /cc dump? Thanks

Hm, the phrase @mouseOver isn't used by anything built-in as that always refers to @mouseover (lower case O)

Check the binding for Rejuv as that uses @mouseOver as well

So your Sunfire binding looks like this:

/use [@mouseOver,harm,exists,form:0/5/6] Sunfire;
[@target,harm,exists,form:2] Shred; [@target,harm,exists,form:0/5/6]
Sunfire; [@mouseOver,help,exists] Rejuvenation; [@target,help,exists]

Is the other Sunfire binding a custom macro? The loaded and unloaded info for bindings restricting the active form is fake due to Blizzard API restrictions (cannot change action buttons in combat). So if that is a custom macro that you've set to only load in form 0,5,6, it will still add add it (it just shows as unloaded in the UI as it could never be trigged in the current state).

Custom macros in general break all of the prioritization rules and whatever you put in there is either put in front of after the auto-generated stuff, depending on the option you set.

Prioritization is roughly:

1. combat/nocombat modifers
2. forms modifiers
3. Mouseover target
4. Everything else with a help/harm modifier
5. Everything else with a dead/alive modifier
6. Everything without modifiers
7. Player target
8. Default target

So with four bindings:

• Target
• Dead target
• Friendly dead target
• Friendly target

It will be prioritized as follows:

1. Friendly dead target
2. Friendly target
3. Dead target
4. Target

Hope that helps :)

From #15:

Thanks! I managed to find what's causing it, it should be fixed in 0.10.0. I've also added a "Status" page to each binding which shows the generated macro(s) and all bindings that affect it:

Note that my change inverted the priority of bindings using the form (or combat) flags, they incorrectly got the topmost priority and now they will get the lowest priority above @player and default targets. You can still add help, harm, dead, nodead, etc. modifiers to them to bump them up in priority :)

This should now work as you'd expect it to.

Hm that's not good. Where did that happen? After interacting with the UI?

Any chance you could post the error you're getting? If it happens again

I can't see any screenshots you post no, try replying on GitHub.com instead of via email