Problem - MezDebuffOnResist not used

[timmy]

Version of KissAssist.mac?

11.05

When did your problem start?

first noticed feb 2020

Character Role?

1. Assist

What class is having this issue?

1. Enchanter

How often does this issue occur?

Always

Can you reproduce the issue?

yes. happens 100 percent of the time.

early edition tl:dr enc never tries to drop a tash if the mob resists his first mez.

first posted about this in feb. but wasn't sure if i was in error trying to use an aa or if my issue was a spell was required. finally captured the behavior with a log in hopes of some salvation.

couple questions posed/considered from my first post is that enc never tries to debuff mobs before mez, so i included all the debuff info. i asked at the bottom of that post if that was the actual order of operations for enc. seems like enc always tries to mez before debuffs or even ae. i could be wrong about that, but i am curious just for the sake of knowing.

the log might be long, but so much spam with the debug option going on i wasn't 100 percent sure this happened until the last mobs in the log.

here is my mez section:

[CODE lang="ini" title="mez section"][Mez]
MezOn=1
MezRadius=100
MezMinLevel=90
MezMaxLevel=118
MezStopHPs=80
MezDebuffOnResist=1
MezDebuffSpell=Proclamation of Tashan
MezSpell=Chaotic Deception
MezAESpell=Neutralizing Wave|4[/CODE]

the relevant lines from my dps section:

[CODE lang="ini" title="debuffs"]DebuffAllOn=1
DPS9=Proclamation of Tashan|100|debuffall|tash[/CODE]

my ae section to just confirm that i'm not using any tash there:

[CODE lang="ini" title="ae section"][AE]
AEOn=1
AESize=1
AERadius=100
AE1=Beam of Slumber|5|Mob[/CODE]

 

[Evelyn]

Can you post your full/entire ini file? I also see in your log file that you were trying to mez Restless Orcs in Velks that are mezz immune. In fact all the mezzes in your log pertain to mezz immune mobs. When you get a mezz immune mob, the mezz section will skip it (at least that's what I see broadcasted in my MQ window for my group).

In general, from an enchanter playing viewpoint, you do mez first and then deal with resists second. That's why enchanters and bards rely on capping out their Charisma stat since it affects mez resists. Unless, you are familiar with certain mobs that you know will give you high resists no matter what, you generally try to cast mez first. By design, KA will mez first, with that being said.

Now as far as why it's not debuffing on resists for a "mezzable mob" for you, let's try to narrow something down.

Looking at this part:
MezStopHPs=80

Are you noticing that the mob is still above 80 percent health when you realize it's not debuffing on a resist? This line tells the enchanter to just give up on mezzing an add that is at 80 percent or lower HP. So that's the first thing worth asking here. Going on the same logic here, I'm also curious if you have DPSOn=1 or DPSOn=2 and if maybe that is causing a conflict in KA when checking against the Mez section. I see in your log file this snippet: DPSOn: 2

I alway use DPSOn=1 in my enchanter ini file since I want to cast things according to mob health and not cast things in absolute descending order (which is what DPSOn=2 does). I'm not sure if in your case this is related to the MezStopHPs line, but it's worth a shot to change DPSOn=1 and see if that affects anything. I would think that the mez section should take precedence over the DPS section no matter what, but that may not be the case if there is a conflict with DPSOn=2, and I think that is something that should be looked into if that's the case.

In any case, your log file seems to explain the actions your enchanter is taking accordingly. If you were to use DPSOn=1, you would be debuffing all the mezz immune mobs (after they are skipped accordingly by the mez section). That's what my enchanter does.

 

[timmy]

there is a chance that some mobs have been below 80 at some point but i've noticed this behavior (no tash on mez resist) for a long time so i'm guessing that at some point it's happened when the mobs have been above 80. i'll not use any dps and see if i can confirm for science.

i use dps2 because (lol) i want to go through the 8 things i have before tash. =p 5 of those are ambush tags and they all are burn stuff but i'll try dps 1 and see if it changes anything. at this point, i'll turn dps off if i can get the enc to drop an ae tash on a mez resist. it's not a life or death thing that breaks my gameplay, but it's more like i'm just ready to spank my enchanter for being so naughty and refusing to use his tools.

 

[Evelyn]

I don't see how DPS1 will change your gameplay drastically. DPS2 is usually used by wizards and mages since they don't need to change targets or juggle anything else beyond just straight up dps. It is generally not advisable to have the 1st spell that enchanters usually cast on DPS line 9. It should be on DPS line 1. If you look at any inis in the library for debuffing classes, their debuffs are at the top.

This line could potentially be an additionally problem combined with DPSOn=2:
DPS9=Proclamation of Tashan|100|debuffall|tash

The line by itself is stating to tash all mobs in camp at 100 percent health, but it will not even bother reading it until it reaches your DPS line 9 since it's casting in a rigorous order thanks to DPSOn=2. Once the absolute rotation is completed, only then it will address things according to mob health in the DPS section.

Considering you have DPS2, I would image it can make matters even worse if you have CastingInterruptOn=0 as you are basically telling your chanter to just not interrupt casting either to do something else. A

I don't have this issue which is why I am pointing these things out to see if they fix them for you.

 

[timmy]

the only problem the enc has is not using tash on a mez resist. otherwise he performs flawlessly. my first 5 dps lines are ambush tags. those tags are legit and do exactly what they do. the next 3, actually, are set at 99. tash use to be set at 99 as well, but i started experimenting with a larger camp radius and tash at 100 to get mobs tashed on inc and not waiting until mob was much closer and being damaged. that 100 value is literally something i stole from your ini very recently =p but even before that, i had this no tash on resist issue.

i'll turn dps off, see if that helps. i'll remove all dps tags but tash, see if that helps. but my only issue is the tash on resist. ><

updates:

lowered MezStopHPs to 50. can confirm mob health was above that when no tash was used on mez resist.
dps0 saw no tash on resist being used.
dps1 with only the tash line saw no tash on resist being used.

sad pandas everywhere.

 

[ctaylor22]

@Evelyn and @timmy Let me clarify something, DPSOn and it's value will have no bearing on how the Debuff routine works. All entries in the DPS array that have a DebuffAll tag are moved to the top of the DPS array, when sorted, and skipped in the CombatCast routine.

@timmy There have been some improvements made in the mez routine in Kiss 12. I know there was an issue during the alpha/beta testing phase that we made some changes because of this exact issue. Here is the fix:

in the MezMobs routine change this line:

                    } else /if (${Macro.Return.Equal[CAST_RESIST]} && ${MezFail}<2) {

To This:

                    } else /if (${Macro.Return.Equal[CAST_RESISTED]} && ${MezFail}<2) {

Also DebuffAllOn has 3 settings: 0/1/2. 1 - Tells the Debuff routine that DPS gets priority and cast debuffs if spell is ready, but DON'T wait for spells to refresh. 2 - Tells the Debuff Routine that Debuffs get priority and to wait for debuff spells to refresh.

 

[timmy]

changed that line and boom, enc started dropping tash! tried both single tash and aa ae tash and both worked. fantastic. thank you.

i might be pressing my luck, but if i wanted to drop the tash on resist after only one fail instead of two, could i change a value in the mez mobs sub? and i noticed a /delay 3 before calling the cast debuff spell. because i'm using an aa off the gcd, i think i could shorten that time up, but maybe i don't understand what that delay is actually for.

 

[ctaylor22]

Spell Global cooldown is like 3.5 seconds. If you don't wait, then when you hit the CastWhat routine the spell won't be ready and leave the CastWhat Routine without casting the Debuff spell. You may be using an AA, but not everyone does.