Problem - EMU - Project Lazarus - LootOn Error

[Naturesong]

Version of KissAssist.mac?

12.002

When did your problem start?

When trying to run KissAssist on Project Lazarus

Character Role?

1. Assist
2. Tank

What class is having this issue?

1. Cleric
2. Enchanter
3. Monk

How often does this issue occur?

Often

Can you reproduce the issue?

Mostly

I've seen the previous threads on this issue and understand that it's an issue with there being no mq2autoloot available.
I have set LootOn=0 but it doesn't appear to pick it up consistently.
I commonly see /mac Kissassist Tank work ok (but not always), but all the other characters in the group show the error when running /mac Kissassist assist ${Group.MainAssist} (I have group roles set).

The threads that I've read highlight the cause, but don't appear to point to a solution.

Is there a way to for KA to recognise that it is running on an EMU server i.e. no mq2autoloot, and ensure that the setting LootOn=0 is picked and the variable set correctly?

NB: in providing information about which classes are affected and what roles, I've only selected the ones I've tested. I would expect to see the issue with all classes and all roles.

 

[ctaylor22]

I know it looks like it is kissassist that is kicking out that error, but it is a plugin that is trying to use LootOn. If you notice the line(s) below the Warning message:
/doevents flush
/declare XSlotTotal int outer 20

The Macro just happened to be on those lines when an error was generated. The Macro engine just sees an error and kicks out a message, even though the macro did not generate the error. Notice the 2 lines that Kissassist is giving the warning on. Neither of those reference LootOn, and since you can only have one macro running at a time. Then something else is trying to use LootOn and 99% of the time it is a plugin.

 

[Naturesong]

I know it looks like it is kissassist that is kicking out that error, but it is a plugin that is trying to use LootOn. If you notice the line(s) below the Warning message:
/doevents flush
/declare XSlotTotal int outer 20

The Macro just happened to be on those lines when an error was generated. The Macro engine just sees an error and kicks out a message, even though the macro did not generate the error. Notice the 2 lines that Kissassist is giving the warning on. Neither of those reference LootOn, and since you can only have one macro running at a time. Then something else is trying to use LootOn and 99% of the time it is a plugin.

I went though the macro and commented out any function call that stems from a LootOn reference as well as the ninjja loot include.
Felt a bit like an old timey barber severing limbs.
Works like a charm since ... ¯\_ (ツ)_/¯