Is this macro banable?

so im just checking if this macro is banable, i dont use addons this is in the built in feature of wow. heres a run down of what it does.

a macro that tracks if nearest friendly target has (buff) if target does not have buff cast(spell) , if player has buff it will prioritize the next closes target and cast said spell. this clears dead targets as well. also this will cycle back to any random target if echo is applied to all targets

here is the macro

/script

/cleartarget [dead][nohelp][mod:ctrl]

/targetfriend

/cast [nobuff:echo]

/cast echo

else if

/targetfriend

/cast [buff:echo]

/targetfriend

1 Like

by built in i mean the built in macro system

If you are using the built in system, it isn’t against automation rules (though a macro can get you in trouble for chat reasons, this one won’t do that). If they don’t want you to be able to do something with a macro, the support won’t be in the game.

Couldn’t say if this would work though.

7 Likes

No, that’s fine.

3 Likes

thank you i asked support they told me that they cant say if any macro are legal or not and to read the rules to find out so now im here

Macros can’t test for buffs, and else if isn’t a valid input.

Try the UI and Macro forum.

5 Likes

No macro is ever bannable because they are already limited by the rules of the system.

Unless you’re talking about macros OUTSIDE of WoW, and those certainly are if they automate multiple inputs.

this is all in game

Addons such as Weak Auras can track buffs.

I don’t use macros myself all that much, the only time I did was to make a simple one for Zekvir to auto-target him and cast Silence (did it on my Priest) because trying to tab back to him while fighting the spider was a bit too nerve-racking near the tail end of the fight. But outside of that I haven’t really used macros so I’m far from an expert on it or how TOS works.

But I don’t think this macro is anything bad. I did hear there was an auto-target macro people were using in Classic to get tags on mobs before anyone could realistically click on them via Druids, and some might have had actions made against their accounts, but I’m not sure since its one of those “I heard it from another gal” kind of situation. But this macro for this intent? Don’t see anything wrong with it.

I do agree with the chat part, though. That can get you into trouble depending on the content of the message. One of the reasons my friend stopped using a rez macro in FFXIV.

This part simply won’t work.

It’s not banable if used within the built in system, also this macro won’t even work.

If one press = one spell cast it should be fine (if it even works)

It’s usually game automation or external macros (programmable keyboard) ones that are iffy.

ill explain what this macro does in detail step by step, but this is all built in idk why it works maybe im wrong in what i think the macro does?
script
/cleartarget [dead][nohelp][mod:ctrl] = clears if the person is dead or not
/targetfriend = targest nearest friend npc.
/cast [nobuff:echo] = tracks of player has echo but the simply put does npc have echo.
/cast echo = if the statment is true cast echo.
else if = this is a function sequence meaning run this as well, kinda like a reative function
/targetfriend = target nearest ally
/cast [buff:echo] = if echo buff active
/targetfriend = target next closest ally

(/cleartarget [dead][nohelp][mod:ctrl]

try it out

Cheap auras gets away with arguably far too much already but like others have said, if you can make an ingame macro do a thing, it isn’t against the rules unless it’s a chat spamming addon in which case you risk breaking spam rules.

What you probably want is a cheap aura to give you some kind of UI indicator whatever you are trying to make via a macro.

it 100% works with the ingame macro system

I have never heard of an “else if” command.

Macros are not programs so

is meaningless as a standalone line. There’s nothing for it to do even if it could evaluate that as true, and if a condition is false it simply skips that line. That’s also why ‘else if’ is completely meaningless, it’s going to continue regardless of having that in it.

Also [buff] is not a condition that it understands and you will get an error when the macro is saved saying that it doesn’t understand that part. You cannot check if a buff is present. Macro conditionals are extremely limited on purpose.

1 Like

it is not chat but thank you