-
-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not responding to adds behind the character #570
Comments
Did the character were idle for 20 seconds ?
I will do some tests today on the PTR.
No plan means that for the given situation there was no suitable Goal to execute, during that time the player character either idle. |
Correct, the malachite + turning too fast was my looting followed by the correction. |
Today did some extensive testing, i had an issue during my character was using Wand, for some reason the player just wasn't faced to the target. Not sure how to fully tackle the issue as i have yet to found a 100% repro case. :( |
Hi, If you set "Skin" to "True" it will quite often spam skin the initial mob while getting constantly interupted by the second mob. I'm not sure if this is something you can fix, I can try to more provide logs if you need them as the repro rate, for me at least, is reasonably high in denser areas. The issue seems to happen around line 113. |
Thanks for the feedback i will look into it, in the upcoming days! |
Downloaded the new version of the bot and tested, still happening. Thanks for trying. |
Potential fix was supplied with #639 |
Description
When botting, I'm occasionally taking aggro from adds which are placed behind my character.
When this happens, the character pauses indefinitely as if waiting to leave combat.
In the logs attached, this happened at the end of the log. I manually targeted the add and resolved the conflict before ending the bot.
Addon Version
Unknown
World of Warcraft Client
The Burning Crusade Classic
Reproduction Steps
Bot until you experience an aggro from behind.
Last Good Version
No response
Screenshots
No response
Logs
out2024_0215_001.log
The text was updated successfully, but these errors were encountered: