Thank you @ctaylor22 for continuing to maintain this project! I continue to use it exclusively for all my groups!
-
Hail, we're RedGuides. We want you to play several EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋
- Thread starter ctaylor22
- Start date
Thank you @ctaylor22 for continuing to maintain this project! I continue to use it exclusively for all my groups!
I’m not sure how much other dev’s use chatgpt/copilot, but figured I’d mention it here.
In learning the KA syntax over the past week or so I’ve found chatGPT to be extremely helpful. If anyone else is starting off with KA it may help you also.
The functionality chatGPT provides is sort of like an assistant who is pretty smart but you can’t always rely on being accurate. Some jobs I’ve asked it for help with have been along the lines of “how can I add a mez section into my bards .ini for kissassist”.
You can also copy a full .ini that you’ve grabbed from the library into chatgpt and ask it questions about each section. One handy but I’ve used it for in other situations in the past is optimizing code, and it seems to work well with KA ini’s too.
Anyhow, if you are new to KA (or like the idea of a little help) give chatGPT a try. The older (3.5) version is free and easy to use.
In learning the KA syntax over the past week or so I’ve found chatGPT to be extremely helpful. If anyone else is starting off with KA it may help you also.
The functionality chatGPT provides is sort of like an assistant who is pretty smart but you can’t always rely on being accurate. Some jobs I’ve asked it for help with have been along the lines of “how can I add a mez section into my bards .ini for kissassist”.
You can also copy a full .ini that you’ve grabbed from the library into chatgpt and ask it questions about each section. One handy but I’ve used it for in other situations in the past is optimizing code, and it seems to work well with KA ini’s too.
Anyhow, if you are new to KA (or like the idea of a little help) give chatGPT a try. The older (3.5) version is free and easy to use.
ctaylor22 updated KissAssist with a new update entry:
More Power! Well for some DPS casters, but not everyone.
Read the rest of this update entry...
More Power! Well for some DPS casters, but not everyone.
Read the rest of this update entry...
That error is only generated when the spell can not be found as an AA or in your spell book. From what I can see it should be Spelled like this.
SomeRandomDude
Well-known member
Hi All,
I'd like to report what I think is a bug, but I have a workaround. I like to set everyone with GroupWatchOn=1|60, and my workaround is to turn GroupWatchOn off for everyone but the MA.
The issue is when I'm playing manually with a few automated people in the group helping out. After I have a death, and the newly rezzed character is OOM, the automated folks will flat out refuse to fight until everyone ready (>60% mana and endurance). I myself don't care about the low mana guy being available or not, so I go ahead and pull to start the next fight, and all my automated guys just stand around complaining that the group isn't ready to fight yet (I forget the exact quote in the output window).
It seems to me like the first three rules of automation should be:
1. Don't talk about automation.
2. Don't talk about automation.
3. Help out whenever there is a fight taking place.
I'm not a big fan of my workaround because it is yet another thing to change if I decide to switch around who is MA, or have someone solo that is normally not an MA, or whatever.
Thanks.
I'd like to report what I think is a bug, but I have a workaround. I like to set everyone with GroupWatchOn=1|60, and my workaround is to turn GroupWatchOn off for everyone but the MA.
The issue is when I'm playing manually with a few automated people in the group helping out. After I have a death, and the newly rezzed character is OOM, the automated folks will flat out refuse to fight until everyone ready (>60% mana and endurance). I myself don't care about the low mana guy being available or not, so I go ahead and pull to start the next fight, and all my automated guys just stand around complaining that the group isn't ready to fight yet (I forget the exact quote in the output window).
It seems to me like the first three rules of automation should be:
1. Don't talk about automation.
2. Don't talk about automation.
3. Help out whenever there is a fight taking place.
I'm not a big fan of my workaround because it is yet another thing to change if I decide to switch around who is MA, or have someone solo that is normally not an MA, or whatever.
Thanks.
YeahCopyMate
Well-known member
is there a way to tone down my guys being very interested in activating every environmental item we get near, example doors, lift buttons, sometimes even zoning out through clickable portals when I'm close to them but not wanting to zone?
That's actually not a KISS function, it's part of MQ2Nav...
Go to your EQ button --> MacroQuest --> Settings --> Plugins --> Nav, there you will find some check boxes related to doors, play around with them and see if it helps.
Having a huge issue with my bard's melee. He will be meleeing away, and when we switch mobs he wont come to me, or he will try and path directly to the mob and runinto things while meleeing nothing and get stuck on things. It doesnt seem to be assisting, naving to target, then meleeing. It will run into a wall dead on and get hung up either cause its trying to run into the wall directly, or falls off the mesh. KA below:
125 Bard KA
125 Bard KA
Code:
[General]
KissAssistVer=12.002
TwistOn=1
TwistMed=13 1 2 3 5
TwistWhat=13 1 2 3 5
XTSlot=1
Role=assist
CampRadius=60
CampRadiusExceed=400
ReturnToCamp=0
ChaseAssist=0
ChaseDistance=15
MedOn=1
MedStart=20
MedStop=90
MedCombat=0
LootOn=0
RezAcceptOn=1|90
AcceptInvitesOn=1
GroupWatchOn=0
EQBCOn=1
IRCOn=0
CampfireOn=0
CharInfo=Bard|125|GOLD
DPSMeter=0
ScatterOn=0
GroupWatchCheck=FALSE
DanNetOn=1
DanNetDelay=20
DefaultUI=TRUE
CorpseRecoveryOn=0
LOSBeforeCombat=1
UseSpawnMaster=1
[Buffs]
BuffsOn=1
BuffsSize=23
Buffs1=Aura of Tenisbre|Aura
Buffs2=Regar's Lively Crescendo
Buffs3=Rallying Call|managroup|30
Buffs4=Rallying Solo|end|29
Buffs5=Rallying Call|endgroup|30
Buffs6=Summoned: Modulation Shard VIII|Mana|80
Buffs7=Wand of Pelagic Transvergence|Mana|75
Buffs8=Selo's Sonata|Cond16
Buffs9=command:/pet swarm|99|cond6
Buffs10=Jann's Veil|Dual|Illusion Benefit Greater Jann
Buffs11=Bixie Buzzer Familiar|Dual|Familiar: Striped Badger
Buffs12=Spider's Bite XXI|Dual|Spider's Bite Poison XII|Me
Buffs13=${InvSlot[back].Item.Name}|Dual|${Me.Inventory[back].Spell}
Buffs14=Eye-Spotted Shik'Nar Saddle|Dual|Mount Blessing Neza
Buffs15=${InvSlot[Charm].Item.Name}|Dual|${Me.Inventory[Charm].Spell}
Buffs16=Summon Eye-Spotted Shik'Nar|Remove
Buffs17=Striped Badger Whistle|Dual|Familiar: Striped Badger
Buffs18=Illusion: Djinn Soldier|Remove
Buffs19=Illusion: Djinn Emissary|Remove
Buffs20=Lute of the Flowing Waters|Dual|Wind of Marr
Buffs21=Breath of Harmony|Dual|Item Benefit: Niv's Melody of Preservation
Buffs22=Mistmoore Battle Drums|Dual|Thunderous Barrier
Buffs23=Grelleth's Royal Seal|Dual|Frightful Aura
RebuffOn=1
CheckBuffsTimer=10
PowerSource=NULL
[Melee]
MeleeTwistOn=1
MeleeTwistWhat=9 10 11 12 6 2 5 6
;MeleeTwistWhat=2 3 5 7 6
AssistAt=97
MeleeOn=1
MeleeDistance=400
StickHow=snaproll rear
UseMQ2Melee=0
FaceMobOn=1
AutoFireOn=0
TargetSwitchingOn=1
PetTauntOverride=0
AssistAtt=97
[Pull]
PullTwistOn=1
PullWith=Sonic Disturbance
PullMeleeStick=0
MaxRadius=50000
MaxZRange=50000
UseWayPointZ=0
PullWait=3
ChainPull=0
ChainPullHP=40
PullPause=30|2
PullLevel=100|114
PullArcWidth=0
PullRadiusToUse=90
PullRoleToggle=0
PullOnReturn=0
[AE]
AEOn=1
AESize=1
AERadius=50
AE1=Spire of the Minstrels|3
AE2=Vainglorious Shout|3
AE3=Ecliptic Psalm|3
[DPS]
DPSOn=2
DPSSize=32
DPSSkip=1
DPSInterval=100
DPS1=Darkened Breath of Harmony|99
DPS2=Blade of Vesagran|99|Cond5
DPS3=Funeral Dirge|80|Cond12
DPS4=Quick Time|99|Cond4
DPS5=Spire of the Minstrels|99|Cond4
DPS6=Flurry of Notes|99|Cond4
DPS7=Frenzied Kicks|99|Cond4
DPS8=Dance of Blades|99|Cond4
DPS9=command:/stopdisc|99|Cond3
DPS10=command:/pet swarm|99|Cond10
DPS11=command:/pet qswarm|99|Cond10
DPS12=Bladed Song|99|Cond13
DPS13=Fierce Eye|99|Cond6
DPS14=Cacophony|99|Mob
DPS15=Intimidation|99|Mash
DPS16=${InvSlot[Chest].Item.Name}|99|Cond1
DPS17=Boastful Bellow|99|Cond2
DPS18=Selo's Sonata|15
DPS19=Thousand Blades|99|Cond4
DPS20=Reflexive Rebuttal|99|Cond8
DPS21=Unified Phoenix Feather|75|Cond9
DPS22=Miniature Horn of Unity|70|Cond9
DPS23=Selo's Sonata|99|Cond7
DPS24=Lute of the Gypsy Princess|99
DPS25=Drums of the Warlord|99
DPS26=Lute of the Flowing Waters|99
DPS27=Breath of Harmony|99
DPS28=Mistmoore Battle Drums|99
DPS29=Farseeker's Plate Chestguard of Harmony|99|Cond4
DPS30=Lyrical Prankster|99
DPS31=Song of Stone|99|Cond4
DPS32=Goblin Frost Totem|100|Cond11
DPS33=Kazumi's Note of Preservation|10|Cond4
DebuffAllOn=0
[Aggro]
AggroOn=1
AggroSize=4
Aggro1=Fading Memories|95|>
Aggro2=Shield of Notes|100|>
Aggro3=Hymn of the Last Stand|100|>
Aggro4=Deftdance|100|>
[Mez]
MezOn=0
MezRadius=70
MezMinLevel=0
MezMaxLevel=123
MezStopHPs=10
MezSpell=Slumber of Suja
MezAESpell=Wave of Stupor|10
MezDebuffOnResist=0
MezDebuffSpell=The Lady's Entreaty
MezOnn=1
[Burn]
BurnSize=7
BurnAllNamed=1
Burn1=Spire of the Minstrels
Burn2=${InvSlot[Chest].Item.Name}
Burn3=Quick Time
Burn4=Flurry of Notes
Burn5=Frenzied Kicks
Burn6=Dance of Blades
Burn7=Thousand Blades
Burn8=Song of Stone
Burn9=Lyrical Prankster
BurnText=BURN THIS DOWN
UseTribute=0
BurnTwistWhat=9 10 11 12 6 5 2 6
[KConditions]
ConOn=1
CondSize=13
Cond1=!${Me.Song[${Spell[Ecliptic Psalm of Potential].RankName}].ID}
Cond2=!${Target.Buff[Boastful Bellow].Caster.Equal[${Me.Name}]}
Cond3=${Me.ActiveDisc.ID} && ${Target.Named} && ${Me.ActiveDisc.Name.NotEqual[Thousand Blades]} && ${Me.CombatAbilityReady[Thousand Blades]}
Cond4=${Me.XTarget} > 2 || ${Target.Named}
Cond5=!${Me.Song[Fierce Eye].ID}
Cond6=!${Me.Song[Spirit of Vesagran].ID}
Cond7=!${Me.Buff[Selo's Accelerato].ID} && !${Me.Buff[Selo's Accelerando].ID}
Cond8=((${Group.Member[0].PctMana} > 0 && ${Group.Member[0].PctMana} < 90) || (${Group.Member[1].PctMana} > 0 && ${Group.Member[1].PctMana} < 90) || (${Group.Member[2].PctMana} > 0 && ${Group.Member[2].PctMana} < 90) || (${Group.Member[3].PctMana} > 0 && ${Group.Member[3].PctMana} < 90) || (${Group.Member[4].PctMana} > 0 && ${Group.Member[4].PctMana} < 90) || (${Group.Member[5].PctMana} > 0 && ${Group.Member[5].PctMana} < 90))
Cond9=!${Me.Song[Blessing of Unity].ID} && !${Me.Song[Grace of Unity].ID} && ${Me.PctMana} < 90
Cond10=${Target.Type.Equal[NPC]} && ${SpawnCount[${Me.Name}`s pet]} > 0
Cond11=${Target.CleanName.Equal[Whirling debris]}
Cond12=${Target.Named} && !${Target.Buff[Funeral Dirge].ID} && !${Target.Buff[T`Vyl's Resolve Weakness].ID} && !${Target.Buff[Braxi's Howl].ID}
Cond13=!${Target.Buff[Bladed Song].ID}
[Spells]
MiscGem=5
MiscGemLW=0
MiscGemRemem=1
LoadSpellSet=2
SpellSetName=KissAssist
CastingInterruptOn=28
Gem1=Pulse of August
Gem2=War March of Nokk
Gem3=Kanghammer's Song of Suffering
Gem4=Slumber of Suja
Gem5=Aria of Tenisbre
Gem6=Eoreg's Insult
Gem7=Nord's Disdain
Gem8=Wave of Stupor
Gem9=Kindleheart's Chant of Flame
Gem10=Swarn's Chant of Frost
Gem11=Goremand's Chant of Disease
Gem12=Marsin's Chant of Poison
Gem13=Regar's Lively Crescendo
CheckStuckGem=1
[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=1
HealsSize=3
Heals1=Spirit Drinker's Coating|50|tap
Heals2=Valia's Unyielding Bravery|30|tap
Heals3=Necromantic Dragonbone|20|tap
Heals4=NULL
Heals5=NULL
XTarHeal=0
XTarHealList=Xtar slots here Example: 5|6|7
HealGroupPetsOn=0
AutoRezOn=0
RezMeLast=0
HealInterval=0
[Cures]
CuresOn=0
CuresSize=10
Cures1=Cleansing Rod|Poison
Cures2=Cleansing Rod|Disease
Cures3=Marrow's Song|Poison
Cures4=Marrow's Song|Disease
Cures5=Marrow's Song|Curse
Cures6=Marrow's Song|Corruption
Cures7=Horn of the Stormcaller|Poison
Cures8=Horn of the Stormcaller|Disease
Cures9=Horn of the Stormcaller|Curse
Cures10=Horn of the Stormcaller|Corruption
[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=0
[Merc]
Help=To use: Turn off Auto Assist in Manage Mercenary Window
MercOn=0
MercAssistAt=98
[PullAdvanced]
PullLocsOn=0Your MeleeDistance is way too large. Your bard is going to run out of camp and try to meet the mob before it gets there. Also, your NAV mesh for the zone might need work if you're running into walls and stuff. No amount of KA tweaking can overcome a poor zone mesh although sometimes shrinking the character and clicking off any sort of Levi will help.
My bards:
CampRadius=60and
Bard melee at 125
INI:
[Melee]
AssistAt=99
MeleeOn=1
FaceMobOn=1
MeleeDistance=62
StickHow=snaproll
AutoFireOn=0
UseMQ2Melee=0
MeleeTwistOn=1
MeleeTwistWhat=6 7 8 9 10 11 1 2 3 4 5
TargetSwitchingOn=0
PetTauntOverride=0I don't camp, I hunt/chase. and it doesn't matter it happens everywhere. Instead of naving to the target, the bard is just turning on attack and running into shit.
There are no nav errors, Its simply turning on auto attack and trying to run directly at its target which is getting it stuck on things.
Also, its not a bard issue, I just only use KA on my bard.
@Myysterio ,
The GetCombatPosition routine is called, just before the Combat routine is called. The message happens when either the Mob is still too far away(MeleeDistance) or the mobs HP are not low enough(AssitAt). So reducing your MeleeDistance could help. Once in the combat routine the stick routine is used to move melee characters into position(StickHow) and turn on stick and Attack. Non melee characters don't use the Stick routine.
You could try using a COMMAND: entry in the DPS section to get positioning when needed.
DPS1=Command:/call GetCombatPosition 1|99|Cond14
Cond14=${MyTargetID} && !${Spawn[${MyTargetID}].LineOfSight}
I would be very careful with this. The argument passed to the GetCombatPosition routine can be a 0 or 1. Passing a 1 will tell the routine to ignore where the mob is and just take off after the mob, so if the character takes off running across the zone to meet the mob on incoming then I would either modify the Condition to include more checks to keep the DPS1 entry from getting executed or pass a 0 and not a 1. If you pass a 0 then the routine will check if the mob is within MeleeDistance before moving the character into position.
I have never tested using a /call as part of a command entry, so this may not even work, but I can't see why it wouldn't.
The GetCombatPosition routine is called, just before the Combat routine is called. The message happens when either the Mob is still too far away(MeleeDistance) or the mobs HP are not low enough(AssitAt). So reducing your MeleeDistance could help. Once in the combat routine the stick routine is used to move melee characters into position(StickHow) and turn on stick and Attack. Non melee characters don't use the Stick routine.
You could try using a COMMAND: entry in the DPS section to get positioning when needed.
DPS1=Command:/call GetCombatPosition 1|99|Cond14
Cond14=${MyTargetID} && !${Spawn[${MyTargetID}].LineOfSight}
I would be very careful with this. The argument passed to the GetCombatPosition routine can be a 0 or 1. Passing a 1 will tell the routine to ignore where the mob is and just take off after the mob, so if the character takes off running across the zone to meet the mob on incoming then I would either modify the Condition to include more checks to keep the DPS1 entry from getting executed or pass a 0 and not a 1. If you pass a 0 then the routine will check if the mob is within MeleeDistance before moving the character into position.
I have never tested using a /call as part of a command entry, so this may not even work, but I can't see why it wouldn't.
drawthow
Well-known member
Never mind. Forgot to do a MQP on before the twist off.
same KA as above, all i did was change LOSBeforeCombat=0, ran it a couple times, and switched it back to =1 and now it wont engage for crap while on /chase. Half the time it just stands there and watches and does nothing, the other half its engaging somewhere between 70 and 1% life with autoattack on. Group moves, and it will follow, but not always engage in combat.
That is a symptom of your various distance settings not working well together. It's unfortunate, but those settings that work fine when you have a traditional "camp" location do not always work when you also factor in the chase distance you are away from your tank.
I usually run my tank semi-manually and when I engage while moving I will back my tank up closer to my group so they will engage correctly.
It could be a couple things. Post your ini file and I am sure we can find a fix.
@Myysterio Is your CampRadius Smaller than your MeleeDistance?
I have, its above. I made no changes.
Yes, but they are both like 200. I tried adjusting them both manually in game and nothing helped other than dragging the mob next to the bard.
Sorry, I must of scrolled past it. Make these changes in your melee and it should fix things. Yes, StickHow=Null will work
[Melee]
AssistAt=99
MeleeOn=1
FaceMobOn=1
MeleeDistance=75
StickHow=Null
If the character is attacking the mob when the mob comes into melee range, then the only thing I can think of is you need to make sure that CampRadius is less than MeleeDistance. If CampRadius is greater than or equal to MeleeDistance then the character will NOT move to the mob. That is by design, so check your settings. Just to test I would set CampRadius=35 and MeleeDistance=75 and increase MeleeDistance if needed. Another thing to consider is when you are in chase mode. When in chase mode the characters current .X, .Y, .Z is used as their Camp Location, and when checking if the character is ready to move to the mob, before attacking, is determined based on the Mobs position/distance from the MA. When the mobs is CampRadius close to the MA then the character should move to engage. When ReturnToCamp is on ChaseAssist should be off, and when ChaseAssist is on ReturnToCamp should be off. There is only one situation where both ReturnToCamp and ChaseAssist should both be off and that is when using the /waithere command. But never should both ReturnToCamp and ChaseAssist be on at the same time. If you are using the /waithere command. Then you should be using either the /chase or /camphere commands to recover.
Ive set campradius and melee distance as high as 400 and as low as 40 and it didn't solve my problem. spent about an hour messing with it yesterday.
When there's a camp set, its a bit slow to react, but it does what its supposed to do, it only does this on chase. On second thought it kinda does it when there's no camp set but you're not really going anywhere as well, but they are likely related.
Edit: Ive also noticed it wont stick most of the time even when it is attacking the mob, will stand right next to tank and not go to the rear.
Last edited:
Hmm. @Myysterio You mind getting me a debug log file so I can look at what is going on. Just PM the log to me.
drawthow
Well-known member
Every time I try to start kissassist I'm getting this type or error Undefined Variable mq used on line... The line number changes ever time I restart the macro. I will post a few examples. I have tried taking a few Bard ini files out of the repository and trying a few version I have in backup files nothing seem to help.
Attachments
this means you have *something* using "mq" as a variable like ${mq} --- this is often something in boxhud, or mq2hud or something else like that
drawthow
Well-known member
Should I be able to just stop the plugin and try running kissassist or will I need to re-log to do testing?
drawthow
Well-known member
I have the same issue and i dont have mq2custombinds on... not sure if someone did something automatically behind the scenes, but i still have the problem :/
