Hi,
Bobby53!
I don't know if this is beyond Singular's design goals or not, but thought I'd double-check. This example is from a Paladin, but the same situation happened when running Mages and Druids through the same scenario.
The Scenario:
While doring the
Breaking the Emperor's Shield quest, we are sent to kill
Nakk'rakas <The Spiritshaper>. As soon as you engage him, he pops a shield that makes him invulnerable, and summons an
Imperial Guard. You must kill the Imperial Guard before Nakk'rakas' shield will drop. Several times throughout the fight, he will pop his shield and become invulnerable, and summon another Imperial Guard.
The Problem:
Honorbuddy initially targets Nakk'rakas, and won't switch to killing the Imperial Guard when Nakk'rakas becomes invulnerable. Instead, Singular continues to attack Nakk'rakas until the encounter resets due to timeout (I assume--as the mobs just depopped after a while).
(Not shown in the log) If I manually target the Guardian each time, Singular spanks it good, and returns to Nakk'rakas.
Incidentals (may be helpful or not):
The shield raised by Nakk'rakas is called
Protection of Zian. The initial shield shows a stack count of 3. Each time he pops a new shield and summons a Guardian, the stack count on the shield is diminished by one.
Expectations:
I expected Singular to pick another target and spank it, if the current target cannot be touched. If this is not a Singular design goal, that's perfectly fine.
If this is just a quirky scenario, that's also fine. But, just wanted to make certain there wasn't a bigger problem in multi-target situations where a mob becomes invulnerable.
As always, the fact you are the Master of Singular makes me happier than bacon-wrapped cupcakes!