gotteshand
New Member
- Joined
- Jun 7, 2012
- Messages
- 273
- Reaction score
- 1
Which act is this in? I would suggest that DB's nav server is (incorrectly) trying to calculate a path in town, and sometimes failing - despite the towninvolving only incredibly short distances. I can force a waypoint inbetween locations to help this. DB is meant to only call on the nav server for paths longer than 300 feet, but I've seen it hitting the nav server for incredibly short distances in a straight line with absolutely no objects in between just because there was a bit of Diablo 3 lag for a moment or similar, and this insatntly opens you up to problems.
Its a bit more wired then that I noticed that problem as well a long time ago and it only accrues if you enable salvaging if you just enable selling instead you're fine not cashs so I somehow doubt its caused by the nav sever I mean what need is there for the nav server inside the city..
When this type of stuck happens its rarely because of monsters in most cases its because because he wants to pickup an item/gold or interact with a shrine or chest (stuff like that).. I've seen the bot get stuck trying to interact with a shrine on a different level right next to him x/y coordinate wise but Z wise totally out of reachThere is actually already some Z-checking for objects - it helps prevent your bot targetting monsters that are on a lower-level/below a balcony from you etc.. I have to be careful not to set this cut-off-point too high as it can cause you to ignore a good shrine that's up a slight decline/incline on a hill etc. - and I've had to REDUCE that check for item drops (otherwise it would ignore an item that dropped at the top of the stairs while you were at the bottom). But it could probably be safely increased for objects like containers and shrines, as it's not a tragedy if it misses them now and then - getting stuck is worse (even if the unstucker resolves it).

Last edited: