What's new
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

New problem, DB or Diablo server?

Sindigger

New Member
Joined
Jun 11, 2012
Messages
55
Reaction score
1
Running same profile I ran all day yesterday with no problems.
Now when running skarkoth something is "remembering" if the cellar is open or not on the first run through, and mimicking that behavior for the remainder of the runs. Not sure if this is a hotfix change from diablo or if something changed with demonbuddy.
For example, if I start a skarkoth run and the buddy sees the cellar as open, every recreated game after that thinks that the cellar is open, if it is or isn't, and gets stuck at the first closed cellar. Likewise if the first run the cellar is closed, it assumes the cellar is always closed and never goes in. Here is a log with cellar being opened the first time in the run then closed the second.
 

Attachments

If were talking about v1.0.646.158 , then im having problems too - Bot is not using Town Portal on ZK run, after he runs out of the soulstone room.
 
If were talking about v1.0.646.158 , then im having problems too - Bot is not using Town Portal on ZK run, after he runs out of the soulstone room.
I'm having no problems on ZK with .158
 
same problem here stuck at the entrance of the cellar
 
I'm also having this problem. It usually runs fine until it finds the first cellar. Then it does its usual thing but on subsequent runs after that it walks over to the cellar even if its closed off....then it gets stuck and wanders around until the zombies kill him.
 
I'm running in to the same problem. I'm using the WD specific profile, but i've tried others as well to verify it wasn't the profile. I run a little over half way to the cellar then tp and leave game if it is up or not.
 
It is the new update for DB roll back to 155. I had the same problem this morning and after i rolled back it is working fine. Although D3 seems to have a bit of a lag issue also.
 
If you notice there was a change made to bot execution stack cache

  • Reset the order caches when you join a game now instead of reloading the profile when it's completed.

It may not seem like it but that is the most likely cause in my opinion; of course I'm guessing :confused:
 
Back
Top