Question - KissAssist Keeps Overwriting LoadSpellSet=2 Back to 0 — Inconsistent Behavior

[Gykrossin]

I’ve been running into a frustrating issue with my KissAssist setup — my toons keep having their LoadSpellSet=2 value reset back to LoadSpellSet=0. It doesn’t happen every time, but often enough to be annoying.

To troubleshoot, I’ve already gone through and completely re-written all of my .ini files to make sure there aren’t any duplicate LoadSpellSet=0/2 entries hiding anywhere. Unfortunately, the problem still happens — usually when I load my team through EQBC.

Here’s what my basic macro looks like:
Most issues come from macro

Macro

/bcg //mac kissassist assist <Name> 98
/pause 5
/mac kissassist PullerTank

When using QKI, which I absolutely loved, this issue happened even more often — to the point where spells wouldn’t load properly and my toons would stop behaving as expected. Sadly, I had to stop using QKI, even though it’s an amazing GUI/Lua setup.

Here’s the QKI version of my macro:

Macro

/bcg //mac kissassist assist <Name> 99
/pause 5
/mac kissassist PullerTank
/pause 5
/bcga //lua run qki

I’m mainly asking to see if anyone else has experienced this or knows what I might be missing to keep KissAssist running consistently — ideally in a way that lets me use QKI again without the LoadSpellSet resetting.


Any insight, suggestions, or fixes would be greatly appreciated!


Revised INI for a main
[CODE title="Revised INI for a Main"][General]
KissAssistVer=12.002
Role=PullerTank
CampRadius=30
CampRadiusExceed=500
ReturnToCamp=1
ChaseAssist=0
ChaseDistance=25
MedOn=1
MedStart=35
MedStop=85
MedCombat=0
LootOn=0
RezAcceptOn=1|0
AcceptInvitesOn=1
GroupWatchOn=1|45
GroupWatchCheck=FALSE
CorpseRecoveryOn=0
EQBCOn=1
DanNetOn=0
DanNetDelay=20
IRCOn=0
CampfireOn=1
CharInfo=-|-|-
DefaultUI=TRUE
DPSMeter=1
ScatterOn=0
LOSBeforeCombat=0
UseSpawnMaster=0
XTSlot=1

[AFKTools]
AFKHelp=AFKGMAction=0 Off, 1 Pause Macro, 2 End Macro, 3 Unload MQ2, 4 Quit Game
AFKToolsOn=0
AFKGMAction=1
AFKPCRadius=500
CampOnDeath=0
ClickBacktoCamp=1

[SpellSet]
LoadSpellSet=2

[Spells]
Gem1=Spike of Disease
Gem2=Disease Cloud
Gem3=Lifespike
Gem4=Scream of Hate
Gem5=Engulfing Darkness
Gem6=Lesser Summon Corpse
Gem7=Bone Walk
Gem8=Grim Aura
MiscGem=8
MiscGemLW=0
MiscGemRemem=1
CastingInterruptOn=1
CheckStuckGem=1

[DPS]
DPSOn=2
DPSSize=6
DPSSkip=20
DPSInterval=2
DPS1=Disease Cloud|98
DPS2=Scream of Hate|95
DPS3=Lifespike|75|cond3
DPS4=Spike of Disease|70
DPS5=Engulfing Darkness|65
DebuffAllOn=0
DPS6=NULL

[Burn]
BurnSize=5
BurnAllNamed=0
UseTribute=0
Burn1=NULL
Burn2=NULL
Burn3=NULL
Burn4=NULL
Burn5=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

[Buffs]
BuffsOn=1
BuffsSize=5
Buffs1=Grim Aura
Buffs2=Endure Cold
RebuffOn=1
CheckBuffsTimer=2000
Buffs3=NULL
Buffs4=NULL
Buffs5=NULL
PowerSource=NULL

[Mez]
MezOn=0
MezRadius=50
MezMinLevel=10
MezMaxLevel=55
MezStopHPs=90
MezSpell=NULL
MezAESpell=NULL
MezDebuffOnResist=0
MezDebuffSpell=NULL

[Heals]
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
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50

[Cures]
CuresOn=1
CuresSize=5
Cures1=Cure Disease|disease
Cures2=NULL
Cures3=NULL
Cures4=NULL
Cures5=NULL

[GoM]
GoMSize=1
GoMSHelp=Format - Spell|Target, MA Me or Mob, i.e. Rampaging Servant Rk. II|Mob
GoMSpell1=NULL

[Melee]
AssistAt=98
MeleeOn=1
FaceMobOn=1
MeleeDistance=75
StickHow=snaproll
AutoFireOn=0
UseMQ2Melee=1
TargetSwitchingOn=0
PetTauntOverride=0

[Aggro]
AggroOn=0
AggroSize=5
Aggro1=NULL
Aggro2=NULL
Aggro3=NULL
Aggro4=NULL
Aggro5=NULL

[Pull]
PullWith=Engulfing Darkness
PullMeleeStick=0
MaxRadius=750
MaxZRange=500
UseWayPointZ=0
PullWait=5
PullRadiusToUse=100
PullRoleToggle=1
ChainPull=0
ChainPullHP=0
PullPause=30|2
PullLevel=15|25
PullArcWidth=360
PullTwistOn=0
PullOnReturn=0

[PullAdvanced]
PullLocsOn=0

[Pet]
PetOn=1
PetCombatOn=1
PetSpell=Bone Walk
PetBuffsOn=1
PetBuffsSize=8
PetRampPullWait=0
PetSuspend=0
PetForceHealOnMed=0
PetFocus=NULL
PetShrinkOn=0
PetShrinkSpell=Tiny Companion
PetBuffs1=NULL
PetBuffs2=NULL
PetBuffs3=NULL
PetBuffs4=NULL
PetBuffs5=NULL
PetBuffs6=NULL
PetBuffs7=NULL
PetBuffs8=NULL
PetAssistAt=95
PetAttackDistance=115
PetToysSize=6
PetBreakMezSpell=NULL
MoveWhenHit=0
PetHoldOn=1
PetToysGave=

[Merc]
Help=To use: Turn off Auto Assist in Manage Mercenary Window
MercOn=0
MercAssistAt=92

[KConditions]
ConOn=1
CondSize=5
Cond1=TRUE
Cond2=FALSE
Cond3=${Me.PctHPs} < 75
Cond4=TRUE
Cond5=TRUE
[/CODE]

 

[kaen01]

if you using qki, then its a qki issue, and not a kissassist isseu, should post under the qki resource

 

[Gykrossin]

if you using qki, then its a qki issue, and not a kissassist isseu, should post under the qki resource

This is an issue for both, and not just QKI, as stated in the question.

 

[kaen01]

and to asnwer your question kinda, i never had kissassist reset any numbers i changed

 

[kaen01]

i am wondering if you have your mq on a synced drive like onedrive or something perhaps?

 

[Sic]

if you using qki, then its a qki issue, and not a kissassist isseu, should post under the qki resource

This is an issue for both, and not just QKI, as stated in the question.

it really *sounds* an aweful lot like *something else* is updating/saving/changing your kiss ini.

if you saved it, kiss wouldn't have a means/reason to change it it would only create the default it if it is missing

 

[Gykrossin]

i am wondering if you have your mq on a synced drive like onedrive or something perhaps?

I am completely using internal hardware without any syncs. I am not a big fan of Cloud systems, to be honest. =D

it really *sounds* an aweful lot like *something else* is updating/saving/changing your kiss ini.

if you saved it, kiss wouldn't have a means/reason to change it it would only create the default it if it is missing

Thanks for your insight and wisdom, and will look to dig deeper into my issue.

If, by chance, I do figure out the issue, I will let everybody know what it was.

 

[kaen01]

i am also thinking here, maybe you have multiple inis? some in config folder, some in macros folder?

currently mq is designed to have all inis in the config folder, maybe worth checking up on?

 

[reedreddington]

I always give my spell set a name so I can track if things are updating strangely.

 

[Motojeff]

I am thinking you got duplicate ini's - could do something like /mac kissassist ini MyCustomFileName.ini to isolate to a specific ini -- seen here https://www.redguides.com/docs/projects/kissassist/cmd-mackissassist/

 

[Gykrossin]

i am also thinking here, maybe you have multiple inis? some in config folder, some in macros folder?

currently mq is designed to have all inis in the config folder, maybe worth checking up on?

I was thinking something along those lines too. So I did do a scan of my files, to see if something was misplaced. May do a more in depth inspection to make sure this is not the case. Thanks.

I am thinking you got duplicate ini's - could do something like /mac kissassist ini MyCustomFileName.ini to isolate to a specific ini -- seen here https://www.redguides.com/docs/projects/kissassist/cmd-mackissassist/

When I do my more in depth inspection, I am going to check this, and other plausible scenarios too.


I want to say that everybody has been awesome, and giving great insight into the plausible issue.

 

[nitramneb]

[SpellSet]
LoadSpellSet=2
[/CODE]

So what I see different on my inis is you have a header for spellset, which does not exist in my inis... Try moving the LoadSpellSet=2 under the [Spells] header.

 

[ctaylor22]

@nitramneb is correct. Using the [SpellSet] group identifier is creating a separate group for LoadSpellSet. The macro would just recreate the LoadSpellSet Entry in the [Spells] group and set it to 0.

 

[Gykrossin]

So what I see different on my inis is you have a header for spellset, which does not exist in my inis... Try moving the LoadSpellSet=2 under the [Spells] header.

I have not been online in a bit, and wanted to respond to my question, with the above information.

Just as Ctaylore stated.

@nitramneb is correct. Using the [SpellSet] group identifier is creating a separate group for LoadSpellSet. The macro would just recreate the LoadSpellSet Entry in the [Spells] group and set it to 0.

This was the issue, and the problem is resolved.

I want to say thanks for all the great feedback, and the help in finding the issue. Everybody here are ROCKSTARS!!!!!