Question - Better named detection

[Ordell]

I've been camping a named in ME in an area surrounded by those four armed mobs, all of which have names. So KA is firing off "is a NAMED!" with an endless string of named. This forced me to turn off Burn All Named in my inis and do it manually, among other things.

Is there any way to improve the smarts of KA so it recognizes these mobs as trash and not named?

 

[Knightly]

Move things you would use in Burn into DPS and use ${SpawnMaster.HasTarget} as your Condition.

 

[Sic]

you can use mq2spawnmaster and the tlo

knightly beat me heh

 

[DallasAg]

So, I've been playing around with using mq2spawnmaster and ${SpawnMaster.HasTarget} to help with Named recognition while playing in ToL.

It's going ok but I do have a question. I've moved my burn section to DPS (with conditions) and I now have a DPS size of 48. Should I put my burn items towards the top of the DPS section since I'm using DPSon=2... or does it matter?

 

[knave23]

Totally making this up, but could you turn off burnAllNamed and then have your spawnmaster condition just call the KA /burn command? Seems like it would save a lot of ini rework, but I don't know if it would actually work.

 

[DallasAg]

My burn section looks like this:

[[Burn]
BurnSize=3
BurnAllNamed=1
Burn1=NULL
Burn2=NULL
Burn3=NULL
BurnText=Burn
UseTribute=0

So I can toggle BurnAllNamed off and on when needed. When I engage a Named mob, I use this condition:

Cond24=${SpawnMaster.HasTarget}.

Not sure if there is another way but this has worked. I'm just wondering if KA would fire off the burn condition faster if I moved up the DPS# with this condition to the top of the DPS list.

 

[Knightly]

The order happens for DPSOn=2 in the order that you specify with the number on the line. For example, if you have |99 that is generally first.

Yes, I would put the burn stuff with that condition so that it is checked first and have your regular rotation after it.