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

42002, Blizzard and Bots

Status
Not open for further replies.
i got this bug yesteday. turned of diablo / bot / computer for the night (aprox 8 hours) turned it on with chestrunner with 30-60 secs between games.
so far it have run for 5 hours without getting the error. im getting lower LPS ofc at it can wait up to a whole minute untill it creates a new game.
but so far its up n running this way
 
Fusionx17 said:
Another quick update:

Total tracking time: 8h 1m 54s
Total games (approx): 482 [60.01 per hour]

Still running strong with 3-5 minute breaks randomly every hour
Click to expand...

How do you set random interval breaks every hour?
 
charlieh0rse said:
How do you set random interval breaks every hour?
Click to expand...

I've been using a auto-it script - its very inefficient.
I am going to try and bring one of the old auto break plugins up to date sometime in the next couple of days
 
xblinov said:
stop plz this stupid arguing....No tagging or bans are incoming...Whole this shit 42002 is about Telia.net(or i don't remember the name of main Blizz Europe provider) problems that are caused by DDoS attacks and I think May holiday's around nearly whole Europe...It's just an element to not give a single fuck about supporting game "THAT MUCH" during holidays and provider problems...Mentioned problems will be solved soon i hope and 42002 will disappear.
So plz close this thread and stop shittalking.
Click to expand...

:D accept.
 
I assume increasing games per hour won't help against this error? Kinda annoying having to have offline time with the bot
 
no, increasing gph does not solve it, lol.

if anything, decreasing gph is more likely to help. I stopped my bot for a few hours yesterday and haven't had the error since, using ghom safe profile (no insta leave) and 7-8 sec delay between games.

a solution to have breaks of a few minutes every hour would be great, then you can basically run the bot 24/7 again while being afk. now, you can't really do that because it'll pretty much trigger 42002 guaranteed.
 
I switched to Non-instaleave ghomprofile and delay to 3-6 seconds between games, seems to help. This dropped my GPH below 60, so it seems that for me, 60 GPH is the number to stay below.
 
After about 42~ hours of running - finally got error 42002.
Taking breaks definitely helps - but its not an end all fix unfortunately.
 
Soldiersbane said:
I put in a ticket and this is what they had to say.


"Thanks for contacting us today about getting error 42002.

Currently this error is related to multiboxing. Anytime you try to login with multiple accounts it will provide this error. Currently it's best to just run 1 account at a time and not together. Currently it's unknown to us if it's going to be worse later on for multiboxing, or if it's just a bug right now. I'd highly suggest just running one for right now and later on it may work again."
Click to expand...

If it is true that it's related to multiboxing odds are at some point demonbuddy is making games too fast (or servers lagging and demonbuddy sends a 2nd request for a game) and with the fact that blizz servers are beyond shit it's logging as double log on realizing it isn't then tossing an error out.

Edit: wording
 
Last edited:
multiboxing - 1 account is trying to create a game too fast on top of another accounts disconnect that causes a bug at blizzard and gives that error

HOWEVER - even tho the bug is not intentional this might get them thinking about games/hr and maybe bots because its fresh news. for us no news is good news.
 
I was using insta leave for the last 4 weeks+ on Ghom, I switched over to non instant leave. I was getting about 52 GPH on T6 Ghom and I still encountered the error. I put a 15-20 second create timer in between, dropped me to 46GPH roughly and I still got the error. As it stands right now, I can restart D3 and go error free for anywhere 5-8hrs sometimes longer WITH INSTANT LEAVE and get 60gph+, or switch to the TP/exit mode and add a 5-15 delay and STILL get the error after 3-8 hours. It's all been random for me, It usually takes 2-3 hours to kick in before error happens at the earliest, sometimes upwards of 5 hours depends. I started switching my bot between rift/bounty farming or not using D3 at all and it increased the time I was able to bot before I got the errors. Pretty much at this point we have too much speculation and no real facts. Blizzard doesn't need some GPH throttler to tell who botters are, it would be obvious from the playing while AFK or the statistics shown in profile(not to mention the ones they probably have you can't see, like what you've been doing, repeating etc over and over). If they wanted us banned, we would be. They would not just set a GPH limit and start tagging people, I know NON BOTTERS who are getting this same issue when they farm crafting mats, and others who are just playing normally doing fast games.
 
Skovmand said:
But then again. It should not matter if you show on battle.net forum you have the problem. If its an error aimed at botters. At the time you get the error, you should already be flagged. Showing it on the forum should not change much.

As long as the actual bot is undetected Blizzard cant do much. If they start to ban people making too many games/h, we would just decrease the time between games and eventually they would ban "real" people playing the game. That would be a lost battle for Blizzard, and they should know it. External hacks are the future.
Click to expand...



All blizzard has to do is read your cpu's memory and see if your running programs that are reading Diablo 3 memory.
 
42002 happens around peak time for me, i switch it over to rifts or bounties that take time, rather then full on 1boss/reset scripts. After peak time, i can spam games to my hearts content. it's a throttle to stop queues for legit players.

stopping the person with 50-70games/hour > legit players suffering queues.
 
Status
Not open for further replies.
Back
Top