Problem - 65 Bard won't mez in Bastion of Thunder

[Snooper]

Version of KissAssist.mac?

12.002

When did your problem start?

Just in Bastion of Thunder

Character Role?

1. Assist

What class is having this issue?

1. Bard

How often does this issue occur?

Always

I've only been playing with kissassist a short while so I'm still a super noob! I've use the bard in Plane of Fire and she has worked perfectly with mez but for some reason in Bastion of Thunder she will NOT mez anything except "a jord kjal". If I run her manually I can mez them but kissassist won't. Am I doing something wrong? I will post my ini file below. Thank you in advance for any/all help!!

[General]
KissAssistVer=12.002
Role=Assist
CampRadius=50
CampRadiusExceed=400
ReturnToCamp=0
ChaseAssist=0
ChaseDistance=20
MedOn=0
MedStart=20
MedStop=50
MedCombat=0
LootOn=0
RezAcceptOn=1|90
AcceptInvitesOn=1
GroupWatchOn=0
GroupWatchCheck=FALSE
CorpseRecoveryOn=0
EQBCOn=0
DanNetOn=0
DanNetDelay=20
IRCOn=0
CampfireOn=0
CharInfo=Bard|65|GOLD
DefaultUI=TRUE
DPSMeter=0
ScatterOn=0
LOSBeforeCombat=0
TwistOn=1
TwistMed=1
TwistWhat=1 2 3 4 5
XTSlot=0
UseSpawnMaster=0
[SpellS]
MiscGem=8
MiscGemLW=0
MiscGemRemem=1
LoadSpellSet=0
SpellSetName=KissAssist
CastingInterruptOn=1
CheckStuckGem=1
Gem1=Selo's Accelerando
Gem2=Guardian Rhythms
Gem3=Anthem de Arms
Gem4=Cassindra's Chorus of Clarity
Gem5=Alenia's Disenchanting Melody
Gem6=Crission's Pixie Strike
Gem7=Kelin's Lugubrious Lament
Gem8=Cinda's Charismatic Carillon
[Buffs]
BuffsOn=0
BuffsSize=5
Buffs1=NULL
Buffs2=NULL
Buffs3=NULL
Buffs4=NULL
Buffs5=NULL
RebuffOn=1
CheckBuffsTimer=10
PowerSource=NULL
[Melee]
AssistAt=98
MeleeOn=1
FaceMobOn=1
MeleeDistance=50
stickhow=loose
AutoFireOn=0
UseMQ2Melee=0
TargetSwitchingOn=1
MeleeTwistOn=1
MeleeTwistWhat=Continuous
PetTauntOverride=0
[GMail]
GMailHelp=Events currently support - Dead,Drag,GM,Level,Named,Leftgroup,Tells
GMailOn=0
GMailSize=5
GMail1=NULL
GMail2=NULL
GMail3=NULL
GMail4=NULL
GMail5=NULL
[AE]
AEOn=0
AESize=10
AERadius=50
AE1=NULL
AE2=NULL
AE3=NULL
AE4=NULL
AE5=NULL
AE6=NULL
AE7=NULL
AE8=NULL
AE9=NULL
AE10=NULL
[DPS]
DPSOn=0
DPSSize=20
DPSSkip=20
DPSInterval=2
DPS1=NULL
DPS2=NULL
DPS3=NULL
DPS4=NULL
DPS5=NULL
DPS6=NULL
DPS7=NULL
DPS8=NULL
DPS9=NULL
DPS10=NULL
DPS11=NULL
DPS12=NULL
DPS13=NULL
DPS14=NULL
DPS15=NULL
DPS16=NULL
DPS17=NULL
DPS18=NULL
DPS19=NULL
DPS20=NULL
DebuffAllOn=0
[Aggro]
AggroOn=0
AggroSize=5
Aggro1=NULL
Aggro2=NULL
Aggro3=NULL
Aggro4=NULL
Aggro5=NULL
[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=0
HealInterval=0
AutoRezOn=0
HealsSize=5
Heals1=NULL
Heals2=NULL
Heals3=NULL
Heals4=NULL
Heals5=NULL
XTarHeal=0
XTarHealList=Xtar slots here Example: 5|6|7
HealGroupPetsOn=0
RezMeLast=0
[Cures]
CuresOn=0
CuresSize=5
Cures1=NULL
Cures2=NULL
Cures3=NULL
Cures4=NULL
Cures5=NULL
[Merc]
Help=To use: Turn off Auto Assist in Manage Mercenary Window
MercOn=0
MercAssistAt=92
[Mez]
MezOn=1
MezRadius=75
MezMinLevel=0
MezMaxLevel=68
MezStopHPs=80
MezSpell=Lullaby of Morell
MezDebuffOnResist=1
MezDebuffSpell=Harmony of Sound
MezAESpell=Your AE Mez Spell|0
[Burn]
BurnAllNamed=0
UseTribute=0
BurnSize=5
Burn1=NULL
Burn2=NULL
Burn3=NULL
Burn4=NULL
Burn5=NULL
BurnTwistWhat=0
[Pull]
PullWith=Throwing Spear|Throwing Spear
PullMeleeStick=0
MaxRadius=500
MaxZRange=100
UseWayPointZ=0
PullWait=5
PullRadiusToUse=90
PullRoleToggle=0
ChainPull=0
ChainPullHP=25
PullPause=60|2
PullLevel=40|70
PullArcWidth=0
PullTwistOn=1
PullOnReturn=0
[PullAdvanced]
PullLocsOn=0
[AFKTools]
AFKHelp=AFKGMAction=0 Off, 1 Pause Macro, 2 End Macro, 3 Unload MQ2, 4 Quit Game
AFKToolsOn=1
AFKGMAction=1
AFKPCRadius=500
CampOnDeath=0
ClickBacktoCamp=0
[KConditions]
ConOn=0
CondSize=5
Cond1=TRUE
Cond2=TRUE
Cond3=TRUE
Cond4=TRUE
Cond5=TRUE
[KissError]
LastCMD:=/if (!37) {
ErrorDateTime:=01/07/2024 13:01:32
ErrorMsg:=Plugin 'MQ2Posse' could not be loaded: Plugin not found
DataError:=NULL
SyntaxError:=NULL
RunningTime:=8643396
BuildDate:=20231228
CurrentUI:=Default

 

[durango773]

Mez immunity is a backside table for Kiss if i remember. So if they are flagged in there as "mez immune" they will have to be removed or updated otherwise Kiss is just going to be like

 

[Psy]

I would start with turning on one or both of these

EQBCOn=0
DanNetOn=0

That will give you mez messages

 

[Lord Sivion]

Likely mobs cannot be mezzed. Just as some mobs cannot be rooted, snared, slowed, or stunned.

 

[Snooper]

Mez immunity is a backside table for Kiss if i remember. So if they are flagged in there as "mez immune" they will have to be removed or updated otherwise Kiss is just going to be like

Is that something on my side? If so where would I find this? Thank you for the reply!!

 

[Snooper]

I would start with turning on one or both of these



That will give you mez messages

View attachment 58395

Ok I went and turn that on for each of my toons. Is that all I need to do or do I need to load up something when I load up kissassist? Thank you for the reply!

 

[Snooper]

Likely mobs cannot be mezzed. Just as some mobs cannot be rooted, snared, slowed, or stunned.

If I go in and run the bard manually I can mez them just fine so it has to be an issue in the ini or something else I'm thinking.

 

[Psy]

Ok I went and turn that on for each of my toons. Is that all I need to do or do I need to load up something when I load up kissassist? Thank you for the reply!

That's it. Once you do that, check your MQ window for messages as it should tell you "mezzing" or not.

 

[grimmier]

I believe this is because the spawns are Giants and KA assumes all giants are immune to mez.
You can try commenting out this section of the kissassist.mac file. with | in front of the lines. 7020-7023

 

[knave23]

MezMaxLevel=68

@grimmier is probably right, but my first thought was this line (don't ask why I went straight to it lol). I can't remember, but do mobs go up to 70 in BoT?

 

[ChatWithThisName]

I believe this is because the spawns are Giants and KA assumes all giants are immune to mez.
You can try commenting out this section of the kissassist.mac file. with | in front of the lines. 7020-7023

View attachment 58425

That was actually my thoughts, glad someone else took the time to find it, as that is exactly what I was going to do! Redcent for your troubles.

 

[grimmier]

I had run into this line when adding charm to my kiss fork.
I though it was odd, when we can just tag it as immune in kissinfo.ini or let it auto tag off of the event on first attempt.

 

[Snooper]

I believe this is because the spawns are Giants and KA assumes all giants are immune to mez.
You can try commenting out this section of the kissassist.mac file. with | in front of the lines. 7020-7023

View attachment 58425

This fixed it!!! Thank you!! But I might have messed something else up now. When the bard mez's a mob the following will contiually spam across the screen.

"DoCommand - Couldn't parse '/continue|'
kissassist.mac@7022 (DoMezStuff(string SentFrom)): /continue|
kissassist.mac@7682 (MezCheck(sentFrom)): /call DoMezStuff MezCheck
kissassist.mac@1065 (Combat): /call MezCheck Combat
kissassist.mac@524 (checkForCombat(int SkipCombat, string FromWhere, int WaitTime)): /call Combat
Kissassist.mac@365 (Main): /if (${DPSOn} || ${MeleeOn}) /call CheckForCombat 0 MainLoop1 0"

Once I start to attack the mezzed mob that spam will stop and she will go back to normal. During the spam she will still fight like normal and remez said mob though. It's just the screen spam that gets annoying.

 

[grimmier]

This fixed it!!! Thank you!! But I might have messed something else up now. When the bard mez's a mob the following will contiually spam across the screen.

"DoCommand - Couldn't parse '/continue|'
kissassist.mac@7022 (DoMezStuff(string SentFrom)): /continue|
kissassist.mac@7682 (MezCheck(sentFrom)): /call DoMezStuff MezCheck
kissassist.mac@1065 (Combat): /call MezCheck Combat
kissassist.mac@524 (checkForCombat(int SkipCombat, string FromWhere, int WaitTime)): /call Combat
Kissassist.mac@365 (Main): /if (${DPSOn} || ${MeleeOn}) /call CheckForCombat 0 MainLoop1 0"

Once I start to attack the mezzed mob that spam will stop and she will go back to normal. During the spam she will still fight like normal and remez said mob though. It's just the screen spam that gets annoying.

did you only comment out one line? or does it look like this now?

           | Test -> is target a giant unmezzable
           | /if (${Spawn[${MezArray[${i},1]}].Body.Name.Equal[Giant]}) {
           |     DEBUGMEZ Spawn[MezArray[${i},1]] (${Spawn[${MezArray[${i},1]}].Name} ID:${MezArray[${i},1]}) is a giant, Skip
           |     /continue
           | }

 

[Snooper]

did you only comment out one line? or does it look like this now?

           | Test -> is target a giant unmezzable
           | /if (${Spawn[${MezArray[${i},1]}].Body.Name.Equal[Giant]}) {
           |     DEBUGMEZ Spawn[MezArray[${i},1]] (${Spawn[${MezArray[${i},1]}].Name} ID:${MezArray[${i},1]}) is a giant, Skip
           |     /continue
           | }

I thought I did them all but it looks like I only did ONE! I am forever grateful thank you thank you!!

There is one more tiny question I have. Everytime I zone I have to "refresh injections" to get the MQ windows back up is that normal?

 

[grimmier]

I thought I did them all but it looks like I only did ONE! I am forever grateful thank you thank you!!

There is one more tiny question I have. Everytime I zone I have to "refresh injections" to get the MQ windows back up is that normal?

that is not normal as far as i have seen. i would bring that up in the discord channels and see if anyone can help trouble shoot.
also make sure you are on latest release of VV from launcher

 

[durango773]

99.9% of the times it means:

MQ is not supported on Truebox servers. If/When a server transitions into "relaxed truebox" or complete removal of truebox restrictions, MQ support would be added at *sometime* afterwards.

> Here is the link to the sticky <

Other tools such as MySEQ and IonBC are available for truebox servers.

 

[Sic]

There is one more tiny question I have. Everytime I zone I have to "refresh injections" to get the MQ windows back up is that normal?

this means that you are trying to circumvent truebox restrictions as durango said.

MQ isn't supported on truebox servers.

 

[Snooper]

99.9% of the times it means:

MQ is not supported on Truebox servers. If/When a server transitions into "relaxed truebox" or complete removal of truebox restrictions, MQ support would be added at *sometime* afterwards.

> Here is the link to the sticky <

Other tools such as MySEQ and IonBC are available for truebox servers.

Oh I wasn't aware! Thank you for the info I appreciate it!!