This addon lets you write macros up to 1023 characters long, and still have their icons update normally when you drag them to the action bar.
If you're running low on macro slots, it also lets you write character-specific Long Macros, and have them take up an account-wide blizzard macro slot instead, or vice-versa!
---
To open the Long Macros interface, type /longmacro, /LM or simply /L (doesn't matter whether you use upper-case or not).
Edit just as you would with regular macros.
Once you're done, simply drag the Long Macro to your action bars, and the addon will create a matching Blizzard Macro for you.
If you accidentally alter the generated Blizzard Macro's contents, erase all text from its body, and it will be safely generated again.
Enjoy!
---
Note: due to limitations imposed on all addons, it is not possible to drag a long macro to your action bars during combat, and changes made to your Long Macros will only take effect after combat ends.
If for some reason the game decides to bug out and changes all your slotted Long Macro icons to red question marks, dragging one of them to a different action bar slot will fix it. You can then safely return it to the slot it came from.
In reply to emmetotter26467:
In reply to Forge_User_53795792:
In reply to AoR_Derangement:
In reply to emmetotter26467:
Update: Turns out patch 8.0.0 changed what arguments the UNIT_SPELLCAST_SENT, UNIT_SPELLCAST_SUCCEEDED and other such events pass to event handlers, which explains why /castsequence Long Macros weren't updating.
CRITERIA_UPDATE just occurs so insanely often during combat that we couldn't notice the bug until I commented that.
This is now properly fixed in v1.0.15 without CRITERIA_UPDATE costing us precious FPS. :P
Thanks again for helping me narrow down the issue! =)
The issue with the Long Macro UI not opening in 8.01 is easily fixable.
Open the World Of Warcraft\Interface\AddOns\LongMacro folder
Then open UI.lua in Notepad or another text editor
Find Line 304 which currently has this:
self.portraitFrame:SetVertexColor(1, .75, .2, 1);
And comment it out like this:
--user changed to fix UI load issue self.portraitFrame:SetVertexColor(1, .75, .2, 1);
I can't find any other usages or declarations of protraitFrame in the LongMacro code so I'm guessing that it was a field in the standard Blizzard Frame object that was removed or renamed in 8.0.1
The Lua error I saw when I used bugsack/buggrabber when I debugged this was:
LongMacros\UI.lua:304: attempt to index field 'portraitFrame' (a nil value)
(i don't normally use bugsack/buggrabber because they can cause taint all on their own but this time it worked)
As a side note, I could of sworn that this frame was movable before 8.0 but now it has a fixed place on the screen and can't be dragged around. Probably not a bug but just how Blizz changed the different frame types in 8.0.1
In reply to emmetotter26467:
I've uploaded a fix for this, which should bring Long Macros back up to speed, and ready for patch 8.0.0
/lm doesnt work anymore. its needed to change the spell name.
I forgot to copy/paste my long macros to a notepad before the patch this morning. I can't access macros when the addon is out-of-date :(
EDIT: I saw the comment below and I was able to get to my macros :)
P.S. Your long macros work where Macro Toolkit doesn't. Their macros fall apart after 255 characters. It's frustrating to no end.
In reply to DannyTheConsumer:
In reply to Forge_User_53795792:
You addon actually used to do the same thing until the day I messaged you about how it might be hyphens/punctuations in spell names that might be the culprit. Ever since you fixed that, it's been golden. I've tried many times to contact Macro Toolkit about the issue and they've never responded after almost 2 years.
Thank you for the best and most functional macro addon. I appreciate all the hard work you put into it and I hope things go well for you hereafter. Goodbye friend, and good luck.
Hey, do you plan to update this addon to BfA? I've found it just recently after leveling my druid just to discover nothing fits in the macro. So this seems like a nice way out, but I'm cautious to go full out on it yet if it's not clear whether it'll work beyond couple months.
In reply to lone_irbis:
Character-specific LongMacros, meanwhile, can be found here:
This way, you'll never lose your work, no matter what :)
I am having an Argus specific issues:
When I open the UI with /lm I cannot view the character specific macros (the only ones I have).
EDIT: previously described 2nd issue with castsequence unrelated to longmacro.
Looking at what happened with Mactro Toolkit, which is similar addon and was broken by 7.3 but fixed, the problem it had was with the PlaySound api changing. Previously a string const was past like this:
PlaySound("igMainMenuOptionCheckBoxOn")
And now a ID # must be past like this
PlaySound(856)
Updating long macro's UI.lua and UI.xml to fix the PlaySound calls can be done.
PlaySound("igCharacterInfoOpen") replace with PlaySound(839)
PlaySound("igCharacterInfoClose") replace with PlaySound(840)
PlaySound("igMainMenuOptionCheckBoxOn") replace with PlaySound(856)
PlaySound("gsTitleOptionOK") replace with PlaySound(798)
Now you can view character specific and general macros and edit existing macros
But you cannot delete existing macros. That functionality is broken. Nor can you create new macros and then drag that new macro onto an Action bar. That functionality is also broken.
The problem with deleting and creating seems to be unrelated to the PlaySound issue.
Ooh, this helps immensely!
Thank you for pointing out the change in PlaySound's api, and the follow-up report on broken interactions with blizzard macros.
I'll read up on what the changes to those might have been, and see what I can come up with. :)
And I think I have fixed the delete/create issue as well. It was also PlaySound related.
in UI.lua there are 5 StaticPopupDialogs structure defs assigning a string to a "sound" field like this
sound = "igMainMenuOptionCheckBoxOn",
When I changed it to this:
sound = 856,
Delete/Creates now work properly.
Replacing a constant with a number is a short term fix. I think that Blizz expects people to reference a SoundKitConstants.lua field.
Oh, cool. I was worried something had changed in the pick-up-a-macro api.
There's a table of sound name strings to IDs, so it should not be too hard to just do a find-and-replace through all the code. :P
My new pc should arrive either tonight or tomorrow, so a fix should be up as soon as I can have wow installed to test that's enough.Edit: new PC is here! v1.0.13 of LongMacros submitted to Curse.
Eep, maybe something changed in the way blizzard handles character-specific macros work, internally.
Sadly, I won't have a PC capable of running WoW for another week or so, which means I won't be able to do the necessary testing to figure out what changed until then.
If anyone can figure out the cause of this bug in the meantime, I'll do my best to upload a fix. :)
So with patch 7.2, Long Macros doesn't work again. Hi :3 <3 Please help
Heheh, hey there! :3
I've uploaded v1.0.12 of LongMacros, which should work with 7.2 out of the box.
In most cases, when a new patch like this one comes out, nothing actually changes for the vast majority of addons: Wow disables them just to be on the safe side, because some of them could be affected.
If you're like me and can't wait for their authors to patch them up, and then for Curse to notice the changes and approve them, you can always specifically tell the game "yes, I know some of these might be broken, but let me try to play with them anyway", by going into the addons list, and checking "enable out of date addons".