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

Reporting -always stuck spot- in Areat craters.

Bertrand

Active Member
Joined
Aug 8, 2012
Messages
1,249
Reaction score
9
This is the spot, for some reason the bot wont decide to move around that statue, rather keeps bumping his head trying to reach certain waypoint in north to north-east direction.
Not sure if this is trinity or profile issue, but will mention this in tinnkaizer thread as well.
Profile used : tinnkaizer, latest .1.12 trinity, and latest .294 db.
This is the spot:


online photo sharing
 
Last edited:
Maybe you should tell which profile you are using and what version of db and trinity -_-
 
He either uses Tinnkaizer 0.5 oder SkyHigh 0.2 (or a profile with the same AC2 settings), encountered the same problem with my Barbs aswell.
Testing a possible fix with 2 Bots right now and will write back if it works. (probably a few hours though)
 
This is a DB issue, as the nav server and local nav includes a path that goes right through this one. The unstucker should handle it in a few seconds but I agree it's annoying.
 
actually, looks more like a node draw, right in the path of that object, what I have found, is after it gets blacklisted you never run into it again.

rrrix there used to be some auto blacklist thing, would this be a better option.

It was doing this one time I seen a stuck in KD2, trying to pickup gold within 15 yard of a wall, otherwise right on the other side of it. So, one version of trinity would auto blacklist that item, and you would see it scrolling

"blacklisting gold 1833"
"blacklisting gold 274"
"blacklisting gold 163"

etc, then would unstuck right away. Do you know about it or where it has vanished to. The trinity unstucker is so sensitive that it sets off a lot between profile loads, sending a multi file profile into chaos.

silly me, is the above object destructible? I found being more conservative in node placement on dungeons has also corrected this stick.
 
I have a fix for this in the next trinity build :)
 
Back
Top