You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This code states they should focus marked targets in combat: https://github.com/vmangos/core/blob/development/src/game/PlayerBots/PartyBotAI.cpp#L373
What they do is will focus the target of the party leader or whatever is hitting them or a target at random completely(?). Most of the time it seems to be the party leader's target upon first engage. They never switch targets until their current target is dead, but the code makes it look like they should change target and go to the marked target then stick on it the entire time in combat, but the don't.
Expected behavior
Mark a target, party bots focus it no matter what. Is not the the case.
Steps to reproduce
Spawn a dps partybot
mark a target
engage something not the marked target
watch as the bots not swap to the marked target until their first target is dead
Profit
Version & Environment
Client Version: 1.12.1
Commit Hash: newest
OS Client: win10
OS Server: win10
Crashlog
None
The text was updated successfully, but these errors were encountered:
🐛 Bug report
This code states they should focus marked targets in combat:
https://github.com/vmangos/core/blob/development/src/game/PlayerBots/PartyBotAI.cpp#L373
What they do is will focus the target of the party leader or whatever is hitting them or a target at random completely(?). Most of the time it seems to be the party leader's target upon first engage. They never switch targets until their current target is dead, but the code makes it look like they should change target and go to the marked target then stick on it the entire time in combat, but the don't.
Expected behavior
Mark a target, party bots focus it no matter what. Is not the the case.
Steps to reproduce
Version & Environment
Client Version: 1.12.1
Commit Hash: newest
OS Client: win10
OS Server: win10
Crashlog
The text was updated successfully, but these errors were encountered: