so you're first response to these threads is to call the OP a liar instead of actually giving him leeway in the fact that this might be actually true? God silly people these days
Glad i never used Oqueue if this is true.
So not only did you get banned, but you got perma banned?
You had to be doing something more than botting which is what you are saying they accused you of.
Even if you were straight up botting herbs bg mining etc you still wouldn't get a perma ban.
How is this thread even still open?
My account was on a last warning for botting 2 years prior to this and that time i recieved a 3 day ban and never looked back into botting.
Basically what the gm's been telling me is to go fuck myself because i have been botting once before and because of that "bot" tag from 2 years ago on my account i recieve no second thought on my ban and they don't even bother checking or confirming to me what has caused the ban.
My mail said third party program and i know all i had on was oQueue which keeps me from getting logged out. That is the ONLY thing i can think of that should serve as 3rd party program.
As others have said also this addon doesn't always keep you from getting logged out. Some does get logged out and some don't.
Don't think you have a reason to complain if that prior transgression was the reason you got banned now. Botting isn't a "oops how did this happen" spur-of-the-moment kind of thing, you *willingly chose* to do something illegal for personal gain. They are right in leaving a permanent mark on your record and bringing down the hammer with the next transgression. No tolerance is the only policy, or people will be exploiting left and right.
That being said, as always with borderline addons you should make SURE before you use it whether or not it could constitute a ToS breach. Ask Blizzard, document the conversations, etc. THEN use it. Don't assume, ever; and especially don't go complaining afterwards when you clearly didn't look into the matter beforehand.
If i had been correctly banned for actually botting at that time i wouldn't have started this thread in the first place. But me standing AFK with oQueue addon is not considered botting.
There are literally thousands of people using this addon and blizzard themselves spoke highly about it on Blizzcon this year so how on earth is this a fair ban?
I don't know the details, or Blizzard's stance on it. Maybe it was a mistake. Maybe their opinion has changed. Maybe something else caused the ban entirely. Appealing to Blizzard formally seems to be the logical course of action to find out for sure.
I don't believe it was Oqueue that got you banned. You had multiple tickets open on your account from other players. You get enough complaints you get banned. Maybe you got caught botting before or players said they saw you botting? This has nothing to do with Oqueue. When you write your next ticket asking them to lift your ban ask them how many tickets are open against you. If you have hundreds then I doubt they'll lift your ban, sorry.
Last edited by Barnabas; 2013-11-23 at 07:26 PM.
My Diablo3 account was chat-banned (just chat) for 6 hours due to oQueue sending friend requests. I hadn't played Diablo3 for months. It happened.
I opened two tickets. The GMs eventually investigated and confirmed it was due to oQueue. My account was not hacked.
That said, my understanding is that newer (and current) versions of oQueue no longer send friend requests or spam to other battle.net games, so that shouldn't be a problem now.
Of course oQueue does still send tons of friend requests to people playing WoW, and a lot of those people don't understand how oQueue works. I'm sure you've gotten whispers from random people "why did you add me as a friend", I know I have many times. If any of those people report you, the GMs could arbitrarily decide to take action on your account. I find oQueue essential at this point, so I basically roll the dice.
Greetings,
Account Name: removed
A user of the above account has recently been involved in actions deemed inappropriate for Diablo III by the In-Game Support staff of Blizzard Entertainment.
Account Action: 6 Hour Suspension of Chat Privilegees
Offense: Spamming
This category includes:
* Excessively communicating the same phrase, similar phrases, or pure gibberish.
* Saying the same phrase more than once in a period of 30 seconds.
Based on a review of the information presented, this Diablo III account has had its chat privileges suspended. While the account has been placed under review, you will be unable to speak to other players via any avenue of Diablo III. Should spamming behavior continue, we may proceed to apply further penalties including extended suspension of chat privileges, account suspension, or account closure. Once an account has been closed, any characters, items, or auctions will be irretrievable.
For further information, please review the Diablo III Policies and Terms of Use Agreement: (http://us.battle.net/support/en/arti...o-iii-policies) and (http://us.blizzard.com/en-us/company/legal/d3_tou.html).
We understand that these policies may seem harsh, but they are in place to ensure that every player is able to enjoy their time spent on Battle.net. Thank you for respecting our position.
Regards,
Blizzard Entertainment
Diablo III Customer Support
http://battle.net/supportThis is the latest response from Customer Support:
Hey there, nameremoved,
Thanks for your followup contact about this action that was taken against your D3 account.
While we're unable to provide a lot of detail about the action, it was found that a large number of friend requests sent out by this account were reported as spam by the recipients, which resulted in the penalty having been applied.
If you have any addons that send out friend adds/requests, I would strongly advise you to disable them, as a large portion of the community receiving these has decided they do not wish to receive them. We do not have evidence that unauthorized access was made to the account, and as a result, we can confirm that the account was not hacked.
We understand that you may still have concerns regarding the action, but we must reiterate that it was taken to address a violation of the Terms of Use and End User License Agreement (http://us.blizzard.com/en-us/company/legal/), which all players accept before logging into the game.
We understand that these policies may seem harsh, but they are in place to ensure that every player is able to enjoy their time in our games. Thank you for respecting our position.
Last edited by Schizoide; 2013-11-23 at 11:57 PM.
What happened to the ops made up screenshot?
Interesting, I did wonder if the addon might cause such a reaction, just based on the fact it can be spammy, and reading issues others had with it, I never downloaded it.
Sorry about your account OP, but thanks for sharing, you might save many others from a similar fate!
If the traditional raiding format was more accessible, was less hostile towards those inconvenienced with a real life then maybe neither would be needed.
But the point remains, the downright horrible community is why LFR exists and oQueue too.
oQueue is a good tool, but the very functionality it has to use is attracting the wrong sort of attention from blizzard.
Lets hope their own version avoids the need for something like that.
There is a blacklisting feature in the game, which can prevent use of an addon should blizzard dictate.
At least one early spammy version of Gearscore was blocked via that means.
They have far better ways of dealing with problem addons than "scare tactics".
Yea i dint use it
The reason are the spams from ppl who have it.Its very anoying when you log and see all these spams because your sister log before you and put that miserable (OQ) to your account notes
About Op do he is a troll or not you can easly drop ticket and ask :d
Shouldn't they just let people use OQ until the blizzard raid browser is finished and in the game. I mean come on, they have done that before with plenty of other addons, incorperated good addons into the game. Whether the OP is telling the truth or not is another question, but that's by the by.
Hi