What is wrong with the NAV & Auth Servers?
- Thread starter Dem
- Start date
shinoowns
New Member
- Joined
- Jan 15, 2010
- Messages
- 320
- Reaction score
- 1
logs?! no OK then no help. For instance I've been running the bot completely fine for the past few versions and noone wants to post anything about when / how if error message logs nothing. How would you want help or are you just posting a complaint and being useless.
Logs for what? If you check the recent threads there at tens of people complaining about DB servers problems. I reversed to older version of DB and was running strong for the past 3 days until last night when all the drops, stucks and disconnects started. No, the problems are not on my side.
Code:
[16:17:07.713 N] ========== Grid segmentation resetting!!! ============
[16:17:08.538 N] Demonbuddy v1.0.994.250 started
[16:17:09.837 N] Logging in...
[16:17:17.121 N] Attached to Diablo III with pid: 8388
[16:17:17.139 N] Flashing windowJust now Auth dropped all of my bots but one... AGAIN. This is just ridiculous. I will just stop until this is solved, ffs.
This is not DB version related. I was using v222 flawlessly until last night when the disconnects/stucks started. Currently I shut all my bots down just becuse they either get stuck and keep remaking games or they get DB disconnected, which is happening every 30 mins now. Nothing has changed from the flawless version I was running software-wise so it is definitely DB Servers that are causing the problems.
Comments like this are just hilarious.
Wow!!! Their servers are resetting once, every few hours MAYBE, for a 2-day period. Everything is broken how dare they this is bullshit!
I have been DC'd 3 times in 48 hours, each for less than 5 minutes. Servers can have issues, any kind of servers, it's not the end of the world to take a 5-10 minute break and restart it.
Also, as someone else said, this has NOTHING to do with your DB version at all. This is 100% server-side drops, so saying dumb shit like 'I shut them down when .250 was released' is pathetic. Especially considering if you bothered to update your profiles as you were supposed to, .250 is running absolutely perfectly with Giles and the Ciggarc champion hunts.
Yes servers can have issues, and it doesn't happen all that often, but downtime is downtime and usually a bad sign. Down for 5 minutes when I go to sleep might mean 3 bots not doing anything for 8 hours each, or longer if I'm out of town.
And if the DB team is resetting the servers or w/e, some notice might be nice? It is rather obvious for blizzard if 10k accounts all logout at the exact same moment?
ezpwnd
New Member
- Joined
- Jul 18, 2012
- Messages
- 950
- Reaction score
- 1
hahaha, didnt think of this one. kinda funny lal
My problem is the self-entitledness of the people posting in here. Woe is me, 1 night off botting while they fix some issues with their servers...
Downtime is downtime, and it's to be expected. If a full operation with a full staff and billions of dollars such as Blizzard can have un-expected delays going 4+ hours of solid 100% downtime, then you would hope people here can give slack considering its a group of ~5 people, without all the resources at their disposal. People need to calm down and wait.
If you choose to leave your bot unmonitored, then that's the risk you're taking if things crash/freeze/servers go down, or anything like that, is you are not watching it.
People such as myself monitor the bot 90% of the time on another monitor or another means, so if it drops a session it takes me 30 seconds to remote in, or if im here just relog it and keep going, or leave the game and check the AH if its not up. Posting here like everyone deserves to have this fixed immediately, and that somehow they are almost OWED something for this is a fucking joke. And that's the attitude of 99% of the posters here.
Downtime is downtime, and it's to be expected. If a full operation with a full staff and billions of dollars such as Blizzard can have un-expected delays going 4+ hours of solid 100% downtime, then you would hope people here can give slack considering its a group of ~5 people, without all the resources at their disposal. People need to calm down and wait.
If you choose to leave your bot unmonitored, then that's the risk you're taking if things crash/freeze/servers go down, or anything like that, is you are not watching it.
People such as myself monitor the bot 90% of the time on another monitor or another means, so if it drops a session it takes me 30 seconds to remote in, or if im here just relog it and keep going, or leave the game and check the AH if its not up. Posting here like everyone deserves to have this fixed immediately, and that somehow they are almost OWED something for this is a fucking joke. And that's the attitude of 99% of the posters here.
satan2004
New Member
- Joined
- Jun 12, 2012
- Messages
- 456
- Reaction score
- 0
i dont think you understand the point of a BOT!
IT IS TO BE ABLE TO LEAVE THE FUCKER ALONE while you do other shit!