Dealing with adds #651
Comments
|
Gooday!
After i reading the following i have a hunch that you might be set your pet behaviour to I'm pretty sure that once you pull more then one target with your pet - accidental body pull even - once the primary target dies, your pet should target the next potential enemy as long as your pet behaviour is set to There's a GoapGoal for it called TargetPetTargetGoal, which is purposefully designed to take advantage of the As long as your character class properly extracted, and read by the backend, this Goal should be added. Let me know if the issue still persists. On the other hand, the following is unrelated to the original issue, however two things caught my eye and they might hinder you to have the expected experience with the project.
Such as [14:00:58:754 I] [GoapAgent ] New Plan= Parallel
[14:00:58:773 E] Index was outside the bounds of the array.
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Core.ActionBarCostReader.Update(IAddonDataProvider reader) in C:\Users\S\Documents\L\L\Core\Actionbar\ActionBarCostReader.cs:line 48
at Core.AddonReader.Update() in C:\Users\S\Documents\L\L\Core\Addon\AddonReader.cs:line 73
at Core.BotController.AddonThread() in C:\Users\S\Documents\L\L\Core\BotController.cs:line 156In the logs, i saw many negative numbers regarding the actions await times. Like Where you can see two elapsed milliseconds notice
You can think of it as like a cause and effect.
I could give you a few hints what you can look up like
|
|
Tyvm for the great answer! Pet is on defensive and he is fighting next mob while we are waiting. I did some changes to code where if our pet has a target and we dont, that we always assist pet, and that seems to work. I fixed the -5 offset aswell but doesnt seem to help. I also tried all the resolutions with different cell sizes. I also looked into the negative numbers and I tested it on 3 different computers they all have negative numbers, and my friend has the same on his computer (I didnt help him to set it up so he must have done exact same mistake). I tested with capping fps to 30, 60, 120 etc, I tried changing hertz and v-sync is also disabled. Im guessing the same bug makes us engage in pvp randomly aswell despite a strict "AllowPvP": false. [10:45:11:659 W] [TargetBlacklist ] (0,17035,MINO) is player or pet! We engage about 30% of enemy players. |
|
Gooday.
It would be great if you could share the mentioned changes in a PR or just sending a diff about the specific changes, it would help a project a lot.
In the past, i've seen user logs who had similar negative numbers, however i was yet to figure out what would case it. Personally i have never seen such issue, i mean the volume of it, it may happens once of twice but not that consistency what your log presented.
So you are trying to tell me that, even tho the |
|
CombatGoal.zip
Yes exactly :P We actively engage in pvp. This happens to my friend aswell he added players to the blacklist for a mega scuffed fix. |
If you were kind enough to provide logs where the mentioned issue exists, i might be able to see what went wrong, thanks! |
|
The above log is from when we engaged a player;
I will save a full log for next time I see him engage in pvp. |
Description
Wondering what im doing wrong, if my pet pulls 2 mobs we just stand and wait for pet to die or mob to die before we continue.
[13:46:36:496 I] [GoapAgent ] Kill credit detected! Session Total: 7 | Last Combat: 1 | Currently fighting: 1
[13:46:36:529 I] [CombatGoal ] Lost target!
[13:46:36:544 W] [GoapAgent ] New Plan= NO PLAN
I have
Assist Target -> F by default is game settings
Target Pet -> Numpad Multiply has to setup manually
Pet Attack -> Numpad Subtract has to setup manually
This works as if I stop targeting the current target im fighting he retargets via pet instantly.
Gone over the settings many times but im not getting any feedback of what we are trying to do, so im not sure whats happening.
Addon Version
1.7.60
World of Warcraft Client
World of Warcraft Classic
Reproduction Steps
Pull a mob, then pull another, kill first mob, then we know the second target exists but we have no plan.
Last Good Version
No response
Screenshots
No response
Logs
headless_out20241231_003.log
The text was updated successfully, but these errors were encountered: