azerothcore-wotlk
azerothcore-wotlk copied to clipboard
azerothcore
fix(DB/Karazhan): Skeletal Usher - Ice Tomb's target
Issues Addressed:
- Closes https://github.com/chromiecraft/chromiecraft/issues/4866
- Closes #16031
How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].
You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).
For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.
The issue I had with this and why I didn’t address it before is that the report says they should pick another target if the main target is frozen, I’m not sure if that’s achievable with SAI
The issue I had with this and why I didn’t address it before is that the report says they should pick another target if the main target is frozen, I’m not sure if that’s achievable with SAI
( edit: btw didn't see the "assigned", totally missed it. )
What I've read from comments is how to "cheat" them by let the tanks go first, build aggro - get Ice Tomb'ed then go dps 'till death (don't see a "fixate" target mechanic like in other instances). Some comments also mention Tank and Off-Tank strat for the main to get ice tomb'ed and Off-Tank to retake it (without any DPS dealing damage).
source: https://www.wowhead.com/wotlk/npc=16471/skeletal-usher#comments:id=2828611
source: https://www.wowhead.com/wotlk/npc=16471/skeletal-usher#comments:id=138953
🤔❓
SAI_1 = Cast Ice Tomb on highest target SAI_2 = aggroReset on target with Ice_Tomb_Aura so by default behaviour the NPC will turn to the second highestAggro
There's a lot of creatures that changes targets based on the victims status. Conflagration and CONFUSE statuses, for example, always puts the affected player at the bottom of the threat list. I've seen it sometimes with STUN auras as well, which is the case here. I think it's more of an core AI issue than SAI one.
There's a lot of creatures that changes targets based on the victims status. Conflagration and CONFUSE statuses, for example, always puts the affected player at the bottom of the threat list. I've seen it sometimes with STUN auras as well, which is the case here. I think it's more of an core AI issue than SAI one.
Hmm, that seems a reasonable point, closing this and you file the issue as Core Generic? or do we all agree this is a good "partial" fix to at least make 50% of the mechanic?
Merge it then consider doing a script for it in karazhan.cpp in the future :))))
