Problem - Interrupt Heals above Threshold

[shaf0o6]

Version of KissAssist.mac?

KissAssistVer=12.002

When did your problem start?

Always had it

Character Role?

1. Assist

What class is having this issue?

1. Cleric

How often does this issue occur?

Always

I am trying to set it up so that my healers won't overlap healing the same targets. With my shaman, if someone gets above a certain HP threshold, I will get a message saying "cast interrupted, target is above xx% threshold". But for my cleric, he will not interrupt the heals at all.

I have tried setting this flag to 1 and 4 (CastingInterruptionOn), but it doesn't seem to be working on my cleric. I believe my shaman was interrupting his heals even without this flag set though. I did end up flipping it to 4 on both the shaman and cleric.

Anyone have any thoughts or suggestions on how I can get this setup for the cleric as well?

[Spells]
CastingInterruptOn=4

 

[ctaylor22]

Setting the CastingInterruptOn=1 will have the Casting Interrupt routine to check for all casting situations. Single Heals, Cures, Mez, DPS, and Buffs. If you want to only interrupt heals then set it to 4. Make sure your cleric is not lagging. Drive your cleric or make sure they are the active screen and see if they don't interrupt when a character is healed before their heal lands.

 

[shaf0o6]

Correct, I was only wanting to do it for heals (hopefully that includes rezzes once a person accepts and it recasts), so I was setting it to 4.

I have had them as my active screen / driven from them and still no luck. This has been an on-going issue for me for almost a year. I had tried to fix it way back then with help from people but nothing I changed seemed to matter. It has never once tried to interrupt the cleric heals.

 

[ctaylor22]

If you can get me a debug log of the cleric casting heals. I will take a look and see what is happening.

 

[shaf0o6]

Thanks, I will run that for a bit today and get that over to you!

Potentially dumb question - where exactly does it log to? I have turned on debug logging with /debug all on, tried updating the DebugSpewToFile to 1 in Macroquest.ini, but I still don't see any log file.

 

[ctaylor22]

Use the command "/debug all on log" to start debug in logging mode and use "/debug off" to stop logging. Look in the logs folder under the MQ2 folder. you will need to change the .log ext of the file to something like .txt to upload it to the forums. DM me and upload the log file there.

 

[shaf0o6]

I do see all the debug messages spamming my MQ window, but no log is in the logs folder, other than the standard MQ logs which are not getting the output from this debug.

 

[ctaylor22]

are you using the log arg when using /debug. try doing a /debug help and make sure I am telling you correctly.

 

[shaf0o6]

I ran /debug all log which I got from the help command earlier. I tried again and still no logs are generated. The /debug all off command doesn't seem to work either. Once the logs start going, I have to kill MQ2 to stop it from spamming my window.

 

[ctaylor22]

Just use /debug off to stop the debug spam. It does take a while for the spam to stop, but it will stop. I am assuming you are running on the live servers. Try using the /plugin list and see if MQ2Log is loaded.

 

[shaf0o6]

I had tried with MQ2logs enabled and disabled. No log file was generated for either. Only the generic log for MQ2 and mq2nav.

I'm okay with it not working - I don't want to waste too much of your time on this! I was just hoping someone had a quick and easy solution on what the issue may be.

 

[ctaylor22]

It is not a problem. But it sounds like you may be looking in the wrong location for the log file. Try this just to see what happens
From your cleric use the following commands:

/mlog on
/echo Testing Mlog!
/mlog off

Now go check your log folder and see if you see a log file for your cleric.

 

[shaf0o6]

Thanks, I had the log plugin enabled but logs weren't turned on. Once I turned them on, it wrote the logs into a file.

 

[shaf0o6]

Just to update the thread in case anyone else was interested in this. The issue ended up being my cleric's heal was set to 64% and shaman's heal was set to 67%. It turned out 65% was the threshold in the background for the auto interrupting. So cleric was just below that threshold and wouldn't trigger the auto interrupt.

I believe @ctaylor22 is updating the script to auto interrupt for any threshold heal only when the targets HP is above 98%.