Threat System Issues

[balleny]

Current Behaviour

Threat system - or implementation of all raid bosses - has a major issue.
abilities that should cause a npc to attack a different target, although lower on threat table (e.g. boss polymorphs chromiecraft/chromiecraft#1 in threat and attacks #2 in threat), result in bosses leaving combat / resetting if all targets are affected by an ability that causes these change in attackable targets.

Expected Blizzlike Behaviour

if all targets are affected by an ability which causes the npc to de-prioritize, it should pick the target according to regular threat table and actually break this CC - or in case of an scripted RP, continue with that instead of resetting and leaving combat.

Source

retail & logic

Steps to reproduce the problem

this issue happens e.g. at Maiden in Kara or Aran in Kara. where repentance and polymorph respectively, can cause every target of the threat table to be temporarily crowd controlled. instead of breaking the highest target according to regular threat table then, the boss currently resets.

Extra Notes

this is a generic issue and not boss specific.

AC rev. hash/commit

chromiecraft@c863a8c

Operating system

ubuntu

Custom changes or Modules

Chromiecraft

[balleny]

see also chromiecraft/chromiecraft#6392 for a concrete example