Auto Macro addon

[Djarid]

I have to disagree here,

So long as the addon is working within the bounds allowed by the built-in scripting engine, that is it is not exploiting some flaw, then it will not be considered automation to use the addon.

If blizzard decided it is against the spirit of the TOS then they will say so (at which point watch out) and will take steps to remove the functionality that allowed the addon to be created.

[smurfy]

Hi,

after looking at the code and seaching a bit in the forum i found something like that:

/if UnitHasSpellEffect("target","????") 
/cast ??? 
/end 
/if UnitHasSpellEffect("target","???") 
/cast ??? 
/end 
/if UnitMana("player")<465 
/cast ??? 
/end 
/cast ???? 
/cast ???

but i really not know how the addon realy works. but from the code i think its somehow allows you to skip spezific lines in macros. with that and some custom slash commands it allows you to create if statements in macros.
but blizz changed the addon api to prevent that function. so i guess this is a working? workaround of the blizz restrictions so i guess blizz will fix that sooner or later.

its realy interesting how the author accomplished that. he must somehow modifiy the workflow of a macro because you cant change a macro on the fly in combat (only out of combat) with a addon.

[Ðeceased]

I have to disagree here,

So long as the addon is working within the bounds allowed by the built-in scripting engine, that is it is not exploiting some flaw, then it will not be considered automation to use the addon.

If blizzard decided it is against the spirit of the TOS then they will say so (at which point watch out) and will take steps to remove the functionality that allowed the addon to be created.

what are you disagreeing with? inch: I was mainly arguing generically :P

I did say:

If the addon contains any form of automation, then it is against the ToS

I did mean to have it refer to targeting automation, based on player class/state(ie if he is dying etc) :P altho sometimes my brain thinks to fast for my fingers to respond and I leave stuff out :P

I have to agree if blizz want to put something down in their TOS it should mainly occur through functionality removal (although I wonder if it's always possible :S )

[thet3rminat0r]

so this is in the deep grey area since I dont think it picks a target but it does use functions like those availiable back in 1.x.x to have restrictions on when to cast the spell

[neux]

I have to disagree here,

So long as the addon is working within the bounds allowed by the built-in scripting engine, that is it is not exploiting some flaw, then it will not be considered automation to use the addon.

If blizzard decided it is against the spirit of the TOS then they will say so (at which point watch out) and will take steps to remove the functionality that allowed the addon to be created.

I have to agree with you Djarid, it is an Addon after all, not third party program, Yet, i don't know how it works, or how can it be used.
I myself after seeing once MacroSequence thought it kinda against what Blizz intended, because I can spam all abilities/spells on one button.
like :
/cast Raptor
/cast Wing Clip
/cast Mongose Bite
/cast Concussive Shot
/cast Arcane Shot

with MacroSecquence I can spam all this abilities and it will work like it used to before change, so if I am not in malee, they can't be activated so it will skip to Concussive and if it is on CD it will skip to Arcane. I thought Bliz removed fall-through logic, yet it is reborn in Addon...

yes, indeed it is gray area >.>

[hardc0re]

I used this addon long before tbc.. i think it was complied in some bigg addon collection like insomniax or cosmos back then.. i would doubt its not leagle. since blizzard already sorted most of those macros

[Simulacra]

Hi terminator!

my apologies if you think I was flaming you. I fully understand that you didn't know the full implications of the macro suite and were merely asking for some clarification on it's capabilities, so no blame
or flame to you in anyway. I was merely implying that subjects that touch upon automation have no place in these forums. It's hard enough being a boxer as it is with all the QQing both in WoW and the WoW forums, I simply didn't want any of our antagonists finding ammunition in here. Once I realised what this suite of macros did I was worried. :|

[Djarid]

@Deceased,

I was disagreeing in general also :)

AFAIK if it is accomplished fully within the published functionality of the Blizzard scripting engine then it is legal until Blizzard say otherwise (pending removal of said feature) Look at the old decursive mod Blizz hated it but until they removed the functionality did not penalise people for using it.

[thet3rminat0r]

I completely understand where everyone is coming from and I found this while surfing the interwebs but have come to the same conclusion as most here... This addon is probable cause for suspension/ban even though it is a good idea. I am sry for getting so defensive i have just been having problems on my end with RL sry to bring it onto the forums..

P.S there is no way that I would ever conceive of hurtin multboxing as a friend and I are working on a 5x2 shammy team for AV and gankage.. one of the best flames ever goes to my buddy who was called an "ascian" the other day.. and yes it was spelled like that. You know the 12 year old is sitting there pounding on his keyboard in frustration cause those "illegitimate multiboxers are using HAXXORS"

[Occam's Razor]

Just googled Automacro and found it on a WOW Exploit site.

One explanation of how it can be used (Without the code, to keep people out of trouble) is a one button Druid heal..... as follows

This macro essentially turns Druid healing into one button.

It checks if Rejuv is on the target, if not it casts it, checks for Abolish Poison,

if not it casts it, if their life is below 75% it will pop Swiftmend,

and it then checks if you have 3x stacks of Lifebloom. All with one macro.
Things like this used to be possible, but was nerfed by Blizzard for whatever reason.

Thanks to AutoMacro you can do it again.

So, this is DEFINETLY illegal