Question - When a named isnt a named!

[Armyboxer99]

There are a number of mobs in the new expac, especially in Kael that have titles but are not named/rare mobs. Is there anyway of tagging these so that conditions designed for named mobs don't trigger?

 

[Sum1]

/burnallnamed=0

and update kissassist_info.ini with the namers in the expansion.

conditions are a different animal and need a different approach, obviously.

 

[Warl0ck45]

With my macros I put in a toggle for the named section so I can turn it off on the fly. MQ2Melee stuff... had to turn off the holyflags and depends on macro driven stuff. (I have a few duplicate to insure X thing fires)

 

[0ptic]

I'm not sure why in Kael but any mob with a name is considered a rare creature which triggers burns. What is MQ looking for in these cases? Is it possible to check for the "a rare creature" tag?

 

[Many_Whelps]

if it's name starts with a lowercase "a" it's not a named, if it's starts with anything else, including an uppercase "A", then ${Target.Named} will likely return True.