Bot keeps returning to beginning of map

[fukuhoe]

I've been watching my bot from time to time and it keeps running back to the beginning of the map even though it has not finished exploring every part of it.

These are the logs I think? This is what I saw as the bot ran back to the beginning. Also this time was different as it didn't advance and kept staying at the same area. Normally it'll go back to the beginning then continue to explore the map until it happens again.

[ExploreDungeonTag] Fully explored area! Tag Finished.
Loaded profile Rift Bot
ToggleTargeting, new values: Looting:True LootRadius:150 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore
ToggleTargeting, new values: Looting:True LootRadius:150 Combat:True KillRadius:80
[Rift Bot] Explore Aquaducts @ 10/40/0.2
[ExploreDungeonTag] ExploreDungeon Started
[ExploreDungeonTag] Marking nearby node <186.25, 436.25, 0> as visited, distance 37/40, IsVisisted=False
[ExploreDungeonTag] Marking nearby node <163.75, 436.25, 0> as visited, distance 27/40, IsVisisted=False
[ExploreDungeonTag] Marking nearby node <186.25, 416.25, 0> as visited, distance 27/40, IsVisisted=False
[ExploreDungeonTag] Marking nearby node <181.25, 386.25, 0> as visited, distance 32/40, IsVisisted=False
[ExploreDungeonTag] Marking nearby node <161.25, 386.25, 0> as visited, distance 24/40, IsVisisted=False
[ExploreDungeonTag] New Nav Target: <161.25, 361.25, 0>
[ExploreDungeonTag] Marking nearby node <161.25, 361.25, 0> as visited, distance 39/40, IsVisisted=False
[ExploreDungeonTag] New Nav Target: <181.25, 361.25, 0>
[ExploreDungeonTag] Marking nearby node <181.25, 361.25, 0> as visited, distance 38/40, IsVisisted=False
[ExploreDungeonTag] New Nav Target: <161.25, 336.25, 0>
[ExploreDungeonTag] Marking nearby node <161.25, 336.25, 0> as visited, distance 40/40, IsVisisted=False
[ExploreDungeonTag] New Nav Target: <161.25, 286.25, 0>
[ExploreDungeonTag] New Nav Target: <161.25, 211.25, 0>
[ExploreDungeonTag] Marking nearby node <161.25, 211.25, 0> as visited, distance 40/40, IsVisisted=False
[ExploreDungeonTag] New Nav Target: <181.25, 211.25, 0>
[ExploreDungeonTag] New Nav Target: <181.25, 186.25, 0>
[ExploreDungeonTag] Marking nearby node <161.25, 186.25, 0> as visited, distance 40/40, IsVisisted=False
[ExploreDungeonTag] New Nav Target: <161.25, 161.25, 0>
[ExploreDungeonTag] Marking nearby node <161.25, 161.25, 0> as visited, distance 39/40, IsVisisted=False
[ExploreDungeonTag] New Nav Target: <186.25, 161.25, 0>
[ExploreDungeonTag] Marking nearby node <186.25, 161.25, 0> as visited, distance 39/40, IsVisisted=False
[ExploreDungeonTag] Fully explored area! Tag Finished.
Loaded profile Rift Bot
ToggleTargeting, new values: Looting:True LootRadius:150 Combat:True KillRadius:80
Loaded profile Rift Bot Optimized Explore
ToggleTargeting, new values: Looting:True LootRadius:150 Combat:True KillRadius:80
[Rift Bot] Explore Aquaducts @ 10/40/0.2
[ExploreDungeonTag] ExploreDungeon Started
[ExploreDungeonTag] Marking nearby node <181.25, 211.25, 0> as visited, distance 34/40, IsVisisted=False
[ExploreDungeonTag] Marking nearby node <161.25, 211.25, 0> as visited, distance 32/40, IsVisisted=False
[ExploreDungeonTag] Marking nearby node <181.25, 186.25, 0> as visited, distance 15/40, IsVisisted=False
[ExploreDungeonTag] Marking nearby node <186.25, 161.25, 0> as visited, distance 27/40, IsVisisted=False
[ExploreDungeonTag] Marking nearby node <161.25, 161.25, 0> as visited, distance 20/40, IsVisisted=False
[ExploreDungeonTag] Marking nearby node <138.75, 158.75, 0> as visited, distance 36/40, IsVisisted=False
[ExploreDungeonTag] New Nav Target: <161.25, 286.25, 0>
[ExploreDungeonTag] Marking nearby node <181.25, 236.25, 0> as visited, distance 39/40, IsVisisted=False
[ExploreDungeonTag] Marking nearby node <181.25, 261.25, 0> as visited, distance 37/40, IsVisisted=False

Edit: attached the log file

 

[Tony]

How To: Attach your HB-DB log file [with pictures]

 

[fukuhoe]

Here you go!

 

[Oksehode]

Here you go!

I see you're using Quest Tools 2.0.82 with Rift Bot.

That means you're not using the recommended plugin versions that is included in the compilation pack.

Quest Tools have issues with how nodes are visited in any newer versions than 2.0.74.

Edit: The log you posted in your last post is also unrelated to your first post.

Edit 2: Sorry to intrude on this thread, but I saw what was causing your problem.