Areas with Stuck Issues Thread

[PalBuddy]

Because you can blacklist it yourself in MapRunner, it's in the GUI.

There's no reason to re-invent the wheel.

While I understand and respect your opinion and everything else you do for the community. For anyone new to botting they would have to read this thread and monitor the bot to pickup out the maps that get the bot stuck. Some of the non-native english speakers might have difficulties reading through pages of content. My point is that ExVault is already internally blacklisting some maps so why not add in these stuck maps as well? Is there a point to not having these maps black listed internally if they cause stuck issues? Since ExVault already had some maps blacklisted I didn't really see my suggestion as demanding the wheel be re-invented. But I am not by any means a coder like you guys; so maybe my suggestion was way too much work considering it would basically only help newer non-english botters.

 

[ExVault]

The reason behind that is simple:

I internally blacklisted 3 maps because MapRunner currently cannot properly navigate through them, it does not mean those maps have issues, they just require additional logic to be coded on my side. On the other hand, writing that logic does not really justify the time put in it: two maps are level 82 (nobody cares about them) and one level 71 map. So, I simply chose the "lazy" approach - blacklist them for good.

Problematic maps listed in this thread have nothing to do with MapRunner. They have issues with Pathfinder, which is the core part of the bot. I cannot "fix" them, or code "additional logic" for them. Thats why I did not internally blacklist them, their issues are not "maprunner-related". The proper solution here is to warn newcomers about them, so they can choose what to do, its the point of this thread.

 

[toNyx]

The reason behind that is simple:

I internally blacklisted 3 maps because MapRunner currently cannot properly navigate through them, it does not mean those maps have issues, they just require additional logic to be coded on my side. On the other hand, writing that logic does not really justify the time put in it: two maps are level 82 (nobody cares about them) and one level 71 map. So, I simply choose the "lazy" approach - blacklist them for good.

Problematic maps listed in this thread have nothing to do with MapRunner. They have issues with Pathfinder, which is the core part of the bot. I cannot "fix" them, or code "additional logic" for them. Thats why I did not internally blacklist them, their issues are not "maprunner-related". The proper solution here is to warn newcomers about them, so they can choose what to do, its the point of this thread.

^ This

Navigation issues have nothing to do with maprunner, and the fact that they could be resolved anytime soon would involve maprunner update to remove them. So No, as generic as possible.
You have the possibility to control the behavior, and that's it. Nothing specifically user-related is welcome.

 

[buddyfu2]

Area Name - Volcano Map
Stuck Type - The bot was stuck trying to walk between the edge of the map and an obstacle
Screenshot

Log

[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 229
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 187
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[LatencyTracker] AverageLatency: 36
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[LatencyTracker] HighestLatency: 57
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153
[TrackMobTask] Cached monster locations: 11
[TrackMobTask] Moving to the monster at {469, 763} distance: 153

 

[pushedx]

Thanks for all the reports guys! While I can't make any promises yet on immediate improvments for the expansion, I can say that from helping out wither another Buddy project, I now understand the pathfinding library we're using a lot better (and also have a new version for EB to use in the near future) and should be able to start actually solving some of these issues and put some better tools in place to understand why it happens in the future.

 

[Tattoo]

is their some complete list of maps we should ignore right now - or do i need to look at all the posts here?

 

[Tormiasz]

Due to changes in the bot itself some of the areas might be fixed already so I wouldn't put any list for now, this thread should be cleared and started from this day.

 

[Infinite Monkeys]

In future it'd be nice to have a list in the OP of recommended maps/boss rooms to skip. Not just stuck issues, but stuff like the Torture Chamber boss which the bot can't handle as well. It would be much easier for new users to read a list than dig through this thread, the stuck thread and the map boss difficulty wiki page trying to work it out.

 

[Tormiasz]

Why bot couldn't handle Torture Chamber boss? Just get build that kills.

 

[fisuska]

Bot gets stuck in Belly of the Beast level 2, after killing Piety the first time and going to harvest. When you return back to Beast L2 spawning a new session, there are spikes lifted up and Piety is behind there again. Spikes prevent you from passing thru there any further.

Spoiler