Problem - Enchanter Mezzing issue - "Confound" Vs "Confounding Constriction"

[Cluelessone]

Enchanter Mezzing issue - "Confound" Vs "Confounding Constriction"

This took me many deaths and more time to track down.

I had "Confound" as my mezz spell and "Confounding Constriction" as one of my DPS spells. Long story short, whenever KISS stated it was mezzing, it actually cast the "Confounding Constriction" which is a DOT that prevented me from manually mezzing the mobs.

Even taking "Confounding Constriction" out of DPS didn't help, I had to remove it from memorized spells to get KISS to start casting the right spell.

- - - Updated - - -

I don't know if it matters (haven't had time to test) but I had "Confounding Constriction" loaded in gem 3 and "Confound" in gem 7, if the macro goes in order and just grabs the first thing that matches. I will test later today.

 

[Maskoi]

Re: Enchanter Mezzing issue - "Confound" Vs "Confounding Constriction"

Kiss can't mezz from the dps section.
If you dot the mobs you can't mez them

 

[vivviv]

Re: Enchanter Mezzing issue - "Confound" Vs "Confounding Constriction"

[Mez]
MezOn=1
MezRadius=80
MezMinLevel=90
MezMaxLevel=113
MezStopHPs=60
MezSpell=Chaotic Delusion
MezAESpell=Perplexing Wave|3

at 110

 

[Cluelessone]

Re: Enchanter Mezzing issue - "Confound" Vs "Confounding Constriction"

Kiss can't mezz from the dps section.
If you dot the mobs you can't mez them

Hmm, I must not have explained it well.

Confound was in the Mezz section and "Confounding Constriction" was in the DPS section. I even took "Confounding Constriction" completely out of the INI file and the macro still cast "Confounding Constriction" instead of "Confound" when trying to mezz.

The macro seems to be matching the spell "CONFOUNDing Constriction" for "CONFOUND". It's only when I removed "Confounding Constriction" from my memorized spells did the macro start casting the correct spell.

TLDR:
I think the macro is matching "CONFOUNDing Constriction" when trying to cast "CONFOUND". I think it matches the word "CONFOUND" and ignores the rest of the memorized spell name.

- - - Updated - - -

[Mez]
MezOn=1
MezRadius=80
MezMinLevel=90
MezMaxLevel=113
MezStopHPs=60
MezSpell=Chaotic Delusion
MezAESpell=Perplexing Wave|3

at 110

Thanks but I am level 100 so I am stuck with "Confound" and "Confounding Constriction" until I hit 110.

Also I just wanted to point out what may be a bug in the code. I believe the same thing may happen with other spells that the first part matches.

- - - Updated - - -

I don't know if it matters (haven't had time to test) but I had "Confounding Constriction" loaded in gem 3 and "Confound" in gem 7, if the macro goes in order and just grabs the first thing that matches. I will test later today.

OK I tested a bit with this and if I memorize "Confounding Constriction" before I memorize "Confound", then the macro always casts "Confounding Constriction" when it should cast "Confound".

If I put "Confound" on top of "Confounding Constriction" in my memorized spell gems, then the macro correctly casts "Confound" most of the time, maybe one in 10 mezzes turned out to be "Confounding Constriction" with the rest being "Confound"

I know this sounds confusing but I am unsure how to better explain it:

This DOES work:
Gem1=Enunciation of Tashan
Gem2=Diminishing Helix
Gem3=Confound
Gem4=Stifle
Gem5=Mind Squall
Gem6=Confounding Constriction
Gem7=Slackening Wave
Gem8=Mental Appropriation
Gem9=Mindcleave
Gem10=NULL
Gem11=Night's Dark Terror
Gem12=NULL
Gem13=NULL

This does NOT work:
Gem1=Enunciation of Tashan
Gem2=Diminishing Helix
Gem3=Confounding Constriction
Gem4=Stifle
Gem5=Mind Squall
Gem6=Confound
Gem7=Slackening Wave
Gem8=Mental Appropriation
Gem9=Mindcleave
Gem10=NULL
Gem11=Night's Dark Terror
Gem12=NULL
Gem13=NULL

 

[ctaylor22]

Re: Enchanter Mezzing issue - "Confound" Vs "Confounding Constriction"

This is an EQ Client issue. Try using /cast confound and it will cast confounding constriction if confounding constriction is memed above confound.


This could be fixed in KISS 11 if we change the /cast "${WhatSpell}" to /cast ${Me.Gem[${WhatSpell}]}

 

[Sinn69]

Re: Enchanter Mezzing issue - "Confound" Vs "Confounding Constriction"

try taking out confounding constriction from from your ini and spell lineup and see if it mezzing correctly.

 

[Cluelessone]

Re: Enchanter Mezzing issue - "Confound" Vs "Confounding Constriction"

try taking out confounding constriction from from your ini and spell lineup and see if it mezzing correctly.

It does, that is what I am using now. Not a huge deal but something I thought you guys should know about. It confused me for a long time

 

[ctaylor22]

Re: Enchanter Mezzing issue - "Confound" Vs "Confounding Constriction"

Thanks for the information. The MQ2Cast plugin just uses the /cast command in the end. So the problem is NOT with MQ2Cast plugin. The Active version of kiss uses the /casting command and KISS 11 uses /cast command. So this issue would be easier to fix in KISS 11. To fix this issue you have to cast using the GEM number the spell is in. Using the spell name and/or ID returns the same results.