Dangerous BUG (high report chance)

[Alfred26]

Hello,
There is a waypoint error in "The Everbloom" dungeon of DungeonBuddy near to 62,52 coordinates.
The bug makes the tank character run towards a wall (trying to climb it) instead of rounding it, doing a really suspicious behavior, which drastically increases your chance to be reported and banned.
The way to fix this is too easy, just add a waypoint to let the bot surround the wall instead of trying to walk across it (it can take 5minutes to fix and save lots of reports)

Note: This bug only appear on the bot who is tanking. If you run dungeons with humans you will be reported, and if you go in a bot party, them all will be stopped when the tank gets stucked here.

 

[BotOperator]

Please attach a full un-edited logfile showing this issue.

 

[Alfred26]

I have a lot of logfiles and don't know in which of them is loged this bug... :/

Anyways, the way to recreate the bug its pretty simple, run DungeonBuddy on Everbloom (Draenor dungeon) with tank role and defaults HonorBuddy script. Then, let the bot lead the way and you will see that pathfinding/waypoint issue in less than 5minutes (when it reach that coordinates).
I think that this is because blizzard fixed some shortcuts on this dungeon in 6.1 and honorbuddy's script tries to follow the old path. (in previous patch you could avoid some pulls by climbing the wall, but now there is an invisible wall)

If you still needing logfiles, I will try to find the right file. But I think that will be easier for you to recreate it and see it by yourself. (seems that fixing it is as easy as adding a new waypoint to everbloom's script)

 

[Tony]

we would like to check your log file as well plz

 

[Alfred26]

Ok, I will clear my log folder and recreate the bug tonight (my log folder is 300mb size and don't know which file is)
How should I attach you those logs?

 

[Alfred26]

Here you have two logs (from two different accounts):
TANK: party leader (the one who gets stucked)
HEALER: party follower (gets inactive following the stucked tank)

We cleared log folder, before recreating the bug, so logs are clear and shows only from START (HonorBuddy -> DungeonBuddy -> Everbloom) to STOP (we stopped the bot to avoid reports cause we had pickups on the party)


In tank log you can see things like this:

Activity: Moving towards boss Witherbark
Applied blackspot for Main path to first boss
[...]
We are stuck!
Trying strafe forward left for 600ms
Generating new path because we are not on the old path anymore!
We are stuck!
Trying strafe forward right for 1000ms
Generating new path because we are not on the old path anymore!
We are stuck!

And it still endlessly, trying to walk through the wall to reach Witherbark boss. On a full bot party it was more than 2 hours trying to go through it (without sucess)

 

[Tony]

thx,we will check it asap!

 

[Alfred26]

thx,we will check it asap!

How is that going? there is an ETA?

 

[Tony]

clear your mesh folder and give it a try

but before you do this can you take note of the last write date for the ShaperDungeon_29_31 tile plz?
File should be in MeshFolder/ShaperDungeon/ShaperDungeon_29_31.etm

A screenshot of the file Properties>General tab would be fine

 

[Alfred26]

Where is that MeshFolder?
I've been looking for it on my HonorBuddy folder and coudnt find it :/

 

[CodenameG]

make a new folder inside your honorbuddy folder called "Meshes" then click "settings and tools" and change the mesh folder location to the new folder you just created.