I can't use skyriding abilities if a Clicked macro is in the same keybind. The [noflying] and [nobonusbar:5] conditionals don't seem to be working.
gotex007 opened this issue ยท 7 comments
Describe the bug
I don't know if this is a Clicked issue or a Blizzard issue, but it's causing issues with skyriding where I can't Whirling Surge because I have a Clicked macro for Purify Disease also on the 5 key.
I tried playing around with built in conditional tickboxes in Clicked itself and just couldn't figure out a way to make it work.
Clicked Version
1..15.3b
World of Warcraft Flavor
Retail
Tried with only Clicked enabled
- Yes
- No
Lua Errors
No response
Reproduction Steps
One macro I was using prior to prepatch was this:
/use [@mouseOver,help,nochanneling,noflying][@target,help,nochanneling,noflying][@Focus,help,nochanneling,noflying][@player,nochanneling,noflying]Purify Disease
/use [flying]Whirling Surge
Replacing [flying] with [nobonusbar:5] also does not work.
Last Working Version
Before prepatch. I don't know which version.
Screenshots
No response
Debug Output
No response
@tharax the game does not allow for a binding to "fall back" to action bars if no match is found. The macro conditions are always active as long as the binding is loaded and thus will always eat up your input.
It's not an addition to the button you assign it to, it's overwriting it completely. To make it work correctly I'd suggest importing your action bars into Clicked for functionality, and keep the bars for visualization.
@Snakybo still having issues, if I don't have spells for 1-4 then it won't default to allow me using my action bars.
For example, on my human warrior I can use Avatar (ALT-2
) but not Charge (1
), even when not mounted and in combat:
@Snakybo interesting, so the "Load conditions" tab can switch on/off a keybinding, but the "Macro conditions" tab can't? Are load conditions checked via a different method, or they are never part of a macro?
Okay for some reason today it works just fine without me changing anything. Hurray? I guess?
I wonder if we could add more things to the load conditions, so stuff like skyriding works the way @tharax is saying. We could listen to PLAYER_MOUNT_DISPLAY_CHANGED event and then use C_MountJournal.GetMountInfoByID to get the mount information, which tells us whether we are skyriding or not. Then we could load the skyriding bindings which will override the action bar, and then unload it when we're not skyriding. Or maybe for all edge cases, the loading conditions could be user supplied LUA script?