Just started botting again and I must say it seems the movement logic has regressed instead of improving over the last 2 months from when I stopped. I'm running 2.41.60 from the svn and after watching it go for the last 2 hours here's a few movement related problems I've noticed.
*The environment interaction logic really loves face fucking doors. Never had this issue last season. Not sure if doors are heavily weighted but this version wants to click on every door. I've seen the bot revert backwards into an already explored path just to click a door then go back to the node it was on then continue on its way. Unless the door in question is on it's current path the bot shouldn't divert just to open and interact with it.
*Bot isn't close enough to interact with door and just sits there trying to open it from a distance. Doesn't happen all the time but frequently enough where it could be a logic issue. Thought this was more due to lag at first but I noticed it was more of a frequent problem with classes with a teleport ability.
*Destructible path object behind a door causes loop. This is a fun one. When a destructible path object like a barricade is located a few yards behind a closed door, instead of opening the door first it will target the barricade which it can't reach and bot will sit there trying to swipe at the barricade.
I think the door interaction should be looked at a bit further as soon as possible. It's not class specific skill, it's game based movement that applies to all classes which really hinders ability of bot to progress at a higher level imo, so should get immediate attention if possible.
Unrelated to doors, I've noticed an issue with Archon wizard and some schizophrenic teleporting. When soloing with a follower often times there are 1 or 2 mobs left from a cluster that the follower is beating on, it seems like the bot is fighting between two conditions causing a loop, it wants to move on searching for a new cluster but then it teleports back to the follower who's engaged in combat on a trash mob, it doesn't do anything but teleport between those two points back and forth.
Going to do some research this weekend looking at source code and making some modifications but thought I'd put this here in case it was already a known issue or being worked on.
*The environment interaction logic really loves face fucking doors. Never had this issue last season. Not sure if doors are heavily weighted but this version wants to click on every door. I've seen the bot revert backwards into an already explored path just to click a door then go back to the node it was on then continue on its way. Unless the door in question is on it's current path the bot shouldn't divert just to open and interact with it.
*Bot isn't close enough to interact with door and just sits there trying to open it from a distance. Doesn't happen all the time but frequently enough where it could be a logic issue. Thought this was more due to lag at first but I noticed it was more of a frequent problem with classes with a teleport ability.
*Destructible path object behind a door causes loop. This is a fun one. When a destructible path object like a barricade is located a few yards behind a closed door, instead of opening the door first it will target the barricade which it can't reach and bot will sit there trying to swipe at the barricade.
I think the door interaction should be looked at a bit further as soon as possible. It's not class specific skill, it's game based movement that applies to all classes which really hinders ability of bot to progress at a higher level imo, so should get immediate attention if possible.
Unrelated to doors, I've noticed an issue with Archon wizard and some schizophrenic teleporting. When soloing with a follower often times there are 1 or 2 mobs left from a cluster that the follower is beating on, it seems like the bot is fighting between two conditions causing a loop, it wants to move on searching for a new cluster but then it teleports back to the follower who's engaged in combat on a trash mob, it doesn't do anything but teleport between those two points back and forth.
Going to do some research this weekend looking at source code and making some modifications but thought I'd put this here in case it was already a known issue or being worked on.