What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

My time with the BBB and Blizzard

H

HyperionX

New Member
Joined
Dec 18, 2012
Messages
5
Reaction score
0
Copy and pasted info from my complaint with the BBB about Blizzard banning my account. Some of the information may be informative. Blizzard is most likely watching this thread. I would recommend others to follow through with complaints even if its futile. I made Blizzard listen to me when the ticket system did not. I will not confirm nor deny unauthorized third party programs were used in conjunction with my banned account but figured this would be the appropriate place to put this. Enjoy.

Complaint Description - Posted 12/26/2012 2:55:14 PM
Blizzard banned my Diablo 3 (PC GAME) account wrongly. I Attempted to sort this out through customer support tickets with no satisfactory resolution nor a clear reason as to why it was banned.. My account was banned wrongly. I have spent about 600 hours playing the game only to see my time go to waste.

Complaint Summary
Account banned by blizzard in diablo3 mistakenly. Attempted to contact support countless times with no clear answer nor a way for it to be unbanned.
Resolution Sought
Unban my diablo3 account or refund my purchase for the game and real money auction house purchases.

Company's Response

Company's Initial Response - Posted 12/31/2012
An investigation conducted on behalf of the customer?s Diablo III account. Upon conclusion of the investigation, it was discovered that the Account was found to be employing a third party program that modifies the game. When the account was logged into the game server, Blizzard?s system detected a third party program that has been prohibited for use in conjunction with Diablo III by Blizzard. The use of these programs is a violation of the Battle.net Terms of Use since it harms the game environment and gives the player unfair advantages over other players. According to the Battle.net Terms of Use Agreement which all subscribers agree to upon registering an account to play Diablo III, ?use cheats, automation software (bots), hacks, mods or any other unauthorized third-party software designed to modify the Service, any Game or any Game experience?. For additional information on the Battle.net Terms of Use, please visit: Blizzard Entertainment:Battle.net Terms of Use Under these circumstances, the account was terminated on 12/18/12. A notice of Account Closure detailing the Terms of Use violation was sent to the customer?s registered email address on that day. Any disputes or questions concerning this account action can only be addressed by Account Administration by submitting a Support Site ticket on your battle.net account. For additional questions on how Account Administration can assist you, visit http://us.battle.net/support/en/article/account-administration-overview for more information.
Initial Response Summary
Customer was in violation of the Battle.net Terms of Use. Please contact Account Administration for additional assistance.

Consumer's Rebuttal

Consumer's Rebuttal - Posted 01/02/2013
the administration and ticket system does not dispute bans. All bans are final with Blizzard's system even if the account was wrongly banned. Blizzard refuses openly communicate with me to get the account unbanned nor will it show any proof of third party programs being used. I have proof of financial loss because the game is online only. By banning my cd key you have prevented me from using the product at all. I did not violate any terms of use. I never agreed to the TOS. The stores do not accept refunds on the game because its online only. I had no choice but to accept Blizzards terms but that is another story. Refund my money or unban my account unless you can show proof. If not I will seek arbitration

Company's Final Response

Company's Final Response - Posted 01/11/2013
According to Blizzard?s internal logs, the records show that an unauthorized third party program was detected when the account logged into the game server. Upon review of the IP logs for the account, Blizzard has discovered that the IP matches the customer?s normal play location. Additionally, several in-game tests were performed by Blizzard?s Account Administration team that showed that the character actions on the account were automated by a third party application. Account Administration has determined that the account shall remain closed on the basis that the account was not compromised and its subsequent use of the unauthorized program. This issue has been reviewed by several levels of our organization, and we consider the matter closed. To be eligible for a refund, you must apply within 14 days of the digital purchase of the product; however, if you exceeded the trial limits set within Diablo III, you are not eligible for a refund
 
this: Additionally, several in-game tests were performed by Blizzard?s Account Administration team that showed that the character actions on the account were automated by a third party application.

Hm... how the fuck... this is really really interesting...
 
According to Blizzard?s internal logs, the records show that an unauthorized third party program was detected when the account logged into the game server.
Click to expand...

This is what i was talking about in a thread i created the other day about reloggers. something has felt off about the login / auth servers for awhile now. also all the maintenence they did on them prior to 12/18 holds some water.


Upon review of the IP logs for the account, Blizzard has discovered that the IP matches the customer?s normal play location.
Click to expand...

I guess this gives some weight to the v--pn guys.

Additionally, several in-game tests were performed by Blizzard?s Account Administration team that showed that the character actions on the account were automated by a third party application.
Click to expand...

This in my opinion are the crashes that are abundant before a wave.


Thank you for posting this.
 
HyperionX said:
//// Additionally, several in-game tests were performed by Blizzard’s Account Administration team that showed that the character actions on the account were automated by a third party application.///
Click to expand...
they crashing *DB* via playing with memory and DB crashes Diablo client = Loged acc is a bot
- imho
 
Metaxer said:
they crashing *DB* via playing with memory and DB crashes Diablo client = Loged acc is a bot
- imho
Click to expand...

Every time db crashes as far as i could have witnessed is manually leaving the game and going to character screen while db is not stopped...
 
I would like a response from one of the devs on this one. This seems like very valuable information the original posters has giving us.
 
"Additionally, several in-game tests were performed by Blizzard’s Account Administration team that showed that the character actions on the account were automated by a third party application."

Means they pattern detected us, easy to do considering they can get a copy of the bot and the profiles... Since private profiles were banned also it was probably DB core (town run routine??) To prevent future detection with the same method we need: Randomized MoveTos, Randomized Routes, Randomized Profiles, Randomized CCs. Most people believe this to be over kill but based on what blizz said in that BBB report it isn't overkill.

Also to OP: Try to argue more about the loss of account due to it being online only. Or is the case permanently closed? If it is closed, did they get a negative mark?
 
cdmichaelb said:
"Additionally, several in-game tests were performed by Blizzard’s Account Administration team that showed that the character actions on the account were automated by a third party application."

Means they pattern detected us, easy to do considering they can get a copy of the bot and the profiles... Since private profiles were banned also it was probably DB core (town run routine??) To prevent future detection with the same method we need: Randomized MoveTos, Randomized Routes, Randomized Profiles, Randomized CCs. Most people believe this to be over kill but based on what blizz said in that BBB report it isn't overkill.

Also to OP: Try to argue more about the loss of account due to it being online only. Or is the case permanently closed? If it is closed, did they get a negative mark?
Click to expand...

"In game test" to me sounds like they wait until you are playing and then do some kind of live test, where your subsequent actions are either human or bottish.
 
HyperionX

Is this a 18th december ban? Because that was probably a one off ban method that has hopefully now been fixed.
 
why nobody cares about this sentence

According to Blizzard’s internal logs, the records show that an unauthorized third party program was detected when the account logged into the game server.

also i wonder why bot does not stealth itself
 
This crashes have something to do with them. I'm sure! I mean... I had 11 Accounts online on 1 Pc, 10 Bots and 1 Mule.
The day before they got banned, they all crashed at the same time! My Mule was the only one online as I was back to take a look at them.
So this wasn't a normal disconnact or something. I have Db logs, that all 10 Bots crashed at the same time. In 2 weeks they never crashed!
I'm running also a second Pc with 8 Bots but none of them crashed, atleast not all at the same time and they are alive!
Actually my bots are online and no crashes....so this must by a way how they can detect us, even more "the" way how they can be sure to ban us.
It's just my opinion but I don't believe that this was just an unhappy coincidence!

Thats the end of the logs as they crashed:

Code: 
[13:12:05.687 D] Navigator.Clear
[13:12:05.687 D] Successfully generated path from {X=418,Y=278} to {X=437,Y=278} in 00:00:00.0000927 with 20(2) hops
[13:12:05.767 D] Generating path to GoatMutant_Ranged_B - <1644.914, 1057.652, 0.1>
[13:12:05.777 D] Successfully generated path from {X=419,Y=277} to {X=423,Y=274} in 00:00:00.0000591 with 5(2) hops
[13:12:05.777 D] Client path generated.
[13:12:05.777 D] Generated path to <1644.914, 1057.652, 0.1> (GoatMutant_Ranged_B) with 2 hops.
[13:12:20.957 N] Closing error dialog
[13:12:22.857 D] System.NullReferenceException: Object reference not set to an instance of an object.
   at GilesTrinity.GilesTrinity.GilesGlobalOverlord(Object ret)
   at GilesTrinity.GilesTrinity.<ReplaceTreeHooks>b__18(Object ctx)
   at Zeta.TreeSharp.Decorator.CanRun(Object context)
   at Zeta.TreeSharp.Decorator.Class232.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.Class234.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Common.HookExecutor.Run(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action.Class172.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.Class234.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.CommonBot.BotMain.smethod_1()
[13:12:22.867 N] Waiting 20.3 seconds before next game...
[13:12:43.217 D] System.AccessViolationException: Could not read bytes from 00000000 [299]!
   at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
   at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
   at Zeta.Internals.Service.BnetHero.get_Native()
   at Zeta.Internals.Service.BnetGames.CreateGame(Act act, GameDifficulty difficulty, Int32 quest, Int32 questStep, Boolean resumeFromSave, Boolean isPrivate, Int32 handicap)
   at Zeta.CommonBot.Logic.BrainBehavior.smethod_107(Object object_0)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action.Class172.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Sequence.Class237.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Decorator.Class232.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.Class234.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.Class234.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.Common.HookExecutor.Run(Object context)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action.Class172.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Decorator.Class232.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.Class234.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.CommonBot.BotMain.smethod_1()
[13:12:43.227 N] Closing error dialog
[13:12:43.327 N] Lost Connection. Closing Diablo III and Demonbuddy
[13:12:43.327 D] System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it.
   at System.Windows.Threading.Dispatcher.VerifyAccess()
   at System.Windows.Application.CriticalShutdown(Int32 exitCode)
   at Zeta.CommonBot.Logic.BrainBehavior.smethod_177(Object object_0)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action.Class172.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Sequence.Class237.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Decorator.Class232.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.Class234.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Decorator.Class232.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.Class234.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.CommonBot.BotMain.smethod_1()
[13:12:43.337 N] Lost Connection. Closing Diablo III and Demonbuddy
[13:12:43.337 D] System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it.
   at System.Windows.Threading.Dispatcher.VerifyAccess()
   at System.Windows.Application.CriticalShutdown(Int32 exitCode)
   at Zeta.CommonBot.Logic.BrainBehavior.smethod_177(Object object_0)
   at Zeta.TreeSharp.Action.RunAction(Object context)
   at Zeta.TreeSharp.Action.Class172.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Sequence.Class237.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Decorator.Class232.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.Class234.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.Decorator.Class232.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.TreeSharp.PrioritySelector.Class234.System.Collections.IEnumerator.MoveNext()
   at Zeta.TreeSharp.Composite.Tick(Object context)
   at Zeta.CommonBot.BotMain.smethod_1()
[13:12:43.447 D] System.AccessViolationException: Could not read bytes from 00000788 [299]!
   at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
   at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
   at Zeta.MemoryManagement.InProcessMemoryReader.Read[T](Boolean isRelative, IntPtr[] addresses)
   at Zeta.ZetaDia.get_CurrentWorldId()
   at Zeta.ZetaDia.get_IsInGame()
   at Zeta.CommonBot.BotMain.smethod_1()
[13:12:43.447 N] Diablo III Exited, Demonbuddy terminating
[13:12:43.457 D] System.AccessViolationException: Could not read bytes from 01873414 [299]!
   at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
   at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
   at Zeta.MemoryManagement.InProcessMemoryReader.Read[T](Boolean isRelative, IntPtr[] addresses)
   at Zeta.ZetaDia.get_CurrentWorldId()
   at Zeta.ZetaDia.get_IsInGame()
   at Zeta.CommonBot.BotMain.smethod_1()

It sais "Lost Connection" so it should be a disconnect I think, but if it was a real disconnect, all active Bots and my mule should be offline, which was not the case.
 
Last edited:
Shitjustgotreal said:
This crashes have something to do with them. I'm sure! I mean... I had 11 Accounts online on 1 Pc, 10 Bots and 1 Mule.
The day before they got banned, they all crashed at the same time!
Click to expand...

I'm afraid that you are right. :(
This night i've left my bots active and when i've checked the PC in the morning all three were off. Crashed and dc'ted. BlizzardError is disabled and the report do not come trough firewall, but i'm not sure it will help me.
If ban wave will come this week again (during today's maintenance maybe) i'm probably gonna lose my bots again, just like on 18/12.
Because i've experinced the same weird crashes back then, shortly before ban hammer struck.
 
Lol yeah, same here, i had all of my bots crash but 2 (hm strange ? ) 3 days back. I knew it was not some random disconnect, and no way it was a coincidence. I guess we see what happens after maintenance...
 
cdmichaelb said:
"Additionally, several in-game tests were performed by Blizzard?s Account Administration team that showed that the character actions on the account were automated by a third party application."

Means they pattern detected us, easy to do considering they can get a copy of the bot and the profiles... Since private profiles were banned also it was probably DB core (town run routine??) To prevent future detection with the same method we need: Randomized MoveTos, Randomized Routes, Randomized Profiles, Randomized CCs. Most people believe this to be over kill but based on what blizz said in that BBB report it isn't overkill.

Also to OP: Try to argue more about the loss of account due to it being online only. Or is the case permanently closed? If it is closed, did they get a negative mark?
Click to expand...

The BBB closed it. So no more replies are allowed. They said the info would be released to the public.
 
Last edited:
Here's mine response from BBB:

Company's Response

Company's Initial Response - Posted 12/31/2012
An investigation conducted on behalf of the customer’s Diablo III account. Upon conclusion of the investigation, it was discovered that the Account was found to be employing a third party program that modifies the game. When the account was logged into the game server, Blizzard’s system detected a third party program that has been prohibited for use in conjunction with Diablo III by Blizzard. The use of these programs is a violation of the Battle.net Terms of Use since it harms the game environment and gives the player unfair advantages over other players. According to the Battle.net Terms of Use Agreement which all subscribers agree to upon registering an account to play Diablo III, “use cheats, automation software (bots), hacks, mods or any other unauthorized third-party software designed to modify the Service, any Game or any Game experience”. For additional information on the Battle.net Terms of Use, please visit: Blizzard Entertainment:Battle.net Terms of Use Under these circumstances, the account was terminated on 12/18/12. A notice of Account Closure detailing the Terms of Use violation was sent to the customer’s registered email address on that day. Any disputes or questions concerning this account action can only be addressed by Account Administration by submitting a Support Site ticket on your battle.net account. For additional questions on how Account Administration can assist you, visit http://us.battle.net/support/en/article/account-administration-overview for more information.
Initial Response Summary
Customer was in violation of the Battle.net Terms of Use. Please contact Account Administration for additional assistance.



Consumer's Rebuttal

Consumer's Rebuttal - Posted 01/08/2013
Sorry, but I have no clue where they are getting that I was using a third party program because I dont even understand what they mean by Third party program I have quite a few of programs on this laptop but I am not the only one that uses this laptop but I know that I personally have not used any other programs. Ive personally put over 1000 hours of gameplay into that game over the past 6 months I dont see how its fair that just because they detected a program on my computer isnt that an invasion of privacy looking through my programs. This really upsets me that they would do this to a customer



Company's Final Response

Company's Final Response - Posted 01/11/2013
According to Blizzard’s internal logs, the records show that an unauthorized third party program was detected when the account logged into the game server. Upon review of the IP logs for the account, Blizzard has discovered that the IP matches the customer’s normal play location. Additionally, several in-game tests were performed by Blizzard’s Account Administration team that showed that the character actions on the account were automated by a third party application. Account Administration has determined that the account shall remain closed on the basis that the account was not compromised and its subsequent use of the unauthorized program. This issue has been reviewed by several levels of our organization, and we consider the matter closed.
 
Also, not sure if any of you noticed, but right before the ban wave (aside from the crashes) I saw 'objects' in my bots usual path. I noticed my bot getting stuck with 'special' boulders and object placement. Wish I would have taken a screen shoot of it to show you guys. Example, I saw a boulder on the stairs in stonefort on act 3 and another one on act 2 desolate sands towards the top of the map. Just my 2 cents on this thread.
 
Hilarious tho IMO. I received the same exact response as two previous. It seems like a blanket response from Blizzards account actions team. It looks to me that Blizzard is only responding with what seems like the most reasonable reponse and not the correct one. I find it funny that Blizzard not only auto-responds to their tickets, but to the BBB as well.
 
Very interesting stuff.

I think it's plausible that there would be something happening beyond just pattern recognition, because pattern recognition will only ever collect circumstantial evidence- it can never PROVE a bot was running.

Something like a manual test where they can change contents of memory and trigger db crash / d3 client crash would definitely be more solid evidence they could use in case it ever went to court/arbitration.

So.. maybe DB devs need to start logging invalid memory access leading to crash? Perhaps it might show patterns before a ban wave?
 
You must log in or register to reply here.
Back
Top