740, bot suddenly hangs

[AllanonHIK]

8 Minutes into perfect run, just stopped:

POI set to Type: None, Location: {0, 0}, Distance: 799, Name: None, Hash Code: 1043865467
POI set to Type: Chest, Location: {601, 578}, Distance: 39, Name: Chest, Hash Code: -873652357
MoveToCoroutine moving to {601, 578}. Reason: Interacting with POI: Open Chest
Navigation path index moved to 1
Pressing bound movement button.
Navigation path index moved to 2
Navigation path index moved to 3

Compeltely dead in the water. If you click somewhere for the bot, it suddenly snaps back to life. It may or may not freeze again, click again if it does and it moves again. Really weird.

Edit more info: Happening in hardcore normal docks, marauder.

Continued... here's another loop it got into when hanging:

avigation path index moved to 8
POI set to Type: Explore, Location: {273, 843}, Distance: 127, Name: Explore, Hash Code: -681192750
MoveToCoroutine moving to {273, 843}. Reason: Exploration
POI set to Type: Explore, Location: {298, 804}, Distance: 87, Name: Explore, Hash Code: -1011982720
MoveToCoroutine moving to {298, 804}. Reason: Exploration
POI set to Type: Explore, Location: {298, 802}, Distance: 86, Name: Explore, Hash Code: 2067841600
MoveToCoroutine moving to {298, 802}. Reason: Exploration
POI set to Type: Explore, Location: {298, 799}, Distance: 86, Name: Explore, Hash Code: -653784795
MoveToCoroutine moving to {298, 799}. Reason: Exploration
POI set to Type: Explore, Location: {298, 796}, Distance: 85, Name: Explore, Hash Code: -200707571
MoveToCoroutine moving to {298, 796}. Reason: Exploration
POI set to Type: Explore, Location: {298, 793}, Distance: 84, Name: Explore, Hash Code: 1758538058
MoveToCoroutine moving to {298, 793}. Reason: Exploration
POI set to Type: Explore, Location: {300, 791}, Distance: 82, Name: Explore, Hash Code: -2082326827
MoveToCoroutine moving to {300, 791}. Reason: Exploration
POI set to Type: Explore, Location: {302, 789}, Distance: 80, Name: Explore, Hash Code: 1276632190
MoveToCoroutine moving to {302, 789}. Reason: Exploration
POI set to Type: Explore, Location: {304, 788}, Distance: 77, Name: Explore, Hash Code: -1636531250
MoveToCoroutine moving to {304, 788}. Reason: Exploration
POI set to Type: Explore, Location: {306, 787}, Distance: 75, Name: Explore, Hash Code: 761759749
MoveToCoroutine moving to {306, 787}. Reason: Exploration
POI set to Type: Explore, Location: {309, 785}, Distance: 72, Name: Explore, Hash Code: -641869269
MoveToCoroutine moving to {309, 785}. Reason: Exploration
POI set to Type: Explore, Location: {311, 784}, Distance: 70, Name: Explore, Hash Code: 1988650437
MoveToCoroutine moving to {311, 784}. Reason: Exploration
POI set to Type: Explore, Location: {314, 782}, Distance: 67, Name: Explore, Hash Code: 397097246
MoveToCoroutine moving to {314, 782}. Reason: Exploration
POI set to Type: Explore, Location: {314, 780}, Distance: 67, Name: Explore, Hash Code: -937514375
MoveToCoroutine moving to {314, 780}. Reason: Exploration
POI set to Type: Explore, Location: {312, 779}, Distance: 69, Name: Explore, Hash Code: 1871816908
MoveToCoroutine moving to {312, 779}. Reason: Exploration
POI set to Type: Explore, Location: {309, 777}, Distance: 72, Name: Explore, Hash Code: 1557457068
MoveToCoroutine moving to {309, 777}. Reason: Exploration
POI set to Type: Explore, Location: {307, 776}, Distance: 74, Name: Explore, Hash Code: -534379929
MoveToCoroutine moving to {307, 776}. Reason: Exploration
POI set to Type: Explore, Location: {305, 775}, Distance: 76, Name: Explore, Hash Code: 200969312
MoveToCoroutine moving to {305, 775}. Reason: Exploration
POI set to Type: Explore, Location: {302, 773}, Distance: 79, Name: Explore, Hash Code: -1197066817
MoveToCoroutine moving to {302, 773}. Reason: Exploration
POI set to Type: Explore, Location: {300, 772}, Distance: 81, Name: Explore, Hash Code: 414183658
MoveToCoroutine moving to {300, 772}. Reason: Exploration
POI set to Type: Explore, Location: {298, 771}, Distance: 83, Name: Explore, Hash Code: 680712691
MoveToCoroutine moving to {298, 771}. Reason: Exploration
POI set to Type: Explore, Location: {295, 769}, Distance: 86, Name: Explore, Hash Code: 1463420097
MoveToCoroutine moving to {295, 769}. Reason: Exploration
POI set to Type: Explore, Location: {293, 768}, Distance: 88, Name: Explore, Hash Code: -1996677504
MoveToCoroutine moving to {293, 768}. Reason: Exploration
POI set to Type: Explore, Location: {290, 766}, Distance: 91, Name: Explore, Hash Code: 1387646190
MoveToCoroutine moving to {290, 766}. Reason: Exploration
POI set to Type: Explore, Location: {288, 765}, Distance: 93, Name: Explore, Hash Code: 118792472
MoveToCoroutine moving to {288, 765}. Reason: Exploration
POI set to Type: Explore, Location: {286, 764}, Distance: 95, Name: Explore, Hash Code: 447799738
MoveToCoroutine moving to {286, 764}. Reason: Exploration
POI set to Type: Explore, Location: {283, 762}, Distance: 98, Name: Explore, Hash Code: 82518058
MoveToCoroutine moving to {283, 762}. Reason: Exploration
POI set to Type: Explore, Location: {281, 761}, Distance: 101, Name: Explore, Hash Code: 879863917
MoveToCoroutine moving to {281, 761}. Reason: Exploration
POI set to Type: Explore, Location: {283, 761}, Distance: 99, Name: Explore, Hash Code: -1143149546
MoveToCoroutine moving to {283, 761}. Reason: Exploration
POI set to Type: Explore, Location: {286, 762}, Distance: 96, Name: Explore, Hash Code: -1332275054
MoveToCoroutine moving to {286, 762}. Reason: Exploration
POI set to Type: Explore, Location: {289, 762}, Distance: 93, Name: Explore, Hash Code: 324920873
MoveToCoroutine moving to {289, 762}. Reason: Exploration
POI set to Type: Explore, Location: {291, 762}, Distance: 91, Name: Explore, Hash Code: -819698722
MoveToCoroutine moving to {291, 762}. Reason: Exploration
POI set to Type: Explore, Location: {294, 763}, Distance: 87, Name: Explore, Hash Code: -1100239463
MoveToCoroutine moving to {294, 763}. Reason: Exploration
POI set to Type: Explore, Location: {297, 763}, Distance: 85, Name: Explore, Hash Code: 1233529827
MoveToCoroutine moving to {297, 763}. Reason: Exploration
POI set to Type: Explore, Location: {300, 764}, Distance: 81, Name: Explore, Hash Code: -851186874
MoveToCoroutine moving to {300, 764}. Reason: Exploration
POI set to Type: Explore, Location: {302, 764}, Distance: 79, Name: Explore, Hash Code: 1442530850
MoveToCoroutine moving to {302, 764}. Reason: Exploration
POI set to Type: Explore, Location: {300, 763}, Distance: 82, Name: Explore, Hash Code: 1118345891
MoveToCoroutine moving to {300, 763}. Reason: Exploration
POI set to Type: Explore, Location: {297, 761}, Distance: 85, Name: Explore, Hash Code: -1462250704
MoveToCoroutine moving to {297, 761}. Reason: Exploration
POI set to Type: Explore, Location: {295, 759}, Distance: 87, Name: Explore, Hash Code: 2009059204
MoveToCoroutine moving to {295, 759}. Reason: Exploration
POI set to Type: Explore, Location: {293, 758}, Distance: 89, Name: Explore, Hash Code: -1036314110
MoveToCoroutine moving to {293, 758}. Reason: Exploration
POI set to Type: Explore, Location: {290, 756}, Distance: 93, Name: Explore, Hash Code: 363671636
MoveToCoroutine moving to {290, 756}. Reason: Exploration
POI set to Type: Explore, Location: {288, 755}, Distance: 95, Name: Explore, Hash Code: 107406682
MoveToCoroutine moving to {288, 755}. Reason: Exploration
POI set to Type: Explore, Location: {286, 754}, Distance: 97, Name: Explore, Hash Code: -767883075
MoveToCoroutine moving to {286, 754}. Reason: Exploration
POI set to Type: Explore, Location: {283, 752}, Distance: 100, Name: Explore, Hash Code: -536328582
MoveToCoroutine moving to {283, 752}. Reason: Exploration
POI set to Type: Explore, Location: {281, 750}, Distance: 103, Name: Explore, Hash Code: -180410936
MoveToCoroutine moving to {281, 750}. Reason: Exploration
POI set to Type: Explore, Location: {278, 748}, Distance: 106, Name: Explore, Hash Code: -36056511
MoveToCoroutine moving to {278, 748}. Reason: Exploration
POI set to Type: Explore, Location: {276, 747}, Distance: 108, Name: Explore, Hash Code: 481579312
MoveToCoroutine moving to {276, 747}. Reason: Exploration
POI set to Type: Explore, Location: {274, 746}, Distance: 111, Name: Explore, Hash Code: 213298476
MoveToCoroutine moving to {274, 746}. Reason: Exploration
POI set to Type: Explore, Location: {271, 744}, Distance: 114, Name: Explore, Hash Code: -554609577
MoveToCoroutine moving to {271, 744}. Reason: Exploration
POI set to Type: Explore, Location: {269, 743}, Distance: 116, Name: Explore, Hash Code: 639690711
MoveToCoroutine moving to {269, 743}. Reason: Exploration
POI set to Type: Explore, Location: {267, 741}, Distance: 119, Name: Explore, Hash Code: -956388726
MoveToCoroutine moving to {267, 741}. Reason: Exploration
POI set to Type: Explore, Location: {264, 740}, Distance: 122, Name: Explore, Hash Code: -1298254233
MoveToCoroutine moving to {264, 740}. Reason: Exploration
POI set to Type: Explore, Location: {261, 740}, Distance: 125, Name: Explore, Hash Code: -1047762823
MoveToCoroutine moving to {261, 740}. Reason: Exploration
POI set to Type: Explore, Location: {259, 740}, Distance: 127, Name: Explore, Hash Code: -90627679
MoveToCoroutine moving to {259, 740}. Reason: Exploration
POI set to Type: Explore, Location: {258, 740}, Distance: 128, Name: Explore, Hash Code: -1507458338
MoveToCoroutine moving to {258, 740}. Reason: Exploration
POI set to Type: Explore, Location: {259, 740}, Distance: 127, Name: Explore, Hash Code: 1730929749
MoveToCoroutine moving to {259, 740}. Reason: Exploration
POI set to Type: Explore, Location: {262, 740}, Distance: 124, Name: Explore, Hash Code: -613838199
MoveToCoroutine moving to {262, 740}. Reason: Exploration
POI set to Type: Explore, Location: {264, 740}, Distance: 122, Name: Explore, Hash Code: -1980385585
MoveToCoroutine moving to {264, 740}. Reason: Exploration
POI set to Type: Explore, Location: {267, 741}, Distance: 119, Name: Explore, Hash Code: 650831187
MoveToCoroutine moving to {267, 741}. Reason: Exploration
POI set to Type: Explore, Location: {269, 742}, Distance: 117, Name: Explore, Hash Code: -1055028084
MoveToCoroutine moving to {269, 742}. Reason: Exploration
POI set to Type: Explore, Location: {272, 744}, Distance: 113, Name: Explore, Hash Code: -1264766125
MoveToCoroutine moving to {272, 744}. Reason: Exploration
POI set to Type: Explore, Location: {273, 744}, Distance: 112, Name: Explore, Hash Code: -1248176040
MoveToCoroutine moving to {273, 744}. Reason: Exploration
POI set to Type: Explore, Location: {272, 746}, Distance: 113, Name: Explore, Hash Code: 997251319
MoveToCoroutine moving to {272, 746}. Reason: Exploration
POI set to Type: Explore, Location: {271, 748}, Distance: 113, Name: Explore, Hash Code: -898160868
MoveToCoroutine moving to {271, 748}. Reason: Exploration
POI set to Type: Explore, Location: {269, 751}, Distance: 114, Name: Explore, Hash Code: -1627879262
MoveToCoroutine moving to {269, 751}. Reason: Exploration
POI set to Type: Explore, Location: {268, 753}, Distance: 115, Name: Explore, Hash Code: 1520051533
MoveToCoroutine moving to {268, 753}. Reason: Exploration
POI set to Type: Explore, Location: {267, 755}, Distance: 115, Name: Explore, Hash Code: -864557148
MoveToCoroutine moving to {267, 755}. Reason: Exploration
POI set to Type: Explore, Location: {265, 758}, Distance: 117, Name: Explore, Hash Code: 1860720920
MoveToCoroutine moving to {265, 758}. Reason: Exploration
POI set to Type: Explore, Location: {264, 760}, Distance: 118, Name: Explore, Hash Code: 1121551611
MoveToCoroutine moving to {264, 760}. Reason: Exploration
POI set to Type: Explore, Location: {262, 763}, Distance: 119, Name: Explore, Hash Code: -1720078999
MoveToCoroutine moving to {262, 763}. Reason: Exploration
POI set to Type: Explore, Location: {263, 763}, Distance: 118, Name: Explore, Hash Code: -1253150890
MoveToCoroutine moving to {263, 763}. Reason: Exploration
POI set to Type: Explore, Location: {265, 764}, Distance: 116, Name: Explore, Hash Code: 1319565178
MoveToCoroutine moving to {265, 764}. Reason: Exploration
POI set to Type: Explore, Location: {268, 766}, Distance: 113, Name: Explore, Hash Code: 1908320815
MoveToCoroutine moving to {268, 766}. Reason: Exploration
POI set to Type: Explore, Location: {269, 766}, Distance: 112, Name: Explore, Hash Code: 1256637795
MoveToCoroutine moving to {269, 766}. Reason: Exploration
POI set to Type: Explore, Location: {267, 768}, Distance: 114, Name: Explore, Hash Code: 1340704178
MoveToCoroutine moving to {267, 768}. Reason: Exploration
POI set to Type: Explore, Location: {265, 769}, Distance: 116, Name: Explore, Hash Code: 899101166
MoveToCoroutine moving to {265, 769}. Reason: Exploration
POI set to Type: Explore, Location: {263, 771}, Distance: 118, Name: Explore, Hash Code: -1410566422
MoveToCoroutine moving to {263, 771}. Reason: Exploration
POI set to Type: Explore, Location: {262, 772}, Distance: 119, Name: Explore, Hash Code: -2000794146
MoveToCoroutine moving to {262, 772}. Reason: Exploration
POI set to Type: Explore, Location: {262, 774}, Distance: 119, Name: Explore, Hash Code: 761625299
MoveToCoroutine moving to {262, 774}. Reason: Exploration
POI set to Type: Explore, Location: {262, 777}, Distance: 119, Name: Explore, Hash Code: 1336230597
MoveToCoroutine moving to {262, 777}. Reason: Exploration
POI set to Type: Explore, Location: {261, 780}, Distance: 120, Name: Explore, Hash Code: -290670737
MoveToCoroutine moving to {261, 780}. Reason: Exploration
POI set to Type: Explore, Location: {261, 782}, Distance: 120, Name: Explore, Hash Code: 126015578
MoveToCoroutine moving to {261, 782}. Reason: Exploration

 

[AllanonHIK]

Just hung again trying to attack a chest, but after a minute or so it unhung and continued. Couple runs in, doesnt seem to be acting up but i've limited instance time to ensure it will give up if it does get stuck. How do we utilize the setting in the config for max instance explore, i've changed it in the config but bot doesn't recognize it, cant find it in gui.

Just caught it hung again after a few flawless runs. It was stuck until max instance was hit. At least it continues fine after that.

Very next instance the bot ran in between these two objects:

View image: screen

The bot tries to click on each barrel between those two objects, for whatever reason it fails to hit each one, gives up on trying to do that and then decides to walk away but it is permanently stuck. Its just hammering movement button right now which has gotta be pretty detectable for GGG.

 

[eendaen]

Just hung again trying to attack a chest, but after a minute or so it unhung and continued. Couple runs in, doesnt seem to be acting up but i've limited instance time to ensure it will give up if it does get stuck. How do we utilize the setting in the config for max instance explore, i've changed it in the config but bot doesn't recognize it, cant find it in gui.

Just caught it hung again after a few flawless runs. It was stuck until max instance was hit. At least it continues fine after that.

Very next instance the bot ran in between these two objects:

View image: screen

The bot tries to click on each barrel between those two objects, for whatever reason it fails to hit each one, gives up on trying to do that and then decides to walk away but it is permanently stuck. Its just hammering movement button right now which has gotta be pretty detectable for GGG.

I'm having the same issue currently. Sometimes it just gets randomly stuck at barrels aswell. Hopefully it is fixed soon.

 

[pushedx]

One of the random hangs is related to the current pathfinding bug where the library we're using ends up processing what seems to be bad data of the current level. This is a really tough issue, because we want to use the library, but it seems either the data that is being generated to feed to it is either wrong, or there is some unknown bug that is causing it to mess up during the update cycle. Since the levels are randomly generated, and the issue seems to randomly happen, we're not sure how to fix it. We're going to be trying to change the data generation routine, but actually knowing if it's fixed or not is going to be something that will take a lot of time and testing.

From time to time, we've noticed the issue where the bot stops, and clicking on the window brings it back to life. It happens infrequently, but still randomly enough time to time to think it's an issue. It might be related to the game client dropping all input messages when not in focus, but we're not sure why. I've not actually noticed that bug in a while now, so not sure what triggers it. The input stuff will be rewritten some, but we're really limited to how we can interact with the client. We can't directly make it move to any location we want to perform a specific action. That might mean, that issue can pop up time to time.

For the chests stuck issue, was it trying to move through the chests or around them but got stuck in the corner of the box? If it was trying to move through the chests, that's another pathfinding issue we have to solve when it comes to being able to knock over chests that are in the way. In most cases, the client walks you around, but in the case where it's trying to travel through a narrow area, it could get stuck like that. I don't think it's related to the new movement change just made, but I'll retest Docks to see if it pops up more now. There is an issue where the pathfinding is using too small of a size to calculate the paths, so the bot will try to go through too narrow walls time to time (Crypt shows this quite often). We'll be tweaking the settings to try and avoid that in the future.

Lastly, for exploration, some of the settings in the config are no longer applicable to the bot. What happened with the last rewrite was a bunch of code was changed, which the GB7 is the rewritten bot, but we didn't remove all the old code or even some of the gui options yet. That gui is not the long term gui EB will have. Right now it's something that mostly works, but it does have its issues. Updating it is still on the todo list, but it's mentioned on the main revision page.

 

[eendaen]

Yes, it act's like it's trying to pass thru the barrels or chests. I also noticed that sometimes it would hang right after saying it was trying to use a quicksilver flask.

 

[pushedx]

Do you guys have a skill assigned to break chests?

I'll double check the Quicksilver usage, but so far in my testing docks (on my 3rd run atm), I've not come across any new issues. It's possible they are just random bot bugs (that always could happen, just rarely did) and not actually from anything that changed. There are a few things that can happen in Docks that breaks the bot. However, they cannot be handled generically. I've mentioned this in other posts, but I think we need to have more area specific logic to handle the things that happen in this game.

One thing I have noticed about Docks for a while now is the desync is much higher or more noticeable than most other areas. The next time the bot is stuck on a wall or the terrain, stop the bot, and /oos to see if your character moves. There's some minor desync issues that can happen that really hurt the bot because of the "dead zone" when moving on the server. The main fix for this, is to really just do random clicking time to time, but in a way that the bot treats it as a task, and not just randomly clicks the screen so it doesn't interfere with the rest of the code. That would be part of the anti-stuck stuff that will be added along with the random idle timers to try and prevent the case of the bot just sitting around and doing the same thing.

I'll still be testing this though to be sure, but I think most of the issues you are seeing are just normal bot bugs. The random level generation is one of the reasons why the bot can work flawlessly sometimes, and other times it just sucks. There's not too much we can do about that though, other than just trying to handle each tileset as best we can.

 

[eendaen]

Do you guys have a skill assigned to break chests?

I'll double check the Quicksilver usage, but so far in my testing docks (on my 3rd run atm), I've not come across any new issues. It's possible they are just random bot bugs (that always could happen, just rarely did) and not actually from anything that changed. There are a few things that can happen in Docks that breaks the bot. However, they cannot be handled generically. I've mentioned this in other posts, but I think we need to have more area specific logic to handle the things that happen in this game.

One thing I have noticed about Docks for a while now is the desync is much higher or more noticeable than most other areas. The next time the bot is stuck on a wall or the terrain, stop the bot, and /oos to see if your character moves. There's some minor desync issues that can happen that really hurt the bot because of the "dead zone" when moving on the server. The main fix for this, is to really just do random clicking time to time, but in a way that the bot treats it as a task, and not just randomly clicks the screen so it doesn't interfere with the rest of the code. That would be part of the anti-stuck stuff that will be added along with the random idle timers to try and prevent the case of the bot just sitting around and doing the same thing.

I'll still be testing this though to be sure, but I think most of the issues you are seeing are just normal bot bugs. The random level generation is one of the reasons why the bot can work flawlessly sometimes, and other times it just sucks. There's not too much we can do about that though, other than just trying to handle each tileset as best we can.

I do use the abilities they use for fighting to break chests, which are Dual Strike on one and Ground Slam on 5 others, 4 of these bots are experiencing the same hangs in southern forest which is where they are now. Most of the time when it hangs it happens to be near stairs for some reason. If there is any information I can get to you from my bot when it gets stuck let me know. I'm always babysitting them.

 

[pushedx]

About 6 runs in, I came across one of the stuck bugs: image

The bot is trying to move along the path under the stairs, but due to the height difference, it's trying to click on top of them. Since the pathfinding data is 2D, the bot doesn't handle this height discrepancy. I don't think I've seen this issue before when testing, but it would have always been there.

Edit: Never mind, the issue is totally different.

I do use the abilities they use for fighting to break chests, which are Dual Strike on one and Ground Slam on 5 others, 4 of these bots are experiencing the same hangs in southern forest which is where they are now. Most of the time when it hangs it happens to be near stairs for some reason. If there is any information I can get to you from my bot when it gets stuck let me know. I'm always babysitting them.

Can you send me a screenshot of a place where it gets stuck in Southern Forest? Or did you mean just areas with stairs?

 

[eendaen]

It's getting stuck right along these rocks.

 

[pushedx]

Ok thanks, that's part of the wall issue that we attempted to solve by making the pathfinder try to avoid walls, but in some cases, it's still getting too close to them.

 

[eendaen]

No problem. Hopefully it will get resolved sometime in the near future. It's still useable it's just slightly annoying working around it. But that's the point of beta anyways. It's worlds ahead of what it was a few months ago so I'm happy with not being banned instantly and I can actually make some profit now.

 

[pushedx]

Yea, pathfinding is one of the main cruxs right now.

The wall code we have to try and avoid those edges, ends up doing things like this in really tight spaces: https://www.dropbox.com/s/pdujhzrnbehto2o/2014-02-14_07-55-33.png The actual problem though, is a client issue. The height checking code returns the floor rather than the stairs, so the bot gets stuck on the stairs. I was just able to reproduce it playing normally.

I can fix one of the stuck issues in this thread, but in doing so, it would break the bot in a ton of other areas, which isn't really worth it.

We'll have to try and think up a better way to handle this, so for now, there's nothing you guys can really do in these areas other than help the bot when possible. Sorry!

Edit: Here's a video that shows exactly why the bot messes up at times on stairs. It's random things like this, that we end up finding when botting, because they are hidden when you play the game normally due to how much you move the mouse around.

 

[eendaen]

Ahh. I see how that could be causing these problems then. Would it be possible to add a check to regenerate pathing if it didn't move for x amount of time? Just something temporary until you guys can get a better fix.

I guess maybe in the mean time I should swap to the library or something. As I don't think there are many stairs to get stuck on there.

 

[AllanonHIK]

Just an update, I botted ALL night using 740 and completed "0 runs" ... lol it doesnt log runs that end cause of max instance time. It was still running when I woke up, it got a lot done over night. But it is definitely having issues hanging for sure.

Can you guys add the max instance explore to the gui?

 

[pushedx]

Ahh. I see how that could be causing these problems then. Would it be possible to add a check to regenerate pathing if it didn't move for x amount of time? Just something temporary until you guys can get a better fix.

I guess maybe in the mean time I should swap to the library or something. As I don't think there are many stairs to get stuck on there.

The bot does do that, but it does't solve the problem because the path it's trying to follow is the bad path in the client, which ends up getting re-calculated regardless.

The solution would have to be something along the lines of simulating more realistic human mouse movement rather than what a bot typically does. That way, the character is dragged over the terrain like when you play instead of trying to click to move to points.