I’ve been waiting to respond until I got some systematic explanation of what you want, but that doesn’t seem to be forthcoming.
From what I see, this is what you’ve asked for (expressed in verbose, but plain English - no code or computer science needed - just disciplined writing):
- If I have an arena1 unit then cast Master’s Call on it.
- If I haven’t yet cast Master’s Call this button-press and I have an arena2 unit then cast Master’s Call on it.
- If I haven’t yet cast Master’s Call this button-press and I have an arena3 unit then cast Master’s Call on it.
- If I haven’t yet cast Master’s Call this button-press and I have the shift key held down and I have a helpable focus unit then cast Master’s Call on it.
- If I haven’t yet cast Master’s Call this button-press and I have the control key held down and I have a helpable mouseover unit then cast Master’s Call on it.
- If I haven’t yet cast Master’s Call this button-press then cast Master’s Call using the default behavior.
It’s likely I’ve got this wrong, but it’s been days and I thought I should give you something. Unfortunately, my mind-reading abilities aren’t working. I’m going to have to make do with what little you provided.
To get this right, I need to know what you want to do and in what priority should it happen, not in broad “do what I mean” strokes - in detail. I gleaned that priority list from what you’ve provided so far, but as I said, it’s likely not what you really mean.
You are never going to be happy with shift-key modifiers on the numpad. Remap your Naga device to use values other than the numpad values or find another modifier.
I’ve written this assuming you’ve remapped your Naga.
I strongly advise using #show instead of #showtooltip to give you at least a hope of spotting when you’ve failed to move the macro into the action button (try it with both and you should see what happens that differentiates them).
#show
/cast [@arena1,exists,nodead];[@arena2,exists,nodead];[@arena3,exists,nodead];[@focus,help];[@mouseover,help];[]Master’s Call
There is no need at all for that “(Cunning Ability)” suffix. Beast Mastery Hunters do not have an overlapping ability named “Master’s Call” available to them and it clutters up the macro.
Unless there is a requirement I can’t suss out of what you’ve written there is no need to code for presence or absence in a raid.
If you DO need to code for presence or absence in a raid, don’t use that raid6 nonsense. There’s a conditional specifically for that - [group:raid] - the negative is [nogroup:raid]. Using this conditional lets you convert a 2-member group to a raid to test your macros, for one thing.
If you want to try again on a priority list, a useful priority list that doesn’t require telepathy to decipher, I’ll check back later and revise as needed.
<grin>