Having a problem when switching specs. I made 1 for vengeance and 1 for havoc. Both work fine. my issue is whatever spec I am not in macro spams a lua storage error.
Example:
BROKEN MACRO VENGENCE was unable to be programmed. This macro will not fire until errors in the macro are corrected.
Interface/AddOns/GSE/API/Storage.lua:515: attempt to index local ‘spellinfo’ (a nil value)
I’ve been getting this bug too. I found you can turn it off by going to sequences, configuration tab, and checking the Disable Sequence checkbox. That should stop the error message. Doesn’t help you develop your macro since you just disabled it. But at least you will not get the message on other characters.
In my research of this is you’ll find this occurs for each Character of the same class, even with different specs. So when you load them they will also gen the Broken Macro error. The funny part is the macro appears to run fine, just you’re throwing these errors.
From what I heard is this pre-patch should have been held back a week or two. So right now Timothy is having to code to a moving target.
Have you got this error? Log into a character and there are other class spells sprinkled amongst your bars. They don’t work, but they are there. So something tells me the Blizzard API might be the root cause.
None of my macros work anymore for any of my characters. I had ST bound to 1 and AOE bound to 2. I’m not able to play the game anymore as it won’t let me attack anything by pressing one of those buttons over and over. I can only auto by clicking a sword on someone. Is anyone able to assist me? I didn’t change anything.
So There is a work around for that. Make a macro name it what your sequence is named and put this in
/targetenemy[noharm][dead]
/click (name of your sequence no parenthesis)
Then put that where you want to use your button kinda like it used to be
sometimes I still have to manually target but my sequences are working that way
Been doing some more testing and the root cause for BROKEN MACRO seems to be using Spell instead of Macro in your GSE Blocks. Are you using Spell in your macro?
I tried disabling the sequence and the error still pops up. everything works the spam is just annoying. Was worried I did something wrong when i made the sequence lol
yep all the blocks have the spell marked then the spell name
So are you saying if I change them all to macro then use /cast “spell name” then the error won’t show?
If you are using spell blocks and using a /click macro on your action bar, this is the price - you will get this message when in a different spec. The spell blocks need to be perfect at all times as Blizzard doesn’t allow the button to be programmed if you don’t know the abilities you are trying to use. You also can’t destroy a button so when you swap specs it’s still there.
The fix is to use macro blocks and keybind as macro blocks are investigated at run time not at design time.
So I tried making the blocks all macro using /cast Eye Beam ect and nothing would fire. So I tried putting them back as spell and making a key bind as bracket and it wouldn’t fire so lost I guess lol. By the way thanks to all trying to help my old brain work through this!
So I got it all to worth using macro blocks and a key bind no more error! woo thanks again all