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

Strange loop/bug leading to bot hangup

PainfulDeath

Member
Joined
Jul 12, 2012
Messages
489
Reaction score
1
Came back to a bot dead in the desecrated ground trying to open a chest with logs
Code:
[LootItemTask] The current item to loot is [12159] Maelström Staff at {xx, yy}. We have been on this task for 00:00:01.2576838 and have been attempting to interact for 00:00:00.9519662.
[RemoveItemLocation] The location 12159 [Maelström Staff] is being removed.
[OpenChestTask] The current chest to open is [26439] Chest at {x, y}. We have been on this task for 00:00:02.2776347 and have been attempting to interact for 00:00:00.
[OpenChestTask] Now moving towards the chest 26439 because it is 129.8015 away (can't see).
[OpenChestTask] The current chest to open is [26439] Chest at {x, y}. We have been on this task for 00:00:02.9645692 and have been attempting to interact for 00:00:00.
[OpenChestTask] Now moving towards the chest 26439 because it is 70.13252 away (can't see).
Nothing happened after this for 3.5 hours. I have unstuck enabled but it didn't work.
The bot won't do anyhting, revive and also cannot even be properly stopped. When pushing stop button the log line "requesting bot thread to stop" comes, but nothing happens.
Seems like the openchesttask can't process being randomly dead?
 
the same exact thing happened to me again (except there was no desecrated ground). Also I think it was the same type of map (Graveyard or maybe Cemetery, I only noticed the tileset, not the name of map). Maybe that's the problem one, I'll blacklist it for now.
 
Last edited:
yep, happened to me some times. Only in graveyard, the logging was exactly like yours.
 
Back
Top