Addon for Raid smoke flares?

[alrit]

It's a lovely function in the new blizzard raid ui.

But after removing original raid frames with no!CRFM or simular addons, I can never find the flag button to use smoke flares.

Is there a way or an addon can bring this flag button back? or make it a more interesting way using smoke flares? ...

[Dridzt]

I started working on something like that but unfortunately the relevant functions are protected.

Still looking at workarounds, I'll post (if no one beats me to it) when I have something that doesn't taint.

[Xinhuan]

The following macro works

/click CompactRaidFrameManagerDisplayFrameLeaderOptionsRaidWorldMarkerButton
/click DropDownList1Button4

Where 4 is a number from 1 to 6. The first 5 corresponds to the 5 colors and the 6th one removes all flares.

Since the macro works as-is (don't try to run it by typing it in the editbox, it won't work), an addon can of course also create an action button with type="macro" for it.

[Dridzt]

Originally Posted by Xinhuan The following macro works /click CompactRaidFrameManagerDisplayFrameLeaderOptionsRaidWorldMarkerButton /click DropDownList1Button4 Where 4 is a number from 1 to 6. The first 5 corresponds to the 5 colors and the 6th one removes all flares. Since the macro works as-is (don't try to run it by typing it in the editbox, it won't work), an addon can of course also create an action button with type="macro" for it.

This also taints.

Run it without opening the compact raid pull out even once (so it 'initializes') after logging on and you will see.
The addon button with macrotext attribute was the first thing I tried couple days ago.

[Vlad]

I wonder why Blizz protects API that can't really be exploited with to begin with. This is one prime example, how can you cheat in the game by having an addon "cast" a flare for you? You would have to click to actually apply it in the world anyway -and that's already protected, so...

Meh, wish they could work as a team sometimes when coding the UI and implementing API. Feels like some decisions are not made as a team, that's all I am saying. Protect the code that you must, have secure templates for stuff like buffs, actionbars, e.g. so addons can't be used for playing the game for you, other than that leave the rest for the modders to use -also don't use local variables like the consolidation table, can't even hooksecure to alter it's function as there is no way of hooking a local variable either... keep stuff global when you don't got the options implemented to customize to begin with.

[SDPhantom]

It's a global thing, performing any "action" is protected.
Also, possible exploits don't have to necessarily be blatant.
Example, if an addon were able to cast flares on a timer script, it would constantly reset the AFK flag in the system. In essence, an AFK bot.