• 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 Release KissAssist 5.6 Updated 11/13/2012 (1 Viewer)

Is there a way to prevent buffing during combat? I recently started boxing a cleric, and typically, when one character dies, the cleric immediately rezes them (good) and then proceeds to buff them while ignoring other players who are in danger of dying (bad), which often leads to a wipe.
what version are you using? kiss can't buff in combat it checks for heals before casting each buff spell
 
are we now using kissassist 6.0? if so why has it become to hard to find and why are we still only seeing 5.6 on the forums do we need a new post to reflect that its 6.1 now?
 
what version are you using? kiss can't buff in combat it checks for heals before casting each buff spell

I'm still using 5.6. I'd seen a couple people have problems with 6.0, so I was waiting to make sure all the bugs were gone. Was the heal-before-buff feature in 5.6, too?
 
we are on 6.2, and it has been posted in the vanilla compile page, where you would have to go to download the compile anyways. 6.2 is pretty stable so far, in terms of what you are used to with 5.6.
 
are we now using kissassist 6.0? if so why has it become to hard to find and why are we still only seeing 5.6 on the forums do we need a new post to reflect that its 6.1 now?

I haven't written the new thread yet. Just haven't had time between work and mq2 being down for 4 days.i am out of town this week so won't be able to get to it until next weekend.

Most of the info is in the new compile thread.
 
we are on 6.2, and it has been posted in the vanilla compile page, where you would have to go to download the compile anyways. 6.2 is pretty stable so far, in terms of what you are used to with 5.6.

Can you link me the post to 6.2? I only see 6.1 listed, other than comments from Mask that 6.2 will be released soon. Furthermore, I make quite a few changes in the KA file, so I don't want to upgrade to something that will be updated in the next day or two; its just a waste of time. Thats the reason i'm still using 5.6.
 
Its 6.1. i gave a few people 6.2 to test but its not released.

Stick with what works for you now. I will be working on and releasing a lot of fixes over the next few weeks.
 
I've got a problem where my puller will get stuck in a wait loop if one of the party members has a familiar (maybe a pet?) out. He checks the familiar instead of the main party member and can never tell if they are rfp.

It happens when my warrior has his familiar out, and I think I found the culprit, though I need to test it. basically, around 2927 in CheckStats

Rich (BB code):
/if (${Spawn[${ckclass} ${charname}].Current${stat}}<${resume}) /goto :wait_for_resume
should be
Rich (BB code):
/if (${Spawn[${ckclass} ${cktype} ${charname}].Current${stat}}<${resume}) /goto :wait_for_resume

since the pet classes are warriors, the way it currently is could possibly check the pet if it is the pet of a warrior. I'm guessing not a lot of people use warriors in their groups. Basically, need to check for type as well.

EDIT: I tested it, it seems to work.
 
Last edited:
It seems that wasn't the only place a warrior tank mattered... line 743-ish in CombatCast

Rich (BB code):
/if (${DPSText.Arg[3,|].Find[MA]}) /varset DPSTargetID ${Spawn[${MainAssist}].ID}
should be
Rich (BB code):
/if (${DPSText.Arg[3,|].Find[MA]}) /varset DPSTargetID ${Spawn[${MainAssist} ${MainAssistType}].ID}

Was having a problem where the cleric was casting Shining Armor on the familiar when it was set up in the DPS=Spell|MA fashion. This fixed it.
 
How weird. I have a warrior but never use a familiar. Kiss will kill familiars on pet classes and wizzies. I'll check out the rest of the mac too. thanks for finding the bug red cented.

That kind of thing is why I included .Type in a lot of the targeting routines.
 
Any idea why a chanter would be starting the dps section before mezing? I could've sworn that in the past it mezed before it started dps. Both mobs arrive in camp at same time, and enchanter recognizes them, then does the first two dps lines before attempting to mez.
 
Only thing i can think of is mobs are just on the outside of your mez range but inside DPS range
 
Is your enchanter level range for mezes set properly? I had a camp that would rarely spawn a mob 1 level higher than the old range that I hadn't properly set when I leveled to the next level mez spells.
 
Is your enchanter level range for mezes set properly? I had a camp that would rarely spawn a mob 1 level higher than the old range that I hadn't properly set when I leveled to the next level mez spells.

Its happening multiple times, in multiple settings. Mob level and distance doesnt seem to be a factor...i dont normally pay much attention to what the enchanter does, because in the past its been nearly flawless at recognizing and mezing mobs immediately...now when i get two or more, im forced to play the tank and blow some discs to ensure i dont die. I'll try to watch more closely and see if i can notice whats happening to cause the delay in mezing.
 
I seem to be crashing whenever I set my tank to be puller or hunter. Hunter, worked better in that he detected an add in camp and killed it, then crashed. Puller just crashes as soon as I execute the macro.
 
KissAssist Release KissAssist 5.6 Updated 11/13/2012

Users who are viewing this thread

Back
Top
Cart