AV weekend

[lokka's]

Ill be setting up a pre made av at 7:30 PM (EST) on Saturday the 7TH

most of you know about the addon you need but for the people that dont here is the link

http://www.curse.com/addons/wow/preform-av-enabler

contact me on skype (skype name, deedsofflesh2)
or in game I am on US Arathor

[Shodokan]

Faction?

[lokka's]

Faction?

Horde

[Ualaa]

Rath Strat (US Horde)
Join the vent, go to a War Room, send a Real ID request to the leader for the wait list.

Vent:
wow.publicvent.org

Port:
4135

[lokka's]

Rath Strat (US Horde)
Join the vent, go to a War Room, send a Real ID request to the leader for the wait list.

Vent:
wow.publicvent.org

Port:
4135

I'll try for sure but I would be ten boxing it not sure if there would be room

[Ualaa]

17 hours of fun, Fri/Sat.
Won't be on tomorrow, but will be back Sun.

[Fat Tire]

This is not something that we are encouraging, but it is also something that we currently have no realistic way to prevent. That being said, this is something that may change soon, which is why we always advise people to not use any type of add-on designed to circumvent or bend our balancing safeguards... using such add-ons can lead to severe account penalties!

http://eu.battle.net/wow/en/forum/topic/3523403390

[Ualaa]

Blizzard's stance has always been, if you can do it with a macro or addon, its okay.
And in the past they have changed the API, specifically to break functionality in certain addons.

As long as the addon API allows it.
I cannot see anyone having an issue with it.
If they change the API, so this functionality is broken... and you find a way around it, that could lead to repercussions.

That said, its your accounts... so make your own decision.

[zenga]

Blizzard's stance has always been, if you can do it with a macro or addon, its okay.
And in the past they have changed the API, specifically to break functionality in certain addons.

As long as the addon API allows it.
I cannot see anyone having an issue with it.
If they change the API, so this functionality is broken... and you find a way around it, that could lead to repercussions.

That said, its your accounts... so make your own decision.

That is quite a bogus statement. By that logic any flaw/bug in the API can be safely used, because the API allows you to do so. The rules are pretty clear about this. Reality is that blizzard has changed it so that raids can no longer queue up for the non 40 man bg's. They did that for a reason. This addon circumvents that.

You mixed up the odds that you get banned with what is ban-able (or what is against the rules). Only a minor fraction of the people that buy gold get caught, but that doesn't make it 'safe' or 'okay' to buy gold because blizzard penalties only a minority. The same goes for circumventing ingame mechanics.

But yeah, I don't see them throw out a big ban wave for using the addon.

[Ualaa]

That is quite a bogus statement. By that logic any flaw/bug in the API can be safely used, because the API allows you to do so. The rules are pretty clear about this. Reality is that blizzard has changed it so that raids can no longer queue up for the non 40 man bg's. They did that for a reason. This addon circumvents that.

You mixed up the odds that you get banned with what is ban-able (or what is against the rules). Only a minor fraction of the people that buy gold get caught, but that doesn't make it 'safe' or 'okay' to buy gold because blizzard penalties only a minority. The same goes for circumventing ingame mechanics.

But yeah, I don't see them throw out a big ban wave for using the addon.

Going back to the early days of Burning Crusade.

There was an addon called Decursive.
In the form it had, you clicked on a button (which you could also keybind).

Doing so, your toon would scan the raid for a debuff which your class could Cleanse/Remove Curse/Etc.
If there was no debuff present, no mana was wasted.

You didn't have to know which spell to use (Abolish Poison vs Remove Curse, for a Druid).
Just press the button.

We had a lady who played a Paladin on our raids.
She would follow the group, and press a single button (thousands of times, every raid).
She would typically have 1000 decurses more than the next best person, with close to zero damage/healing on the night.

Blizzard had the blue post saying they didn't like how the addon worked.
And were changing their API, specifically what can and cannot be accomplished with an addon.
And that minor patch they did, broke the addon.

Maybe Blizzard's stance has changed.
But as of early Burning Crusade, a blue posted if you can do it entirely with an in-game macro or an addon (nothing external to the game), it is fine to use without repercussion; when we don't like what you can do with an addon, we will change the API to break it.




Many functions of the addon API are protected, so cannot be used in combat.
Many are not.

Jamba gives the ability to "strobe" the /Follow command, once a second indefinitely without any user input beyond enabling the feature.
Evidently /Follow is not a protected function that Blizzard gives a shit about.
But it is absolutely automated use of a function, without user input at the time of the numerous /Follow commands issued by the addon.

But it is part of an addon... which Blizzard has complete control over what can and cannot be done via in-game addons, not a third party software such as the G15's profiler.
Because the addon is doing this, you're not going to get banned for automation.

If Blizzard decided to not allow an addon to initiate /Follow, or to Strobe the /Follow command...
They would change their addon API, so an addon is unable to perform that functionality.

They're unlikely to turn around a ban you.

Exactly the same deal with Preform AV Enabler.
The addon is allowing a functionality.
Something that Blizzard can break, if they want to break.
It is not a third party, out of game, tool that people are using to "bot" with, or "automate" the timing of their queue for this game.
The addon uses Blizzard approved addon API, and nothing else.
Evidently a blue (or several blues/whatever) do not like this addon, which is warning that at some point it might be broken should Blizz decide its worth the time to do so.

As of now, it is expressly allowed because that functionality exists within the addon API; I'm not claiming it is something Blizzard is happy about, nor that it will always work... but it does now.
And as long as you can do it with their Addon API, they're not going to ban you.