im not using anything special, using the base beta eb
Bot will play for a random amount of time then stop moving, wont log, nothing
- Thread starter Seero
- Start date
amwilliams
New Member
- Joined
- Dec 17, 2012
- Messages
- 20
- Reaction score
- 0
hmm.. well I'm kinda running into new issues now as well. lol. (before I had freezing issues that were just completely locking everything). Now my character will randomly stop and be extremely slow to respond or not respond at all. I'm going to start a new thread with logs.
Theres like no point, Im going through and reading other threads and none are being answered lol.
all of them basically have said the same thing I said, they all come down to freezing in the game and having to completely start over or restart from desktop. After leaving the Bot for hours and coming back to see that it did nothing. Kinda not cool.
Thats what I am hoping for =)
A few new beta builds have come out, but they havnt fixed it.
imdivesmaintank
New Member
- Joined
- Oct 30, 2013
- Messages
- 342
- Reaction score
- 0
still doing it in 622
Code:
2013-11-25 21:47:27,028 [Main Bot Thread] DEBUG ExilePather (null) - The current pathfinding data has been reloaded in 00:00:00.0079212.
2013-11-25 21:47:27,038 [Main Bot Thread] DEBUG ExilePather (null) - [Hull] The stored pathfinding data has been modified in 00:00:00.0097499.
2013-11-25 21:47:27,039 [Main Bot Thread] DEBUG ComponentInformation (null) - Adding new ComponentMap Cache for Metadata/Items/Armours/Shields/ShieldInt2.ao (Miss #605)
2013-11-25 21:47:27,041 [Main Bot Thread] DEBUG ExilePather (null) - Adding hull for Sarcophagus at {1115, 1046}.
2013-11-25 21:47:27,050 [Main Bot Thread] DEBUG ExilePather (null) - [Hull] The stored pathfinding data has been modified in 00:00:00.0090301.
2013-11-25 21:47:27,051 [Main Bot Thread] DEBUG ComponentInformation (null) - Adding new ComponentMap Cache for Metadata/Items/Armours/BodyArmours/BodyInt2B.ao (Miss #606)
2013-11-25 21:47:27,052 [Main Bot Thread] DEBUG ComponentInformation (null) - Adding new ComponentMap Cache for Metadata/Items/Weapons/OneHandWeapons/Claws/Claw5.ao (Miss #607)
2013-11-25 21:47:27,077 [Main Bot Thread] DEBUG ExilePather (null) - The stored pathfinding data has been adjusted in 00:00:00.0223464.
2013-11-25 21:47:38,850 [Main Bot Thread] DEBUG ExilePather (null) - Adding hull for Sarcophagus at {724, 655}.
2013-11-25 21:47:38,859 [Main Bot Thread] DEBUG ExilePather (null) - The current pathfinding data has been reloaded in 00:00:00.0086629.
2013-11-25 21:47:38,869 [Main Bot Thread] DEBUG ExilePather (null) - [Hull] The stored pathfinding data has been modified in 00:00:00.0091075.
2013-11-25 21:47:38,878 [Main Bot Thread] DEBUG ExilePather (null) - The stored pathfinding data has been adjusted in 00:00:00.0076329.
2013-11-25 21:47:41,549 [3] INFO (null) - Session is invalid!
Code:
2013-11-25 21:46:27,932 [Main Bot Thread] DEBUG (null) - Using Quicksilver Flask for movement!
2013-11-25 21:46:35,781 [Main Bot Thread] DEBUG ComponentInformation (null) - Adding new ComponentMap Cache for Metadata/Items/Amulets/Amulet2 (Miss #408)
2013-11-25 21:46:35,782 [Main Bot Thread] DEBUG Targeting (null) - Ignoring Coral Amulet [5702] from loot targeting. (No Filter Match)
2013-11-25 21:46:37,761 [Main Bot Thread] DEBUG (null) - Using Quicksilver Flask for movement!
2013-11-25 21:46:45,008 [Main Bot Thread] DEBUG Targeting (null) - Ignoring Ursine Pelt [53EE] from loot targeting. (No Filter Match)
2013-11-25 21:46:50,977 [Main Bot Thread] DEBUG Targeting (null) - Ignoring Karui Chopper [47C4] from loot targeting. (No Filter Match)
2013-11-25 21:47:00,409 [Main Bot Thread] DEBUG Targeting (null) - Ignoring Siege Axe [39E9] from loot targeting. (No Filter Match)
2013-11-25 21:47:00,411 [Main Bot Thread] DEBUG ComponentInformation (null) - Adding new ComponentMap Cache for Metadata/Items/Weapons/OneHandWeapons/OneHandAxes/OneHandAxe10 (Miss #409)
2013-11-25 21:47:00,411 [Main Bot Thread] DEBUG Targeting (null) - Ignoring Chest [E46] from loot targeting. (Opened Chest)
2013-11-25 21:47:00,412 [Main Bot Thread] DEBUG Targeting (null) - Ignoring Tomahawk [3E78] from loot targeting. (No Filter Match)
2013-11-25 21:47:14,100 [3] INFO (null) - Session is invalid!Session is invalid bug.
Also these are my current errors as of the latest builds:
View attachment 8796 2013-11-25 13.27 Errors.txt
View attachment 9060 2013-11-25 11.22 Errors.txt
Im using a summoner and so Ill generally use Exile with grindbot.
Ive been told to use Apoc but I die a lot more and use less skills.
I fixed my issue by opening path of exile and closing the bot and opening it again.. after a few tries it worked. My other problem was it wasnt using spectral throw and i went into the routine and added that as the top of my list.. now i have the most efficient farming thing EVER. I'm clearning mericless ledge at like level 55 in 2-3minutes.... i got about 3 exalteds worth last night and 5 legendaries.. Its friggin amazing. If anyone needs help with it i can quickly tell you how to fix what skills to use. because spectral throw is amazing for farming.
Thank you for attaching the log.
Everyone who is having this problem is seeing the same bug with the "Loki.Bot.Exploration.ExplorationManager", which is currently being changed to address some issues with it. We're not sure yet why it's suddenly breaking as of the past week or so, but we're checking into it.
We try to reply to as many threads as possible with bugs, but sometimes we don't since otherwise there wouldn't be time to fix the bot.
Thanks for your patience!
Everyone who is having this problem is seeing the same bug with the "Loki.Bot.Exploration.ExplorationManager", which is currently being changed to address some issues with it. We're not sure yet why it's suddenly breaking as of the past week or so, but we're checking into it.
We try to reply to as many threads as possible with bugs, but sometimes we don't since otherwise there wouldn't be time to fix the bot.
Thanks for your patience!Thank you for attaching the log.
Everyone who is having this problem is seeing the same bug with the "Loki.Bot.Exploration.ExplorationManager", which is currently being changed to address some issues with it. We're not sure yet why it's suddenly breaking as of the past week or so, but we're checking into it.
We try to reply to as many threads as possible with bugs, but sometimes we don't since otherwise there wouldn't be time to fix the bot.
hey better late then never, and I assumed with all the beta updates the last few days something was going on lol.
Also the last build, not the latest, my bot actually didnt freeze for once.. just ran out of room =p. Hopefully it will continue that.