WowAce

hi!

this addon is awesome :) but may i suggest an update?

sometimes, when all the adds are piled up on top of each other, it is hard to target a certain target (for example, star).

would it be possible to just right click on the target's bar of magic target to target the mob?

thank you :)

I wonder if it's possible to instantly have the marked target auto targeted. for example in P3 at Anub'Arak when players have 10% health and need to be instantly topped. if you get a mark assigned to you that you can instantly act by clicking on the appropriate mark assigned to you so you can heal fast. is there a similar addon otherwise?

I raided with my guild in Burning Crusade, Which was 2.0 and beyond, and our guild leader had us install RDX to be able to raid.

I specifically recall setting up main tank/assist lists that would show their targets all as bars, yet they WERE clickable.

You could add ANYONE in the raid to these lists, and could add as many ppl as you wanted to the lists, and still be able to click on any target they had.

So, I am not sure why you say: The bars are not clickable. Due to the secure templates added in WoW 2.0, this is no longer possible.

I have even install the new version of RDX, called OpenRDX, and tested out the lists in the most recent version as of patch 3.3, and the bars continue to be clickable target bars.

Could you please explain why you believe you cannot make these bars clickable?

Thanks.

nice, but i'd like to select targets clicking bars instead of looking for symbols when i'm fighting huge groups, and i cant find how to set this option. i have these errors also, hope it can help

1x MagicTargets-2.0.95\MagicTargets.lua:362: attempt to call global 'UnitGroupsRolesAssigned' (a nil value) MagicTargets-2.0.95\MagicTargets.lua:676: in function `UpdateBar' MagicTargets-2.0.95\MagicTargets.lua:467: in function `?' CallbackHandler-1.0-5 (Ace3):145: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:145> <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4> <in C code>: ? <string>:"safecall Dispatcher[1]":13: in function `?' CallbackHandler-1.0-5 (Ace3):92: in function `Fire' AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119> <in C code>: ? <in C code>: in function `CameraOrSelectOrMoveStop' <string>:"CAMERAORSELECTORMOVE":4: in function <[string "CAMERAORSELECTORMOVE"]:1>

-

5x MagicTargets-2.0.95\MagicTargets.lua:362: attempt to call global 'UnitGroupsRolesAssigned' (a nil value) MagicTargets-2.0.95\MagicTargets.lua:676: in function `UpdateBar' MagicTargets-2.0.95\MagicTargets.lua:467: in function `?' CallbackHandler-1.0-5 (Ace3):145: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:145> <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4> <in C code>: ? <string>:"safecall Dispatcher[1]":13: in function `?' CallbackHandler-1.0-5 (Ace3):92: in function `Fire' AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>

-

5x MagicTargets-2.0.95\MagicTargets.lua:362: attempt to call global 'UnitGroupsRolesAssigned' (a nil value) MagicTargets-2.0.95\MagicTargets.lua:676: in function `UpdateBar' MagicTargets-2.0.95\MagicTargets.lua:467: in function `?' CallbackHandler-1.0-5 (Ace3):145: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:145> <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4> <in C code>: ? <string>:"safecall Dispatcher[1]":13: in function `?' CallbackHandler-1.0-5 (Ace3):92: in function `Fire' AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119> <in C code>: in function `TargetNearestEnemy' <string>:"TARGETNEARESTENEMY":1: in function <[string "TARGETNEARESTENEMY"]:1>

-

51x MagicTargets-2.0.95\MagicTargets.lua:362: attempt to call global 'UnitGroupsRolesAssigned' (a nil value) MagicTargets-2.0.95\MagicTargets.lua:676: in function `?' CallbackHandler-1.0-5 (Ace3):145: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:145> <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4> <in C code>: ? <string>:"safecall Dispatcher[1]":13: in function `?' CallbackHandler-1.0-5 (Ace3):92: in function `Fire' AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>

-

694x MagicTargets-2.0.95\MagicTargets.lua:362: attempt to call global 'UnitGroupsRolesAssigned' (a nil value) MagicTargets-2.0.95\MagicTargets.lua:676: in function `UpdateBar' MagicTargets-2.0.95\MagicTargets.lua:737: in function <MagicTargets\MagicTargets.lua:719> (tail call): ?: <in C code>: ? <string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5> (tail call): ?: AceTimer-3.0-5 (Ace3):164: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>

-

Thanks, unfortunately:

1x MagicTargets-2.0.95\MagicTargets.lua:590: attempt to index local 'tti' (a nil value) MagicTargets-2.0.95\MagicTargets.lua:604: in function <MagicTargets\MagicTargets.lua:599>

2x MagicTargets-2.0.95\MagicTargets.lua:362: attempt to call global 'UnitGroupsRolesAssigned' (a nil value) MagicTargets-2.0.95\MagicTargets.lua:676: in function `UpdateBar' MagicTargets-2.0.95\MagicTargets.lua:737: in function <MagicTargets\MagicTargets.lua:719>

Currently I use ora3, Pitbull4, Grid, Aloft

Isn't it possible to determine, who targets a mob or who gets aggro ? That way it should be possible to make the bars clickable (targets target) ?

Been using this for a while, and like it very much. It would be great to have a new tag for the labels that showed threat% for AoE pulls, using UnitDetailedThreatSituation. Health is visually pretty easy, aggro not so much, so a numerical display would be sweet.

is there anyway you can show / hide this addon?
tried all the usual /mgt hide but what im wanting is to hide it when im not raiding like i do with recount omen etc with a macro.

Great addon btw :)

Unrelated to my previous posts (the CC timers are still off), you could use default blizzard tank roles (as opposed to requiring oRA2) by using GetPartyAssignment("maintank") - gets a list of unit IDs), GetPartyAssignment("maintank", unitID) - gets a true/false returned if that unitID is assigned MT, or looping through from i=1 to GetNumRaidMembers() and using 'select(1,GetRaidRosterInfo(i))' - gets you name) and 'select(10,GetRaidRosterInfo(i)') - gets you their role (ie maintank, mainassist).

I had originally just been hard coding our warrior tanks, as tanks, however sometimes one switches to dps. To finally fix this, so I don't have to run oRA anymore, I used the final version described above to edit the mod to make it detect said tanks.

Thanks for all your work on this mod, we use it every day in raids, I'll take a look at your CC calculation code next to figure out wtf is happening there.

It is a great program. I think you'd get fewer requests for clickable buttons if you'd outline how it would fail.

A button can't be set for the unique identifier of a monster, Blizz has made sure of that. You can target based on name, getting whichever is closest, or on identifier, like playertargettarget, raid5target, party3pettargettarget, etc.

A button can be set for a target like raid2target, but once in combat, that designation can't be changed. if bob targeted a rook, we could make a button targeting bobtarget labeled rook, but pressing the button would always target bob's current target, so if he were attacking the knight, pressing the "rook" button would target the knight.

And you can't get around it by relabeling the button "Knight" because you aren't allowed to do that to secure buttons in combat, and only secure buttons can target. You also can't move secure buttons during combat, so you can't make a button for every raidmember's targets, and move the one with the most people hitting it to the top of the stack, or to a different position, or even fading out all of the other buttons. Blizz REALLY wants you to have to think when targeting.

You could make a button to target "Rook" but if there were 2 rooks, either might be targeted, and you can't even use targetnexttarget to jump between the rooks, because it's just as likely to target a pawn or a bishop next.

And if the rook was a type of shaman's totem you couldn't target it by name because they recently prevented it to destroy "Totem stomping macros"

I posted this because I thought, as so many others, that the author hadn't seen the "Obvious" way to make the buttons clickable. And each person with a separate suggestion here had a different method for getting around the problem. I thought mentioning several (hopefully all) of the schemes might reduce the number.

It's a great program, it just can't do what blizzard forbade. I'll make do with the arrow telling me who I'm targeting, and tab-targeting. And seeing if dbm can't open up 14 unitbars for the faction fight, where they're all uniquely named, like it does for the tupple adds for Freya.

If you find a way to make a button to target "the mob with the lowest health" or "the mob with the greatest number attacking it" Blizz will remove it so fast, your head would spin. I had hopes once of a macro/command/addon that would set the focus if the current target had fewer hp, then set the spells to tabtarget wildly, but aim at the focus. Sigh.

I hope you don't find this post presumptuous, and feel free to point out any errors in a derogatory manner.

I almost wanted to just jokingly ask if you could make these bars clickable, as almost every comment you receive is simply that. I've noticed that both my CC abilities, Psychic Horror and Shackle Undead end up with a much longer 'CC time remaining' that the debuff actually shows on the target. I'll end up editing it myself, however you might want to take a peek at your code to see what is causing the timer issue. I'll post again, after I get a chance to use it in raid and see if poly or other standard CC are off as well.

Sorry I meant Psychic Scream (as I'm a priest). I tested your r92 on Wowace as well and it is displays the CC incorrectly as well.

Thanks much, just very odd how it sets fear at 10 sec when the tooltip itself says 8, and shackle is a good 5-7 sec longer than the max CD as well.