On classic, I’m experiencing the following bug with this, and all similar macros:
#showtooltip Charge
/cast Charge
/startattack
When logging in fresh, they will show the “?” icon on my bars until I do a /reload, this applies to all macros using #showtooltip, with and without addons enabled.
Strange I’m using showtooltip on my macros and they all show
Edit: try #showtooltip
/cast charge
I’ve had the same problem with all my startattack macros, like you say when logging in sometimes they’ll show the ? icon and will take me messing around redragging them around to fix
It’s a known bug.
Macro tooltips do not load in when you first load into the client.
Same for me
was this an issue specific to vanilla – one of those bugs they’re keeping in on purpose? Or is this a classic issue? I’m still experiencing it, it’s very annoying on my Warrior as a lot of abilities are macroed for stance dancing.
Mine does that every time I log on until I run my mouse over them all. I don’t have to click, but before that they all show as red ?.
Same here. /reload gets rid of the ?
It’s just another bug that blizzard seems to have gone quiet on.
Happens to me, not everytime though. It normally sorts itself when I go into the macro, click around. Glad it’s not just me.
Yes, macroses bugs. I have other macroses without /startattack which bugs as well. Not a big deal, they’ll work after you successfully used it first time, but a little bit annoying.
This is a known issue, listed in the known issue post from blizzard
No need to be toxic about it. It’s a known bug, but it’s not really a big issue. They’ve got bigger issues, like important abilities not working properly. They’ll fix it at some time, don’t worry. Release was obviously rushed, just like any other WoW release.
I don’t think the release was that rushed. A bigger issue is that a lot of the beta test seems to be just abused by streamers who’d rather boost their viewer count rather than do any actual testing, hence why I so often saw them close the bug report box even when a bug was clearly present. Some did their job, though.
I don’t think I was being toxic either – a term which I believe is being tossed around far too casually these days. I simply made an innocuous observation that they’d gone quiet on a lot of issues. Stating a fact isn’t toxic.
There were thousands of testers and only few of them were streamers. Those streams were big, so you couldn’t see all those little people sending bug reports, but they were there. And streamers, well, they are here to entertain people, not to test, obviously. They got their free ticket not because they are good testers after all.
But yeah, it’s a shame that ground breaking bugs were released, like bugged demo shout or instance reset via layer switch. I don’t know who to blame.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.