kolton / d2bot-with-kolbot

d2bot game manager by D3STROY3R with kolbot libs by kolton for d2bs
345 stars 332 forks source link

Failed to join game #2008

Open Rzn92 opened 4 years ago

Rzn92 commented 4 years ago

hello, since last monday almost always enter game give me Failed to join game i play always 5 char in same game and never get it, but since last monday all game 2 or 3 char get stuck failed to join game, and sometimes they are all in game ... and the one after it stuck.

Some one an help me ? 2 friends have the same probleme same time of me help is welcome thanks

alfton commented 4 years ago

hi, guess you have the same problem as many, blizzard have done something here, if your followers quit the game to fast, you suffer fail to join game. https://github.com/kolton/d2bot-with-kolbot/issues/2002#issue-529557835 https://github.com/kolton/d2bot-with-kolbot/issues/2001#issue-528979014

Rzn92 commented 4 years ago

ok thank you, in fact nobody has any solution ... yes blizzard had to do something almost everyone has the same problem.

it's really weird sometimes for 1 hour everything is fine then after it's '' failed to join game '' on some character, 1 game on 2 it works normally, there is no logic of style temp ban or other , I do not see what can be '' flagg '' even changing wifi, key MAC, or cd key diablo not work, all other char work fine it's forcing the fact of bot but what circumstance causes it to be wrong. its not the game time, it can appear even if you launch only one bot ... never have it the first game i launch all my bot

Rzn92 commented 4 years ago

hi, guess you have the same problem as many, blizzard have done something here, if your followers quit the game to fast, you suffer fail to join game. #2002 (comment) #2001 (comment)

its your post, have find any solution ?

and its not delay for follower leave, 2 of my follower almost never have Ftj and they leave as the same time of lead

alfton commented 4 years ago

hi, no, thats the problem, its take long time to test out becouse of this, max 2-3 attempt, and the fail to join game setts a stopper to testing out. So for now, I just run all bot in there own games, and just keep the time they are in game long enought to not get them in trouble. also have set some delay on making games, and also for the crashing part, that the bot use longer time befor enter again.

naderox commented 4 years ago

Does Proxies help ? saw on website they sell proxies so that you can bott 1 ip /bott so you dont get ftj

alfton commented 4 years ago

would not bet on it, becouse in a preemp messures blizzard have denied vpn from connecting. not sure how strix they are with proxies.

naderox commented 4 years ago

Looking for IP addresses to grow your bot empire?

All Purchases Include Free Technical Support & Setup Help

We provide thousands of Private Proxys Socks5 which can be used with all proxy programs.

No more sharing IP addresses, and no more paying for overpriced private proxies.

You will receive a username and password via E-Mail within 1-2 days of purchase to access all these IPs.

All IP addresses are legit.

22,50 dollars/month xd and its for diablo bots so idk

alanchais2 commented 4 years ago

Seems I'm getting better results doing solo MF runs with my paladin than my light sorc. Light sorc gets RD/FTJ after about 3 games (20+ min games), while my pally bots continuously.

Anyone getting better results without a sorc? Or if you don't have any FTJ problems, what char/build do you use?

alfton commented 4 years ago

what you have to do, is to slow down the leaving, and how fast you join. I have 3 bot in same game now, and they have been runing 24 hours without any RD, or fail to join. you have to if the soso chicken, put extra delay before creating new game.

AlmightVictorP commented 4 years ago

It's Bnets way of temp banning you. You need to adjust your create game time. If you exceed 25 games per hr, then you risk getting FTJ because you're in a line to create game soft ban.

alanchais2 commented 4 years ago

My runs usually last around 20 mins, so that's not the issue. I had to add a manual delay to leaving for solo bots which helps.