Broken macro targets in 3.0?

[magwo]

Hello,

I logged in today to discover that most of my macros are broken.

Basically they work like this:
/cast [target=Boohm-target, harm, nodead] [...] Lightning Bolt



Which no longer seems to work. Did Blizzard just stealth nerf this, or has there been a syntax change?

[Maxion]

I don't understand how your "Boohm-target" is supposed to work or ever have worked before, targettarget and focustarget, and i guess party1target and the like are the only such ones working as far as i know.
Name-target... never heard of that before.

[Tynk]

nametarget does work, I believe the - is what is causing the issue.
any unit descriptor will work in conjunction with target, a players name is just another unit discriptor

[magwo]

Yep it did work before, but not in 3.0. Am I the only one with a problem with this?

[Tasty]

I have the same problem, asked in the ui/macros forums on the wow site and got zip. Ended up switching to focustarget temporarily cause I wanted to PVP damnit

[magwo]

This is such an obscure target usage, I doubt very few but multiboxers will ever encounter this problem.
I hope it gets fixed, or that we discover the new syntax if it has indeed changed.

[Sethra]

I had the same problem. For now I have just switched to:

/cast [target=party1target] Lightning Bolt

Adjusting as appropriate... my party is always in the same order.

Not what I'd prefer to do but it works for now, and doesn't take away my focus, or my real target, which was the reason I did it the way you did in the first place.

[Ateleiotos]

I decided to start using Name-target as well after 3.0 but haven't had a chance to try it yet. Silly question, but have you tried it without "-"? (I'd test it but I'm at work)

[Fortis]

I wanted to try targetless/focusless/leaderless setup yesterday, now I know why it didnt work. I hope they fix this soon....

[Ateleiotos]

Anyone figure this out or find an answer? I've had no luck playing with the syntax, nor have I gotten an answer to the question I posted to the WoW UI forum.

[Vainte]

Woot, First Post!

Anyway, I'm also hoping this is a bug and gets fixed. This will be a major pain if blizzard removed this functionality.

Here is the best I've come up with so far that mimics my old lazy lightning bolt, so far it appears to work. You lose focus to hold onto your target, but I haven't found a good use for focus yet.

#showtooltip Lightning Bolt
/focus target
/clearfocus [target=focus, dead]
/use 13
/use 14
/castrandom ,,,,,,,,,,,,,,,,,,,,Elemental Mastery
/cleartarget
/assist Mozgus
/cast [harm] Lightning Bolt
/assist Ivarella
/cast [harm] Lightning Bolt
/assist Wylad
/cast [harm] Lightning Bolt
/assist Rickert
/cast [harm] Lightning Bolt
/cleartarget
/target focus

[magwo]

Entirely unacceptable for arena play to use focus for main assist - you need focus for other purposes. Sometimes I wish they would give us two focuses, one friendly and one enemy.

[aboron]

for my focusless/leaderless setup i wanted to use this for "current toon target" macro:


/target [nomod]playertarget;[mod:ctrl,mod:alt,nomod:shift]toon2target;[mod:alt,mod:shift,nomod:ctrl]toon3target;[mod:ctrl,mod:alt,mod:shift]toon4target;[mod:ctrl,nomod:alt,nomod:shift]toon5target

but it wouldn't work so i ended up converting it to this:


/target [nomod]playertarget;[mod:ctrl,mod:alt,nomod:shift]toon2;[mod:alt,mod:shift,nomod:ctrl]toon3;[mod:ctrl,mod:alt,mod:shift]toon4;[mod:ctrl,nomod:alt,nomod:shift]toon5
/target [nomod]target; []targettarget

Seems to work just as well (even if insanely redundant on the current leader)

[Littleburst]

Having the same problem here.

Was about to try and use focus, for the unexpected nuke in arena. But now i first have to get my main target fixed.

Thinking about making 4 bars, 1 for each character and keybind the barswitches to the '/follow toon2 /focus toon 2' button
So i can just use /assist toon2 /cast LB.

Still hoping it's a bug though.

[TheXevs]

Kinda sucks they broke this...use focus macros for seconday holds and nukes on my setup and like the slaves to be 'target free' for the surprise factor. I have tried this out in the interim and it seems to do the job pretty well:

/assist main
/cast XYZ
/cleartarget

or

/assist main
/focus targettarget
/cleartarget

+

/cast [target=focus] XYZ

party1-5 would be fine except for battlegrounds - if you are set up like this and happen to not get leader or get an uncooperative player as leader, you're kinda boned.

-Xeva

[Hachoo]

Entirely unacceptable for arena play to use focus for main assist - you need focus for other purposes. Sometimes I wish they would give us two focuses, one friendly and one enemy.focus and target ARE two different "focuses" you have. It is entirely acceptable to use focus as main assist in PvP. I use focus as my main assist (without using /assist, just target=focustarget), and then I use my REGULAR target as my "focus". Ie: If I want to seduce someone with my lock and keep them seduced, the macro goes:

/assist [noexists][dead] focus
/cast Seduce

Basically this will make my warlocks target my focuses target, and then if I use the macro again, as long as my warlock's target isn't dead, it keeps casting seduce on that same target. Once that target is dead or cleared somehow, my warlock will take my main's new target again and use that one.

I do the same thing for spell lock, etc.

[Drakkun]

Well this explains why I had problems setting this up with the new patch. I thought I was going crazy when I see posts about using toontarget and it wouldn't work for me.

I hope this does get fixed soon. Otherwise, I just have a leaderless setup.

[Souca]

The OP is correct, the behavior has changed with 3.0. I think it is either a bug, or a change in the secure functions based on the following behaviors.

/cast [target=Souca-target] Lightning Bolt
This worked in 2.4.3, but fails silently in 3.0.2. Removing the - or adding single or double quotes does not alter behavior.

/target [target=Souca-target]
This worked 2.4.3. Same behavior as above in 3.0.2

/assist [target=Souca-target]
This works in 3.0.2 but is the same as [target=Souca-targettarget] in function.

The inconsistency in the behaviors leads me to believe that this is a parsing bug. I'll try and come up with some concrete macros to prove this and post them on the official forums. Apologies if I got something wrong as I am doing this from memory at work.

- Souca -

[Ateleiotos]

I was searching the WoW UI forum and found a thread started by Tastyheals for this issue.

http://forums.worldofwarcraft.com/thread.html?topicId=11228563246

I abandoned my own and went ahead and bumped it because I would really like to know if the functionality still exists or if it will be coming back. :S

[Ateleiotos]

Woot! Blue just confirmed that the functionality will be fixed with patch 3.0.3 in Souca's thread:

https://forums.worldofwarcraft.com/thread.html?topicId=11829374441 ('https://forums.worldofwarcraft.com/thread.html?topicId=11829374441')

I've read that 3.0.3 could go live as early as 10/28, but that could be just wishful thinking on my part.