Macaroon is a macro-based "action bar" addon. Up until Macaroon, even considering Trinity Bars, all bar addons were action ID based (at least "out-of-the-box" they were). Macaroon aims to expand beyond the limitations of the action ID system through maximum use of the macro-based button which was introduced in WoW 2.x.

Macaroon is designed to be many things to many users. It can stand on its own as a full-fledged bar addon. Or it can even run side-by-side with other bar addons. It can be an addon for keybinders or even clickers. The whole of the addon is designed to be as feature rich as a user may need, without needing to "fuss" with options one does not care about.

Macaroon is centered around the WoW macro. However, you do not need to know how to write a single WoW macro to use Macaroon! All buttons accept drag-n-drop spells from your spellbook and "feel/function" much like any other button in the default UI or other action bar addons. But if you do decided to expand into the world of macros, be prepared, for you are about to "Feel the power of the macro side..."

• Macaroon offers an unlimited number of macros and an unlimited number of bars of arbitrary length. Create as many bars/buttons as you want/need per character with as many buttons per bar as you want. If you are a major button clicker, you can have at it.

• Players who are considered "Key Binders", people who's style of play is to have minimal buttons (or none at all) on the screen, using hidden key bound buttons to play, can find Macaroon extremely "Key Binder" friendly with the button storage area. The button storage area merges some key features that "Key Binders" should enjoy -

Consolidated area for all buttons, up to 144 buttons (visible).

Edit your macros directly on the buttons in the storage area.

Edit your key binds directly on the buttons in the storage area.

• In-game macros are limited to 255 character in length. This is a limit of Blizzard's macro interface, not of macros themselves. The Blizzard internal macro system can actually handle macros of up to 1024 characters in length, and Macaroon makes full use of that fact on each and every macro

• Uses Maul's unique mouseover key-binding system - where the mouseover binding system was born!

• Many other of the favorite desired bar addon features and then some. You can scale, pad, "sticky" bars together and much more.

Macaroon is distributed as two addons, Macaroon and MacaroonProfiles. MacaroonProfiles is only needed is you decide to save profiles of Macaroon setups. MacaroonProfiles does not even load unless you go to the Profiles configuration menu or load a profile.

Once downloaded, simply unzip the file into your Interface\AddOns folder so that you see both addons in the file structure as

Interface\AddOns\Macaroon

Interface\AddOns\MacaroonProfiles

Make sure that you are fully exited out of WoW when you install new addons.

When you enter WoW after an initial install of Macaroon, you will not see any major difference on your screen save for a newly added minimap button on your minimap. Macaroon starts you off with a clean slate, letting you, the user, decide what you want out of Macaroon instead of me, Maul, deciding for you what you should have and where.

To configure Macaroon, there are two ways to go about it. Via slash commands and the path of command lines or via the minimap button and the path of GUI. Please note that I endeavor to have as many configuration options doable via slash command or GUI, but may overlook some in my zeal to work on addons!

The Path of Command Lines -

There are two primary slash commands that Macaroon recognizes, "/macaroon" and "/mac". The syntax of the commands is as follows -

/macaroon <command> [<options>]

The current command set is -

menu: Toggle the main menustorage: Open the button storage areacreate: Create a blank bardelete: Delete the currently selected barconfig: Toggle configuration mode for all barsadd: Adds buttons to the currently selected bar (add or add #)remove: Removes buttons from the currently selected bar (remove or remove #)edit: Toggle edit mode for all buttonsbind: Toggle binding mode for all buttonsscale: Scale a bar to the desired size.snapto: Toggle SnapTo for current barautohide: Toggle AutoHide for current barshape: Change current bar's shapename: Change current bar's namestrata: Change current bar's frame strataalpha: Change current bar's alpha (transparency)alphaup: Set current bar's conditions to 'alpha up'arcstart: Set current bar's starting arc location (in degrees)arclen: Set current bar's arc length (in degrees)columns: Set the number of columns for the current barpadh: Set current bar's horizontal paddingpadv: Set current bar's vertical paddingpadhv: Adjust both horizontal and vertical padding of the current bar incrementallyshowgrid: Toggle the current bar's showgrid flagx: Change current bar's horizontal axis positiony: Change current bar's vertical axis positionstate: Toggle states for the current bar (/mac state <state>). Type /mac statelist for valid statesstatelist: Print a list of valid statesload: Load a profilelock: Lock buttons

Examples -

/mac menu - this will bring up the main options menu

/mac create bar - this will create a standard bar

The Path of GUI -

The Minimap Button - This button is the gateway to several options via a click and/or modified click.

After you enter the bar configuration mode, all bars become visible. When you mouseover a bar, you will see a tooltip (by default) detailing how most options are currently set for that particular bar. All deselected bars will be a very light gray color. When you select a bar for editing, it will turn blue.

While a bar is selected, it will respond to clicks and modified clicks. These clicks will do different tasks

Left Click: If a bar has more than one state, left clicking on a bar will manually cycle through all available states. A state is a certain condition in which to show buttons, such as bar pages or stances/form.

Right Click: This will bring up a bar editor. The bar editor is the gateway to many configurable options for a bar. Initially, on the left side of the editor is a list of options that can have a varied range of values. On the right side of the editor is a list of on/off options. At the bottom of the editor are next/prev buttons that will take you to an additional set of options that are text-based.

Left-hand options -

Scale: Scale a bar to the desired sizeShape: Change current bar's shapeColumns: Set the number of columns for the current barStrata: Change current bar's frame strataAlpha: Change current bar's alpha (transparency)AlphaUp: Set current bar's conditions to 'alpha up'Arc Start: Set current bar's starting arc location (in degrees)Arc Length: Set current bar's arc length (in degrees)Arc Preset: Chose from preset arc settingsPad Horz: Set current bar's horizontal paddingPad Vert: Set current bar's vertical paddingPad Horz+Vert: Adjust both horizontal and vertical padding of the current bar incrementallyButton Count: Add/Remove buttons to the currently selected bar

Right-hand options -

Paged Bar: Toggles bar paging, allowing for up to 6 unique pages.Stance: Toggles stance paging for classes that have stances/forms.Prowl: Toggles a special stance state for druid prowling.Pet: Toggles pet paging based on pet's existence.Stealth: Toggles paging based on any stealth condition except for druid prowl.Reaction: Toggles a bar switching states based on current target's hostile/friendly reaction.Combat: Toggles a bar that will switch states based on combat status.Group: Toggles a bar that will switch states based on group status.Possess: Toggles a state to show special buttons when possessing another creature.Vehicle: Toggles a state to show special buttons when using a vehicle.Alt Key: Toggles a state to show when the alt key is held down.Ctrl Key: Toggles a state to show when the ctrl key is held down.Shift Key: Toggles a state to show when the shift key is held down.Custom: Allows for defining custom states using the macro system conditionals.Autohide: Toggle AutoHide for current barShowgrid: Toggle the current bar's showgrid flagSnapTo: Toggle SnapTo for current barHidden: Toggle a bar as always hidden while not in configuration mode.Dual Spec: Toggle a bar to allow it's buttons to update data based on current spec.

Text-based options -

Bar Name: Assign a unique name to a bar.Bar Target: Set a bar's target so that it will show/hide based on that unit's existence.

Linked To: Link a bar to another bar. The linked bar will obey the state conditions of the bar it is linked to.State: Determine a specific state to link a bar to.

Bar State: Select a bar state to remap.Remap To: Determine which state to remap the above state to.

Custom States: Allows the entry of custom bar state conditionals using the in-game macro syntax. Place a new state condition on a new line. For example -

After you enter button edit mode, all visible buttons will display their button type. There are three possible button types -

Macro: A button that utilizes the in-game macro sytax to cast spells/perform actions.

Action: A button that uses a unique action ID to indicate what spell/action it contains. The contents of an action ID are stored server-side. There are only 120 (1-120) unique ID's for character spells. A special case are possess buttons which can use the action ID's 121-132.

Pet: A button that uses a unique pet action ID to inidacte which pet spell/action it containts. The contents of a pet action ID are stored server-side. There are only 10 (1-10) unique ID's for pet spells.

To change a button's button type, simply left click the button. As you left click, it will cycle through all button types.

Each button type has its own specific button editor. To enable the editor for a button, right click on the button and the appropriate button editor will be displayed. As with the bar editor, there are next/prev buttons at the bottom of the editor. These are additional button options that are not tied to the button's particular type.

The Macro Button Editor -

Macro Icon: Allows the selection of a unique icon for the macro. Using the ? icon will use the spell's default icon.

Macro Name: Allows for the naming of a macro, but is not needed for a macro to function.

Macro Master: The macro master stores unique user-created macros per account. All characters on an account can pull macros from the macro master.

Macro Edit Area: The area to edit your macros.

Expand: Allows for the ability to expand laterally the macro edit area for easier reading of longer macros.

Macro Note: Allows for the adding of a note to a macro.

Use Note as Tooltip: Allows the note to be used as the button's tooltip.

The Action/Pet Button Editor -

Action ID: Allows the selection of the action ID for a button.

Propagate: Clicking on this option will set the action ID's in sequential order for the entire bar of the current state.

Additional Options Editor -

(Note: The click/Mouse anchors are not functional as I wait for some changes to the Blizzard code to make it possible)

Click Anchor: Sets a button to hide/show a bar's button when it is clicked (even in combat)

Mouse Anchor: Sets a button to hide/show a bar's button when it is moused-over (even in combat)

Anchored Bar: Set the bar to anchor to the current button.Delay: Set the delay to hide a anchored bar for a mouse anchor.

Scale: Set the individual scale of a button.

XOffset: Set the individual x offset in relation to the bar of a button.

YOffset: Set the individual y offset in relation to the bar of a button.

Up Clicks: Set the button to respond to up-clicks.

Down Clicks: Set the button to respond to down-clicks.

Spell Counts: Show the number of times a spell/ability can be used before your character's power is depleated (Rage, Mana, Energy, Runic)

Combo Counts: Show the current number of combo points on a target (druids and rogues only)

Editing Bindings -

/start random fact
At the risk of being immodest and for historical reasons, I shall state here that the mouseover binding method that is so popular now got its start in the early days of Trinity Buttons, for those who don't know The concept first showed up in the early Trinity Buttons days of beta for The Burning Crusade. It was Tuller of Bongos/Dominos fame that refined the system and made it popular in his bar addons. Just some FYI /end random fact

After you enter binding mode, all visible bind-able buttons will display either "bind", meaning that button can have its bindings adjusted, or "locked", meaning that whatever bindings that buttons has cannot be changed until it is unlocked.

While in binding mode, simply mouse-over the button you would like to assign a bind to, and hit the key. You may give a button any number of binds you want. The first bind is the one that will display on the button.

Once a binding is set for a button, you have the option to lock that button's binding so they cannot be changed by left clicking the button. If you dabble in the more advanced features of Macaroon, the need to lock bindings will become more apparent.

The Main Menu -

The main menu is for options that are not bar/button specific. Some may affect bars/buttons, others may not. The following explains what each option does.

The Storage Area -

The storage area serves two purposes. The primary purpose is to be a place where button frames go when not in use by any bar. Frames, once created, cannot be destroyed. Also, as one sets up their bars, they may go back and forth adding and removing buttons. The storage area is just a holding area for those buttons.

However, the storage area can be useful for holding buttons that you want to use, but not have shown. Each row of buttons in the storage area has a lock toggle. This toggle is designed to prevent buttons on that row from becoming part of the "pool" of buttons that bars pull from and add to as bars are adjusted.

For the users convenience in regards to this secondary purpose, some options are provided at the bottom -

Binding Mode: To toggle binding mode.

Edit Mode: To toggle button edit mode.

Create Button: Create a new button that is placed into storage immediately.

Delete Button: To delete unused/unwanted buttons. Note, buttons are not really deleted until you re-log or reload your UI. Until such time, they are merely flagged for deletion. You cannot un flag a specific button once deleted.

The Profile Manager -

(Note: currently profiles are not directly shared between characters as they are in other addons. This is a feature that is in the works)

These options are for setting up and storing specific profiles for use by any character on the current account. These are "dumb" profiles. That means, once you load one, any changes you make on that character are not re-saved to the profile unless you specifically re-save it yourself.

Button Layout: This option saves how many buttons are saved on each bar and in which states. Specific button data is not saved with this option.

Settings: This option saves your main menu settings.

Button Data: This option saves the actual button data such as spells, button scale and keybindings for the button. Right now, keybindings are integrated into the button's data and is problematic to have them saved separately. This is a known issue that is being worked on.

For each profile, you can name it (in fact you must give it a name for it to save) and you can add notes to remind you what the profile is for. In the profile list, you can see all data needed to understand what a profile contains.

At the bottom of the profile manager is the new dual spec feature being added in patch 3.1. Enabling this feature will allow the current character to swap full profiles upon a spec change.

Note: This feature is optional. If you do not need to change bar layouts, button counts or global settings upon a dual spec swap, Macaroon will natively handle the button data swapping without this option being set. Just make sure you have dual specs enabled in the main menu.

Macaroon is a complex addon, with many features. It can use a larger amount of memory compared to other similar addons. However, one thing to understand is that memory usage in an addon has no direct impact on game performance. What impacts game performance is CPU usage.

The WoW client itself uses magnitudes more memory than the most memory intensive addons. If your computer can handle running WoW well, added memory usage by addons will not affect its performance. If your computer struggles to run WoW even at minimum settings, then addons are merely a straw on the proverbial camel's back.

CPU usage is another story. Addons do use CPU time, and the more they do, the more time they use. Macaroon, because of its nature, tends to use more CPU time than other addons of a similar nature. However, I am very, very focused on insuring CPU usage is within reason. If you ever experience an FPS drop and deem it to be related to Macaroon, please give me information on the FPS drop so that I may improve Macaroon!

So remember, in the majority of cases, especially if your computer already runs WoW well (set at average or above average settings) without addons, and you experience FPS issues, your addons are using more CPU time than your computer can keep a decent frame rate at. It is not a memory issue

The following is a post I made on WoWInterface in answering the "whys" of discontinuing "Trinity Bars" and making "Macaroon". By this time, the "shock" should have subsided, but I post it here for the curious

First, I need to make an addon that was easier to maintain. The direction I was going with the whole TrinityUI thing was taking that in the wrong direction. I was making things too complex for myself where I almost got to the point that I had to document for myself my own "API".

Second, two things made me delve deeper into the world of macros - playing my mage to 70 and multi-boxing. Prior to that, I was not a heavy macro user. However, while going through the above, I found myself using the macro side of Trinity more and more and began to feel how "clunky" it felt to keep macros up-to-date. So I decided to make a macro-only bar addon - Macaroon.

Third, there are already action bar addon choices out there. I saw a hole for a macro addon. People want more of them. They want longer macros. They want an easier way to manage them. True, there are some macro solutions out there, but there was yet to be a "macro-bar" addon. So I decided to make the first truly macro-focused bar addon. So I started throwing it together, basically starting fresh where I knew I had issues in Trinity (I call them coding knots), but re-using Trinity's code where it was proven to be rock-solid. Macaroon, to me, has proven to be a much more enjoyable addon to code and maintain than Trinity, so I started to see what I could add to it. And I have not stopped adding yet. To date, Macaroon is almost as functional as Trinity. Only a few key features are missing, but I plan to add them as well (like anchor buttons).

I intended to update Trinity, but as I developed Macaroon more, it became obvious to me that the differences to the end user were small. To me, maintaining such addons as an author, the differences were huge. And I was getting plenty of positive feedback from Trinity users, such as being much easier to configure.

Fourth, I decided this time around to get all those extra items put into a totally separate addon, Macaroon Xtras. Those bars had been the most irritating for me to deal with in Trinity, mostly because of mistakes I made in how I set up handling them. But it was not easy to undo those mistakes without doing exactly what I did with Macaroon. Re-write with a clearer direction of where to go and remembering lessons learned.

Fifth, WoW 3.0 brings some big changes to action bar addons, almost to the same level as WoW 2.0. At least from an author's perspective. The whole internal mechanisms had to be re-coded from scratch. I was initially using Macaroon as a "test-bed" for learning the new API. However, it soon became apparent to me that really if I were to keep a "Trinity" addon going, all it would be is a Macaroon addon with a Trinity name. I was faced with possibility of maintaining two addons that were virtually identical for the sake of a name.

Why the name change, then? Why not keep "Trinity"? Well, I felt "Trinity" was feeling heavy. I wanted something that sounded more fun and light. I knew it was going to be a macro-bar addon, so I was looking for Mac-somthing. I went over a bunch in my head. And since I happen to *love* macaroons, it was the name that took. I also wanted to back away from the uni-name titles of my addons. It was a neat idea at first, thinking I would release a whole suite of "Trinity" addons (and indeed during WoW 2.0 I had many more "Trinity" addons I had never released), but yet again, the effort to maintain my own libraries across all the addons was becoming some serious work. So, in the end, I wanted to break away from the Trinity name (not because I don't like it, but because I want to be more creative and flexible in my addon making endeavors) and not lock myself down to a mono-theme name.

So, here we have Macaroon. It is, for all intents and purposes, really Trinity Bars 3.0, but with a new name and a new coding structure that will make it easier for me. So far during the public testing phase of Macaroon, issues have been minimal. And I don't get daily messages of "well, this is broken now, but thanks for fixing this!" which kinda stressed me out, to be honest. I needed to break away from where it was all going or I was just going to throw in the towel and stop publicly making a bar addon. I make addons for enjoyment, and Trinity was not heading in that direction.

Macaroon has been a new invigoration in terms of coding. Everything is falling into place and tough issues I had in Trinity are just being naturally solved via the new coding. The key to this all is that I am aiming to get to a point where I can release a version of Macaroon and it will stay stable for many months until Blizzard API changes affect it, not because I am constantly trying to undo tightly-tied coding knots I made in Trinity's code.

Macaroon is a new breed of bar addon, as well: a macro-bar addon. "Feel the power of macros" is a good catch phrase for it. Trinity was a highly involved action-bar addon that happen to do macros as well. My bar addon focus has shifted, and Macaroon reflects that in both design and name.

I can only hope that most Trinity users will like Macaroon as much as Trinity. The spirit and soul of Trinity is indeed in Macaroon. And I also hope that those who enjoyed the Trinity journey will join me on the Macaroon journey, as it is already going places Trinity has not.

Hello, just installed Macaroon to replace Bartender4, looks great so far.

One thing I'd like to know is how you can adjust the number of pages for a specific bar, i.e. I got my main Bar (Bar1) paged with 6 pages (by default) but only need 3 pages (scrolling pages with mousewheel)

Bartender had a box to set up custom paging rules, is there any similar option in Macaroon?
I know I could just copy buttons from page1->page4, 2->5, 3->6 but that seems rather crude, I guess there's a simpler solution to this problem?

I'm brand new to Macaroon, but am a HEAVY macro and key binding user.. However, I cannot for the life of me figure out how to GET STARTED using Macaroon... I can pull up the menus and such, but i guess i don't understand the relationship between the standard WoW action bars and exactly what Macaroon does? Mostly I want to be able to use lots of key bindings without a ton of buttons on the screen. Can you please help? Thanks!

I open up the WoWarcraft Macro interface ( /macro ) and +DRAG+ a custom Macro, we'll say its name is FindTarget (with a pre-selected image of a bullseye from the selection of icons offered) I have created from that interface directly onto:

BAR 1: (Action id:1) button 1

... what happens at this point is that this very same "FindTarget" Macro (with its 'Bullseye' icon) instantly appears on the following BARS' locations:

BAR 2: (Action id:1) button 1
BAR 3: (Action id:1) button 1

Also note that the "(Macro)" button type specification has also instantly changed on the very first Bar/button where I directly placed my custom "FindTarget" Macro to "(Action id:1)".

Note that I can only see the button type specification if I am in ''Button Edit'' mode. From here, I can left-click on the affected button(s) and toggle them in between any of these three button ''types''. If I switch it back to "(Macro)", my custom Macro (+icon, obviously?) disappears from view. I am then able to +drag+ some other =usable= Macro, or game item, to the Macaroon button bar.

For some reason, this unexpected behaviour is *NOT* 100% consistent. Sometimes I can +drag+ a quest item (that has a "Use" function) onto one of my Macaroon bar buttons and it does not affect any other buttons anywhere. Other times, it does not matter what I try, I cannot get Macaroon to cooperate with how I expect/anticipate to be able to utilize even a basic Macro button replacement interface.

I will not even delve into how it completely replaces the contents of my default WoWarcraft Macro bars' (1-6) buttons (1-9,0, -, =). Apparently I overlooked this in the provided(?) documentation somewhere?! So if I have to, for some ghastly reason, say a GUI -glitch-, have to disable Macaroon from the character choice screen or even on-the-fly, I do not even have my original action bar set-up available to me. I have to reconfigure it from scratch, afterwards. (Then, if I later go back to using Macaroon, there goes my default macro bars again! No... I will not pollute this topic with that mess... one thing at a time.

I'm brand new to Macaroon, but am a HEAVY macro and key binding user.. However, I cannot for the life of me figure out how to GET STARTED using Macaroon... I can pull up the menus and such, but i guess i don't understand the relationship between the standard WoW action bars and exactly what Macaroon does? Mostly I want to be able to use lots of key bindings without a ton of buttons on the screen. Can you please help? Thanks!

Aranission

Macaroon starts out as a clean slate. You will need to create your bars then add buttons to the bars.

I open up the WoWarcraft Macro interface ( /macro ) and +DRAG+ a custom Macro, we'll say its name is FindTarget (with a pre-selected image of a bullseye from the selection of icons offered) I have created from that interface directly onto:

BAR 1: (Action id:1) button 1

... what happens at this point is that this very same "FindTarget" Macro (with its 'Bullseye' icon) instantly appears on the following BARS' locations:

BAR 2: (Action id:1) button 1
BAR 3: (Action id:1) button 1

Also note that the "(Macro)" button type specification has also instantly changed on the very first Bar/button where I directly placed my custom "FindTarget" Macro to "(Action id:1)".

Note that I can only see the button type specification if I am in ''Button Edit'' mode. From here, I can left-click on the affected button(s) and toggle them in between any of these three button ''types''. If I switch it back to "(Macro)", my custom Macro (+icon, obviously?) disappears from view. I am then able to +drag+ some other =usable= Macro, or game item, to the Macaroon button bar.

For some reason, this unexpected behaviour is *NOT* 100% consistent. Sometimes I can +drag+ a quest item (that has a "Use" function) onto one of my Macaroon bar buttons and it does not affect any other buttons anywhere. Other times, it does not matter what I try, I cannot get Macaroon to cooperate with how I expect/anticipate to be able to utilize even a basic Macro button replacement interface.

I will not even delve into how it completely replaces the contents of my default WoWarcraft Macro bars' (1-6) buttons (1-9,0, -, =). Apparently I overlooked this in the provided(?) documentation somewhere?! So if I have to, for some ghastly reason, say a GUI -glitch-, have to disable Macaroon from the character choice screen or even on-the-fly, I do not even have my original action bar set-up available to me. I have to reconfigure it from scratch, afterwards. (Then, if I later go back to using Macaroon, there goes my default macro bars again! No... I will not pollute this topic with that mess... one thing at a time.

When making macros with Macaroon, it is best to make them with the Macaroon macro editor. While in button edit mode, right click the button.

The primary reason why dragging a Blizzard macro to a Macaroon button switches it to a button of "type" action is that in the past most people who write Blizzard macros but also use Macaroon want changes made in the Blizzard macro editor to reflect on buttons. When a Macaroon button is set to "macro" there is no direct link to Blizzard macros after-the-fact.

And since when an button using an action ID saves its contents server-side, they will reflect those changes on any button (Macaroon or not) using the same action ID's.

I may work on a scheme where a Macaroon macro button can be "linked" to a Blizzard macro, but that is a bit down the line

Currently the best way to go about it without messing with action ID's is to copy-paste Blizzard macros into the Macaroon macro editor.

I am trying to create macro's which will be utilized for multiboxing in a focusless leaderless targetless system while maintaining functionality of the posess and vehicle bars.

My ultimate goal is to create bars that work off each other to enable me...

With no keybindings a single button:
/target [mod:]Player1;[mod2:]Player2;[mod3:]Player3 (etc)

Multiple buttons with no keybindings:
/cast spell

A vehicle bar with no keybindings:
vehicle buttons (ActionID 121-130?)

And finally the glue that pulls this all together (I hope)... two bars, one with:
Normal mode with keybindings:
/click MacaroonButtonID (this is the target macro above)
/click MacaroonButtonID (this is the casting button referenced above)

So... my question is - is there a better way to address this or am I just hitting the ceiling of what Blizzard wants us to be able to do? The end goal of course is that hotkeys 1-= work for my spells when I'm casting and for my vehicle when I'm posessing... the reason I use two bars (one vehicle, one normal) is so I can still use my non-possess bar in vehicle fights if necessary (some quests, the discs in EOE, etc).

I am trying to create macro's which will be utilized for multiboxing in a focusless leaderless targetless system while maintaining functionality of the posess and vehicle bars.

My ultimate goal is to create bars that work off each other to enable me...

With no keybindings a single button:
/target [mod:]Player1;[mod2:]Player2;[mod3:]Player3 (etc)

Multiple buttons with no keybindings:
/cast spell

A vehicle bar with no keybindings:
vehicle buttons (ActionID 121-130?)

And finally the glue that pulls this all together (I hope)... two bars, one with:
Normal mode with keybindings:
/click MacaroonButtonID (this is the target macro above)
/click MacaroonButtonID (this is the casting button referenced above)

So... my question is - is there a better way to address this or am I just hitting the ceiling of what Blizzard wants us to be able to do? The end goal of course is that hotkeys 1-= work for my spells when I'm casting and for my vehicle when I'm posessing... the reason I use two bars (one vehicle, one normal) is so I can still use my non-possess bar in vehicle fights if necessary (some quests, the discs in EOE, etc).

It would be the means I would go at it myself at first. I do multibox, but I have not tried to do any complicated vehicle stuff yet. You may want to ask at dual-boxing.com, many experienced mb's there

It would be the means I would go at it myself at first. I do multibox, but I have not tried to do any complicated vehicle stuff yet. You may want to ask at dual-boxing.com, many experienced mb's there

Yea, the problem with being on the bleeding edge of things is that no one writes guides for you ... as the author of two highly detailed how-to's at dual-boxing.com I'm fairly confident that no one there's going to be able to answer this particular concept until I set it up to prove it works or doesn't.

[indent]This area discusses some of the more advanced possibilities of Macaroon.

This looks great but it's really difficult to imagine Blizzard turning a blind eye to things like in<>. My understanding is they've refused to put a similar mechanism in the default macro processor because of the chaining it allows.

This looks great but it's really difficult to imagine Blizzard turning a blind eye to things like in<>. My understanding is they've refused to put a similar mechanism in the default macro processor because of the chaining it allows.

You are very uninformed sir. There is absolutely nothing wrong with this functionality... of course, you would need to read further to see the important part...

Originally Posted by Maul

This command allows for the execution of an unsecure chat line after a specified event for a given spell

See, UNSECURE being the key part of this feature. UNSECURE means you can do lots of things that blizzard has no problems having timed or automated or chained or anything. Secure actions are things like targeting, casting spells, movement, etc... none of that can be done.

This looks great but it's really difficult to imagine Blizzard turning a blind eye to things like in<>. My understanding is they've refused to put a similar mechanism in the default macro processor because of the chaining it allows.

Zanthor is correct. Commands like "/cast" or "/target" are secure, and cannot be used. Other commands like "/say" and "/emote" are not secure, so they can be executed in this manner.

I would not code anything nor release any code if I felt it was not okay by Blizzard