Nostalrius Begins - Quality wow vanilla realm (1.12)

And not only if they are exploiting a bug!

Unlike on retail, API automation is not considered ok here. Not that I don't agree that Neutral AH sniping, as in this specific case, is kinda unethical in and of itself, but there are a ton of addons that are at least borderline with these rules. In fact, the letter of the law (even if it would never be enforced so broadly) is that almost any and all addons are against the rules, since what addon doesn't automate some component of the game, however insignificant in scope and degree?

(Link)

Daemon wrote:Hello,

This account has been banned for performing automatic AH actions, which falls under the bot ban reason. This functionnality is no longer accessible from future clients API, because Blizzard considered that it was not legitimate to use it.

Let me quote the terms of use:

B. Bots; including, but not limited to, any code, hardware and/or software that allows the automated control of the Game, or any feature or component thereof.

Regards,
Daemon

Surprised the hell out of me.

Jeniwyn wrote:In fact, the letter of the law is that almost any and all addons are against the rules, since what addon doesn't automate some component of the game, however insignificant in scope and degree? (Link)

I don't think so... 90%+ of addons do nothing of the sort.
Unless you broaden the definition of "automation" on purpose.
Common sense will serve us well in most cases.

This is a hard dilemma for GMs, to remain blizz-like you can't take alot of liberties with the client code.
So you can't solve the problem by breaking the API. If you start doing that where do you stop?
Do you start pushing patches? 1.12.1 > ? To break API that's clearly easy to exploit?

So you slap the wrist and hope the playerbase takes the hint.
There are core game systems: combat, economy, 3D world where most everyone has a feeling what's not ok.

The API isn't easy to exploit at all. I don't see any reason to police it whatsoever. I think the point of where to stop is to not even begin. I think that will only lead to arbitrary decisions. And I don't think permanent bans are "a slap on the wrist".

And no, I realize that any and all things that can be seen as automations (The entire Event API, if you push it) will not be considered bannworthy by the GMs. But the rule is written to throw as wide a net as possible and certainly forbids it even if it will never be enforced. I made a slight edit since I don't really think that is the interesting part and don't want to much discussion on it. If the edit doesn't prove to be enough I'll just edit the sentence you quoted out completely.

LazyPig is probably a good example of a borderline addon though. Lots of nasty, shady automation in there.

This functionnality is no longer accessible from future clients API, because Blizzard considered that it was not legitimate to use it.

Wow, this is ridiculous. Isn't disagreement with what blizzard thought fitting and unfitting for their game in later expansions the whole reason why we're here?

Bit wrote:

This functionnality is no longer accessible from future clients API, because Blizzard considered that it was not legitimate to use it.

Wow, this is ridiculous. Isn't disagreement with what blizzard thought fitting and unfitting for their game in later expansions the whole reason why we're here?

Haha. Indeed.

Also, the list of functions removed from, added to or changed in significant ways in the API since 1.12 is freaking huge. I think this change in policy interpretation is a huge mistake by the GM team. I hope they reverse it. It is hard to be more unblizzlike than this.

I also suggested that they could just allow people to mail cross faction if they now think that the neutral ah addons is a problem. That would be a way, way less intrusive way of handling it.

Bit wrote:

This functionnality is no longer accessible from future clients API, because Blizzard considered that it was not legitimate to use it.

Wow, this is ridiculous. Isn't disagreement with what blizzard thought fitting and unfitting for their game in later expansions the whole reason why we're here?

Tinkertown wrote:
Haha. Indeed.

Also, the list of functions removed from, added to or changed in significant ways in the API since 1.12 is freaking huge. I think this change in policy interpretation is a huge mistake by the GM team. I hope they reverse it. It is hard to be more unblizzlike than this.

I also suggested that they could just allow people to mail cross faction if they now think that the neutral ah addons is a problem. That would be a way, way less intrusive way of handling it.

I believe 99% of the Nostalrius playerbase is disagreeing with Blizzard's later content and class mechanics, and not the changes they made in the API.

I have to say I'm not aware which function(s) the GM talked about but in my opinion the GMs are correct on this matter.
They also banned for abusing the AV group-queue which on retail was also implemented once but even reverted before 1.12 so why not also with functions which could damage the economy.

What was the addon called man???

or what was the macro used?

frozted wrote:What was the addon called man???

or what was the macro used?

some AH sniping stuff that automatically scans the AH and buys out items that were put in for cross faction transferring

I think they call this scripting... hmm not sure though.

not sure if stupid. or a hater

Who cares what exact addon was used. The rule is clearly applied arbitrary, since it has to be, thats the whole reason it is so bad. The only guideline is what addon/macro/script you personally think that any GM might suddenly be in the mood to ban you for at any given day.

The wording in the ToU is fine for 3rd party programs and such since you want sweeping rules for those. The wording suck donkey balls for API scripting.

If someone were to program a .exe that does what LazyPig does, it would certainly be considered a bot. Thus, since acconding to Daemon the rule applies to addons too, LazyPig is a bot. It's just that they won't enforce this rule, in that case, at the moment. Fantastic. What happened to: we apply the Terms of Use ruleset uniformly across all players on Nostalrius Begins. No exceptions, no special cases?

Words fail me in my efforts to describe how much I dislike ingame scripting being bannable without warning if done in a way a GM suddenly decides he doesn't like.