Issue with default/group bindings
Prophetnoata opened this issue · 4 comments
Describe the bug
This may not be a bug itself or just confusion on how the addon is supposed to work, or maybe the addon isnt building the syntax correctly.
So I'm not sure if i am just messing with the settings wrong, but i expect when I make a macro of the same grouping is like how this macro executes.
#showtooltip
/cast [mod:ctrl,@player] [@mouseover,help,nodead] Unleash Life; [@mouseover,harm,nodead] [harm] Lightning Bolt; Unleash Life
So this macro casts Unleash life on me if I'm not targeting or mousing over anything. It cast lightning bolt if i mouseover or target an enemy. But if i mouseover a unitframe or press ctrl it still heals me.
The part that is failing on the addon side for me is the casting on myself if nothing is targeted/mouseovered. If i set the heal to default, it will now cast my healing spell without target but it wont cast my dps spell. I have tried changing the grouping with riptide as the default or flame shock as the default and unable to get this to work.
Clicked Version
Clicked 1.16.9
World of Warcraft Flavor
Retail
Tried with only Clicked enabled
- Yes
- No
Lua Errors
No response
Reproduction Steps
Create Healing Spell - Bind to a Button
Crease Damage Spell - Bind to the same button
Set Targets to Mouseover and Target for DPS Spell and Mouseover/Default for heal spell
Last Working Version
No response
Screenshots
Debug Output
No response
Hi :)
Try setting them to the same action group — that will make them combine into one /cast
command.
Hi, Apologies if i wasnt clear, I've tried that too.
If you dont set Riptide as default, it doesnt cast without a mouseover/target.
But if you set it as default the macro never reads the rest to ever use flame shock.
And if you ever set flame shock as default it wont use riptide without a target. But if you set the macro to target player, it wont prioritize flame shock either.
This has been my main gripe with Clicked since it has been made available for download is that the options in targets are not actually a priority. I have to manually create a macro with the correct priority and then it works as expected.