SetRaidTarget macros broken

Guides UI and Macro
1

While questing I like to use /target macros to target and automatically set an icon on what I’ve just targeted.

Ex: /cleartarget [dead][noharm]
/target Tarantula
/cleartarget [dead][noharm]
/stopmacro [dead][noharm]
/run if GetRaidTargetIndex(“target”) ~= 8 then SetRaidTarget(“target”, 8) end

When running these target macros, with no addons enabled, I can no longer set a target marker icon through this macro.
/tm 8 works but it’s not as useful as what I have above. Anyone else having this issue? Is it intended?

3 Likes
2

/run SetRaidTarget(“target”,8)

is now broken for me.

3 Likes
3

think all the atto mark addons, be it curseforge or made from the ingame macro tab are cooked at the moment. i know my one i made to atto mark the tank and healer in keys isnt working and i have to just mark them by hand

not the end of the world, but still a little annoying

3 Likes
4

/tm 8 probably still works

1 Like
5

Yes, it does, but can’t use it conditionally, unfortunately. :frowning:

6

I’m curious if sticking a ! in front of the number makes it only toggle on like it does with spells.
/tm !8

7

I’d love for this functionality to come back. My group used this heavily to coordinate kicks. I just don’t believe that Blizz has pulled back far enough on the number of kicks needed for this to be obsolete.

1 Like
8

Encountered this as well and keep getting errors. Why would they remove this?

2 Likes
9

I don’t understand what is broken about the macro if you just replace the last line with /tm 8?

/cleartarget [dead][noharm]
/tar NAMEHERE
/cleartarget [dead][noharm]
/stopmacro [dead][noharm]
/tm 8

/tar NAMEHERE
/cleartarget [dead][noharm]
/stopmacro [dead][noharm]
/tm 8

/cleartarget [dead][noharm]
/targetenemy
/cleartarget [dead][noharm]
/stopmacro [dead][noharm]
/tm 8

/targetenemy
/cleartarget [dead][noharm]
/stopmacro [dead][noharm]
/tm 8

All of these options effectively do the same thing. Is this not the expected behavior you’re looking for, or am I missing something? Is it an issue that the skull icon will disappear on the target if it gets targeted twice by the macro?

Elven - The ! in front of the 8 stops the marker from appearing. It would make sense to use it here since I use that on Ice Block to stop it from cancelling the aura when spamming the hotkey, but it doesn’t like it. :\

2 Likes
10

Thanks for checking!

11

My previous macro would not turn off the marker I placed if it already had one. With /tm if I lose the target and have to use the macro again, and it targets the enemy that already has a marker, it will be removed.

So yes, the skull icon disappearing now is what I am sad about. It’s not a huge issue, but I guess I’m just sad that the previous code no longer works. If it’s not a big deal because of /tm, then why remove it in the first place is my reasoning.

12

THey require too many kicks still for what they took away. They are ridicoulous. Not everyone wants to be stressed and sweaty all the time for content.

1 Like
13

I think the idea is that addons aren’t supposed to be able to tell everyone what to attack.

1 Like
14

ty very much

15

So it is the SetRaidTarget part of my targeting macro for Poseidus that is giving me this error? I only get that error when Poseidus is targeted via the macro.

Here is the macro I have been using:

/tar Poseidus
/cleartarget [dead]
/stopmacro [noexists]
/script SetRaidTarget("target", 2);
/script PlaySound(888);
/script DEFAULT_CHAT_FRAME:AddMessage("Target found!", 0, 150, 150)

16

Ya, just change it to /tm 2

1 Like
17

Thank you!