I'm not using unstucker anymore after i tested the profile restarter, and with the last version of DB, almost all stuck it's been solved by the DB itself.
Thanks, just a question, did you bot follow mosters there and trying to get to right waypoint or did it just stuck?
It unstucked when the profile restarter unstucker kicked in. DB built in unstucker only moved it closer to the bush. It didn't chase monster there, it met some monsters when it arrived there however. The actual stuck spot is actually more at where the green corpse is, DB unstucker moved the char down a little.
Using 1.6 - Seems to get stuck here on latest version (first time and only on one bot I've seen this) - I tried manually moving ("manually unstucking") around the left and then around the right of the obstacle a bit but it just went right back down into that dip and got stuck again.
Its DB sucking arround... -.- Had something like that too, had to loot a chest (was near) and after the bot got the gold, he ran the normal route... I think unstucker/DB is some kinda bugged (sets the "unstuck-point" as the next waypoint somehow...)
Yeah, DB-Unstucker moves ALWAYS south... ...thats way i use 3x unstucker right now (but will try to turn unstucker 1.8 off)^^
I dont think it has anything to do with 1.6, field of mistery have been touched in 1.6 But ill take a look at the waypoint. Its good that i got stuck in a cave, that way i could do specific unstucks for just that cave.
Uhm wondering... Is DB updating itself or how does that all work out? Oo I can't really seem to find the version numbers anywhere, just says; Demonbuddy. Also Radonic, I was wondering if its possible to make the bot check a place for champions in the Cemetery of the Forsaken.. Right before it enter the gates for The Weeping Hollow, on the left side (from the bots point of view) there is a little staircase of what it's called where the "rare" champion offen is standing with his companions.. Problem is the bot is just running past em
I get this error quite often Unable to create a game while the party is performing another operation. (Error 316700) Would it be possible to put a 1-2 second lag time between when the bot leaves the last game, and makes a new one? to get rid of this problem. Whenever I get this error it puts it in the D3 log files and could potentially be a red flag to blizz to see this constantly since its very difficult to get this bug as a non bot.
It would have a high chance to get stuck so i would just leave that to it. I rather skip one champion pack then get another stuck area. Sry dude!
It's alright Radonic =) Didn't think bout it that way.. But I get your point! I actually got the exact same thing Thirdi is speaking about.. Twice or so! I'm wondering what is causing it hehe..
Talk to the Devs of DB. They are the guys to check with. I think you get the error when the bot tries to make a game while you still are loading the lobby. You know the little lag between hitting logout and when the lobby appears. But i might be something else.
Well ill defently add it to my todo list, but it will have to have hours of testing before i could release it. As everything else. As of this moment im just trying to make this profile as AFKable as possible at the moment.
Stuck at S highlands many times, with position: x="2538.651" y="3893.556" z="-0.4362263" (new Vector3(2538.651f,3893.556f,-0.4362263f))
