• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver
KissAssist

KissAssist Release KissAssist (3 Viewers) 12.002.039

No permission to download
@cotto8177 What character is your puller and what character is your tank? You can set your camp radius and meleedistance to be different values for each character. For your tank, to keep him/her from lunging out as a mob is incoming, just set your meleedistance to the same value as your campradius.

bard is my puller
CampRadius=55
MeleeDistance=55

i personally would love to see my War Pal SK throwing agro spells around 75ish farther when im in a good camp spot. but that would cause the moving isssue and makes "bot" movements obvious.


what i have noticed tho that MIGHT fight this issue is like KA11 have ambush used? could make it into an Exception cast with a custom range base on per user preference?
given as currently it will cast when using that tag anytime threw out the fight when placed in the agro section.
1589134136734.png

so would be something like
CampRadius=55
MeleeDistance=55
Ambush=75
 
Last edited:
I would just turn DPSMeter off on all the toons you are assisting with. Other thing you may not be aware of is you don't have to load the DPSAdv UI to use the DPSMeter that kissassist uses. All my toons that have DPSMeter turned on. Do not load the UI, because I agree that you don't need anymore windows open with everything already open.
And that is the problem, it is never loaded but if I start kiss12 up with dpsmeter=1 it somehow loads it....
 
I just started using the new version of Kiss12 this morning getting some errors/spam in the mq2window.

1589548436809.png
 
Hmmm. I am not getting that error from the AECheck routine. What is your ${MacroQuest.Parser} returning?

Anyone else having this issue?
 
Hmmm. I am not getting that error from the AECheck routine. What is your ${MacroQuest.Parser} returning?

Anyone else having this issue?

I'm running the latest beta and not having any sort of similar problems. Just did the GD mission where I had 8 wolves on extended target and it was smooth as a baby's behind!
 
Hmmm. I am not getting that error from the AECheck routine. What is your ${MacroQuest.Parser} returning?

Anyone else having this issue?
When I'm just sitting in the zone ${MacroQuest.Parser} returns a 1.

Got this on both my war and sk doing the GD missions BigDaddy mentioned. It's also happening on my SK in the TBL FIght Fire missions
 
If it's on Test and you have that character on Live, I would see if it's an issue on Live, but that specific error (MQ2Data portion 'Spawn') looks like it might be an issue with MQ2. There was a particularly large patch to Test, so possible there are errors shaking out. That's eqmule's territory so he'd be the best one to look.
 
I have a question regarding Mage pet toys at high levels. The only thing my level 115 pet will take is a pair of weapons. However I also like to give a full set of gear to the other non-mage pets in my group (sk, chanter, shammy).

In order to do that I need to define the plate armor and the trinkets in the mage's INI file. But then the macro insists on trying to give my mage pet all those things which the pet rejects with a message in /say. It looks really bad to be standing next to the mage handing those out one by one and the pet giving a rejection message for each and every item. It's a sure marker of KA usage. Not to mention it takes a long time to fully equip a pet like this.

So my question is, how can I configure the macro or INI file give non-mage pets a full complement of gear but have my own mage pet only receive the pair of weapons it will accept? I currently handle the non-mage pets the old fashioned way... manually!
 
@B_I_G__D_A_D_D_Y in kiss 11.5 you can't. But the new beta version you can use conditions in the PetToys routine.

The PetToys routine requires a pet name to be passed to it that you can use in your conditions. Use ${petName} in your conditions. Here is an example: ${Me.Pet.CleanName.Equal[${petName}]}


As all other sections that use conditions add the |cond to the end of the entry.
 
@B_I_G__D_A_D_D_Y in kiss 11.5 you can't. But the new beta version you can use conditions in the PetToys routine.

The PetToys routine requires a pet name to be passed to it that you can use in your conditions. Use ${petName} in your conditions. Here is an example: ${Me.Pet.CleanName.Equal[${petName}]}

As all other sections that use conditions add the |cond to the end of the entry.

Sounds like a straightforward thing to check if the pet is NOT mine. However it appears that ${petName} is an internal temporary variable and KA will not initialize with that line in my Conditions. So I added it to the Declare.Outers section as a test and then the macro would run and initialize but it screwed up the actual ability to hand the items to the pet. (It made the items but then dropped them into the mage's inventory rather than handing them out.)

Please don't worry about this now, I know you've got something planned for "begging" pet toys directly from the other characters.
 
I just started a Bard and I wanted to say that the new MeleeTwistOn=2 option is pretty freaking great. Thanks for adding it. (Man, Bards are weird from a macro perspective...)
 
Autorezz fell into infinite loop using the following lines:

Heals13=Call of the Wild|0|rezcombat
Heals14=Rejuvenation of Spirit|0|rezooc
AutoRezOn=1

Description:
Had the puller die while pulling, but group got aggro, because healer attempted to save the puller.
So the situation was:
  • Puller dead
  • mobs in camp

mq2-window was flooded with messages about the healers impossibillity to summon the corpse of the puller to rezz him ... but no heals

suggestet change: some exit strategy (maybe counter for max attempts to summon the corpse) for the macro for the case, the corpse can't be summonned to leave the corpse alone and proceed with healing of the living groupmembers

My Workaround for now: AutoRezOn=0

Using KA12 for serveral weeks now and this is the first time, I found something I would like to be changed.
 
Was the role puller or pullertank?

I can't find any code that locks the rezzer in the rez routine. There is no loop that keeps the rezzer trying over and over again. it tries to rez then leaves. Can you post the heal section of your healer.

Also was the puller in the same zone as the healer when they were trying to rez?
 
I found where it could be possible if a group member was to far away to be healed and was the most hurt in the group. That would keep the healer from casting any heals on the rest of the members.
 
Mage kept trying to buff someone else pet after I sent /pettoysplz
Summons weapons gives it
Summons Mask give it
repeats

Stopped it after 4 times.
 
@jande are you using /bct MageName //pettoysplz PetName from the pets owner? If you could paste what command you are using. I can't replicate that error.
 
yup thats what I did /bct MageName //pettoysplz PetName

mmm I do it incorrectl first /bct MageName //pettoysplze PetName then the correct command
wonder if that is the problem.

It stopped after the 3rd time summon/giving this time.
 
Try /bct MageName //pettoysplz ${Me.Pet.Name} and see what happens, it should only give the toys one time, even if the pet gives them back.
 
Was the role puller or pullertank?

I can't find any code that locks the rezzer in the rez routine. There is no loop that keeps the rezzer trying over and over again. it tries to rez then leaves. Can you post the heal section of your healer.

Also was the puller in the same zone as the healer when they were trying to rez?
Role was Tank, and died maybe 3 feets to far, to be summoned. After the fight I had to Do just a viw steps to be able, to summon him. The loop was already the attempt to summon, there was a flood of messages like 'to far to be summoned'

Thank yo for checking the case. Next time I am at PC, i,'ll Post the heal section.
 
I have a question it concerns the buff section of the KA_Mytoon.ini file. (Lead in) I have a group that has 2 characters that can cast similar type spells. Example: Damage shields. One can cast Shield of Brambles and the other casts Shield of Flame. I know that Brambles is dominant spell in this case and Flame will not stick. My question is: Can I have Brambles cast on the MA (stronger DS) and have Flame cast on the rest of the group? Also while defining the buff I can make the buff cast on MA but can I use !MA to not have it cast on him or do I need to make a condition and set it up there?

The reason is to try not to duplicate casting the same type of spells and having on caster keep trying to cast a spell that will not stick. I have seen this happen with shield spells. Some classes have their own shield spell and healer has better shield spell. The healer spell will over right the individual shield spell if it is better. Example: Druid, Shaman and Magician. Druid is for porting. Shaman is for buffs. Magician is for DPS and pets. But there are overlapping spells that one is better than the other.

Druid and Magician both have damage shields but the druid is the better. (at this low level and mana is also not great). Druid and Shaman have heal spells and speed spells. But again one spell is stronger than the other at the same Level of character. So what I am trying to do is have one (druid) cast the best damage shield on the MA and have Mage cast his damage shield on the rest of the group. Thus saving mana on the druid for the better heal and have shaman cast the lower heal or little heal before the druid has to use the bigger heal.
 
identified an issue, just started trying the 12 beta so not sure if I did something wrong.

I just installed 12 beta over previous 11. same ini files.
When I hit group button to send KA start:
/dgge /mac kissassist war 99

my toons are setup "war", and "war"healer

all my toons are showing MA is "war"healer

i.e. same first part of name but additional letters tacked on. I noticed same issue when i first starting using MQ2. my old habit of /autofollow for toons would default to clerics name. Not sure if this working as intended or if I don't understand some key issue.
 
Here the Healer section of the shaman:
INI:
[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=1
Heals1=NULL
Heals2=Zrelik's Recourse|99|Cond10
Heals3=Primordial Intervention|56
Heals4=Reckless Renewal|65
Heals5=Reckless Rejuvenation|63
Heals6=Ancestral Aid|60|MA|weave
Heals7=Union of Spirits|52|MA|weave
Heals8=Soothsayers's Intervention|55
Heals9=Spectre of Renewal|96|Cond13
Heals10=Reckless Regeneration|61
Heals11=Spirit Guardian|49|Me
Heals12=Ancestral Guard|45|Me
Heals13=Call of the Wild|0|rezcombat
Heals14=Rejuvenation of Spirit|0|rezooc
AutoRezOn=0
Heals15=NULL
XTarHeal=0
HealGroupPetsOn=1
HealsSize=15
XTarHealList=Xtar slots here Example: 5|6|7

As you made already a modification, I'll switch AutoRezOn=1 and report back, when it happens again.

Tyvm
 
identified an issue, just started trying the 12 beta so not sure if I did something wrong.

I just installed 12 beta over previous 11. same ini files.
When I hit group button to send KA start:
/dgge /mac kissassist war 99

my toons are setup "war", and "war"healer

all my toons are showing MA is "war"healer

i.e. same first part of name but additional letters tacked on. I noticed same issue when i first starting using MQ2. my old habit of /autofollow for toons would default to clerics name. Not sure if this working as intended or if I don't understand some key issue.

I'm not sure what the "/dgge" command signifies, but here's a solution using the older EQBC service..

Easiest fix would be to have your chars target your MA first, then run Kissassist. As in

/pause 3, /bcga //tar "War"
/bcga //mac kissassist
 
My question is: Can I have Brambles cast on the MA (stronger DS) and have Flame cast on the rest of the group? Also while defining the buff I can make the buff cast on MA but can I use !MA to not have it cast on him or do I need to make a condition and set it up there?

Yeah, this definitely works. Just do |MA and |!MA like you described in the various characters' buff sections. I've got something similar in my setup. I'm not clear whether this works with class descriptors or melee/caster groups, but it definitely works with MA. (Update: !me is not a thing that works.)
 
Last edited:
with autorezz on = 1 new behavior
Situation:
during a fight the tank died, due to overpull ... but offtank took over and fight went on
behavior:
Tank's corpse is targeted but not called ... after some seconds some heals to other groupmember, than target back to corpse ... this went like that for 4-5 times before I clicked "Call of the Wild" manually
but even after that, with living tank in group and his corpse in camp the shaman continued to target the corpse about half of the fighting time (I presume attempting to rez/call the corpse), while any couple of secondes he shot some heals into the group

so as far as I can say:
  • "Heals13=Call of the Wild|0|rezcombat" is not operated, corpse is targeted but aa: "Call of the wild" not cast
  • "Heals13=Call of the Wild|0|rezcombat" is not aware that no combatrez may initiated, if char who belongs to corpse is as well alive in group (caused by call of the wild or other priests call)
 
Next time that happens can you get me a debug log please. Just set up a hot key with /debug all on log. Use /debug all off to stop the logging.

In the rez routine the MA's corpse is targeted just before the castwhat routine is called. Except in the group check routine, it targets the corpse and then checks the corpse distance. The corpse has to be within 100 units or there is no rez cast.
 
I'll do that. In this last situation the tank has died in camp, so less than 5 feet away from shaman. So distance shouldn't have been a cause. Just to be sure I had described the situation right.
 
Hi, my cleric sometimes try to sit down with medcombat=1, despite having aggro; resulting in critical hits. As far as I can see line 3675 is doing this:

INI:
        /if (${MedCombat} && !${Medding} && ${AggroTargetID}!=0 && ${AggroTargetID}==${MyTargetID}) /return

If i read this correctly, the problem is that if the character has agro while it's NOT his targetID..it will try to sit down again; my suggestion would be to remove the last part:

INI:
        /if (${MedCombat} && !${Medding} && ${AggroTargetID}!=0 /return

or perhaps include GotHit variable somehow?
 
Last edited:
Setting MedCombat=1 tells the med routine to med while in combat. If you don't want your cleric to med during combat set MedCombat=0

Thats obvious but not what the problem is, the problem is that the check routine to decide "should we meditate right now" doesnt take into account that you can have agro but it not be your targetID, resulting in constantly trying to sit, being critical hit, stand, trying to sit, etc., etc. As in, you want to med in combat, but not while you're having agro.
 
KissAssist Release KissAssist

Users who are viewing this thread

Back
Top
Cart