• 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
Kiss10 (old version of KissAssist)

KissAssist Release Kiss10 (old version of KissAssist) 10.2.6

No permission to download
Re: KissAssist v10.2.4 Released 02/04/2018

Yep, that's not a Kiss error, but normally something to do with a bad /aliase.

Yea, I figured... appreciate the assistance, though. Sorry to co-opt your support thread.

Having a similar error for other variables, too. Bah, wonky crap. I'm just gonna try doing a fresh install. I think I know what the issue is (or at least what started it) ... but no idea how to unfuck it in a piecemeal fashion right now.

- - - Updated - - -

Well, that didn't entirely fix my issue. There's other stuff going on. I think I messed up the macro folder and/or config files by doing a copy and paste job from one compile over to the RG compile. I've shifted 100% to RG compile, and something in the other configs/.inc files is messing shit up over here. I doubt I'll get much sympathy over here for that mistake lol.. but alas.
 
Re: KissAssist v10.2.5 Released 02/25/2018

I have my sk as pullertank. when i /mac kissassist he sits there until i manually pull a mob. once the mob is dead he takes forever to find a mob and pull. i have my same ini as i had in the previous kissassist.
 
Re: KissAssist v10.2.5 Released 02/25/2018

Rich (BB code):
/mac kissassist pullertank
 
Re: KissAssist v10.2.5 Released 02/25/2018

Hi guys, So do I need to install the KissAssist or does it eventually get put in with the Updater? I'm new so have no idea.. I'm on 10.2.3 and I keep running the update thing, but nothing happens. So if I install this, and run the Vanilla, does it automatically update the character.ini files to 10.2.5? Do I need to recreate those ini files? Any help is appreciated. Stil new and enjoying my Subscription..love playing EQ this way.
 
Re: KissAssist v10.2.5 Released 02/25/2018

We release kiss upates often. So the updater doesn,t always have the latest. It's a good idea to check here and then just copy over the one in your macro folder.
 
Re: KissAssist v10.2.5 Released 02/25/2018

Anyone else having issues with toons buffing nearby out of group guild mates using this version? In the past the toons would buff anyone in the vicinity, but that behavior is not happening anymore.

Thanks!
 
Re: KissAssist v10.2.5 Released 02/25/2018

Kiss should never buff anyone out of group unless those toons are being run on your computer.
 
Re: KissAssist v10.2.5 Released 02/25/2018

Heya, Tried searching but just pulls up every post that says target in it.

Where do I find Extended Target Window file?
 
Re: KissAssist v10.2.5 Released 02/25/2018

Kiss should never buff anyone out of group unless those toons are being run on your computer.

They are. I have 12-15 accounts running at any given time. The enc doesn't buff out of group, guilded toons running on the same comp and killing in the same camp. Is there an .ini setting that might be out of whack? I couldn't find one, but you're the expert!
 
Re: KissAssist v10.2.5 Released 02/25/2018

well if they being run on the same computer, and all using kissassist but in different groups they should be buffing each other cross group right? cause htey will all be using the kissassist_buff.ini
 
Re: KissAssist v10.2.5 Released 02/25/2018

Not sure if this is by design or if I am doing something wrong. Plus, I do not code by any means, so pardon my extreme newbness in this regard.

I noticed that if a character is casting an INI defined buffed, where that character has the spell blocked, that characters recasts the spell over and over. For example, I block haste on my enchanter, but some other group members do not. My cleric has it blocked as well. But, its not until I remove the spell from the Enchanter's Block List where the loop stops.

So in my mind, I want to say that the Block itself isn't the issue (since the CLR and MAG block it), but it's the combination of the block plus the character casting.

Is this on purpose? Not a big deal, just an observation.
 
Re: KissAssist v10.2.5 Released 02/25/2018

I guess this is a bug. In Howling Stones, it considers Arisen bones to be a named, when they are trash mobs.
 
Re: KissAssist v10.2.5 Released 02/25/2018

I guess this is a bug. In Howling Stones, it considers Arisen bones to be a named, when they are trash mobs.

Unfortunately, there are a few instances like this scattered through the various expansions.. Makes it tough when you're camping that ooze named in the basement in Howling though.. When you burn every single spawn LOL
 
Re: KissAssist v10.2.5 Released 02/25/2018

I'm no expert but it would seem really obvious for the named mob check to check against the spawn master ini file rather than checking for italics.
 
Re: KissAssist v10.2.5 Released 02/25/2018

for the burn issue of it not knowing which mobs to burn in certain zones, there is a simple solution.

i personally dont have burnallnamed on, as i dont play afk. and issue my burn command when i need it.
but if you dont want to do that use the kissassist_info.ini file:
Rich (BB code):
[beastdomain]
MezImmune=List up to 10 mobs. Use full names i.e. a green snake,a blue tiger,a wide eye ooze or NULL
MobsToPull=filthy ape
MobsToIgnore=List up to 25 mobs. Use full names i.e. a green snake,a blue tiger,a wide eye ooze or NULL
MobsToBurn=List up to 10 mobs. Use full names i.e. Beget Cube,Helias,Raze or NULL
PullPath=Place holder for path file. Not yet impletmented.
here you can add the full name of the mobs to burn on, and you wont waste a burn on maybe names or similar to named sounding mobs.

for buffing, kiss wont buff anyone unless told to, and specially not people not running kiss and on the same computer as the buffer, if it does then i suggest you check if you have some plugsin that conflict, like downshits in mq2melee, or afheal etc,
 
Re: KissAssist v10.2.5 Released 02/25/2018

Not sure if this is by design or if I am doing something wrong. Plus, I do not code by any means, so pardon my extreme newbness in this regard.

I noticed that if a character is casting an INI defined buffed, where that character has the spell blocked, that characters recasts the spell over and over. For example, I block haste on my enchanter, but some other group members do not. My cleric has it blocked as well. But, its not until I remove the spell from the Enchanter's Block List where the loop stops.

So in my mind, I want to say that the Block itself isn't the issue (since the CLR and MAG block it), but it's the combination of the block plus the character casting.

Is this on purpose? Not a big deal, just an observation.

If you are casting a group buff. Kiss checks if the caster does NOT have the buff first, and if you do NOT have the buff it will cast the Buff, So yes blocking the buff on the caster will not work when using KA..
 
Re: KissAssist v10.2.5 Released 02/25/2018

In my group with a Druid healer, the puller will hang in a loop if they have a corpse in camp. The puller starts to look for mobs, sees the corpse, tries to pull it back "to camp." However since the Druid is using the combat no-exp rez, the puller never automatically gets a rez that erases the corpse, so the puller loops on targeting the same corpse.

Is there an option to use the out-of-combat Druid/Sham 96% rez? Or turn off the puller's corpse drag option? Thanks.
 
Re: KissAssist v10.2.5 Released 02/25/2018

I use my shaman to rez all the time, just make sure you have the shaman setup to rez and the puller is setup to except 96% rezzes. Set RezAcceptOn=1|96 on your puller.
 
Re: KissAssist v10.2.5 Released 02/25/2018

i believe what is happening is that you have set ka to use the druids combat rez, so he will do that, but not use a proper rez since he dont know how to do that.

so you gotta make a choice do you want the combat rez or the out of combat proper rez?
 
Re: KissAssist v10.2.5 Released 02/25/2018

Heads Up!

Here are some of the changes coming to the next version of KissAssist.

Rich (BB code):
Gmail Now has an option for Tells.

The CastMount routine will now use condition checks. So if you created a condition for your Mount buff entry, 
it will now check the condition before casting your mount.

Rezall switches added /rezallon and /rezalloff
    Rezzers will try to rez a corpse 3 times, then add the corpse to the not to rez list. Turning rezall off will reset the not to rez list.
    Note: All other rezzing still works the same. If there is a corpse that is a member of your group, Fellowship, and/or Guild.
          there is no limit on the number of times they will try and be rezzed.
          
You can now have multiple items to rez with.
    AutoRezWith: AA/Spell/Item    
    AutoRezWithSec: AA/Spell/Item    
    AutoRezWithThd: AA/Spell/Item    
    
/Stayhere alias added. So now you have 3 aliases to use when dragging your group around the zone(s).
    use /camphere to set camp at current location, and stop chasing.
    Use /chase to abort camp and start following.
    Use /stayhere to stop following, but don't make camp and just stay put where you are.

Added Before Combat check that allows for an action to be executed before turning on /attack.
    Use the ambush tag at the end of your DPS entry to add this to the BeforeArray. Works with conditions.
    
    Allows 5 entries and is used like so:
        DPS1=Moving Mountains|100|ambush
        DPS2=Slap in the face|95|ambush
        
XTarget Healing has been changed. You can now use all XTarget entrys as heal targets.
    XTarget Healing options:
    XTarHeal=0:
        Will Heal Self, MainAssist, and Group. XTargets are ignored.
    XTarHeal=1:
        Will Heal Self, MainAssist, Group and XTargets
    XTarHeal=2:
        Will Heal Self, MainAssist, and XTargets. Ignores the Group.

    To set what XTargets to check for heals, set:
        XTarHealList=1
            This will check the first XTarget only.
        XTarHealList=1|2
            This will check the first and Second XTarget.
        XTarHealList=1|3|5|7
            This will check the first, third, fifth, AND seventh XTarget.
        XTarHealList=all
            This will try and use every XTarget.
            
    Note: When using XTargets for healing, XTargets will be checked for Rezzing as well.
    Note: You should have all your XTargets setup before starting Kissassist, and if you add or remove entries to your XTarget window, 
          you will need to restart kissassist
            

Made changes to how stick is used in Combat.
    If you have UseMQ2Melee turned on then you will need to setup MQ2Melee stick commands. 
    Kiss will not use /stick commands in combat if you have MQ2Melee turned on.
    
    StickHow=0:
        Will use the /stick id ${Target.ID} command so you will have to tweak the MQ2MoveUtils settings for /stick.
        
    StickHow=yourstickoptions:
        will issue the /stick ${Target.MaxRangeTo} id ${Target.ID} ${StickHow} command.
        Note: Kiss will try and use Max melee distance, so if you want to close the gap/get closser to the mob use the % option in your StickHow option.
            Example: StickHow=MoveBack 50% loose. This will move you back to 50% of targets MAX radius using loose movements.         
    Note: If durring Combat, you are to close to a mob, and can't see it. Kiss will try and back you up a bit untill you can see the mob. 

DPS, and Burn got a command Tag added.
    The new command tag has 2 paramaters and can be used as follows:
    DPS1=command|Param1|Param2
    
        Param2 is optional but Param1 is the command itself withOUT the /. Param2 would be used if the command itself required a paramter.
        
    This can also be used with the mash, weave, and ambush tags. But the mash, weave, and ambush tag must be the last tag on the entry.
        
    DPS1=command|stopdisc|ambush
    DPS2=command|removebuff|levitation
    DPS3=command|stopdisc|mash
    
    Note: The command tag is not setup to use ${Variables} in any of the paramaters. Conditionals apply
          

    
Added Mass Group Buffing.
    Uses Tranquil Blessing AA Not Mass Group Buff AA.
    Will Not cast Group only spells(Group_V1).
    You have to be in active or resting combat state.
    
Lootstuff routine now checks if MQ2Autoloot Plugin is loaded and active. Will allow Autoloot plugin to handle looting.

Added code that helps to keep GOM from hijacking heals and mezzing.

Clerics that are non-DPS will now burn named if BurnAllNamed is on.

Looking for a few people who will help beta test this version. Please PM me if you are willing to do some testing.

Thanks in advance.
 
Re: KissAssist v10.2.5 Released 02/25/2018

count me in, I need to get my beta back on
 
OK guys and gals, KissAssist 10.2.6 has been released.

I want to give a Special thanks to Kaen01 for all his help during the Beta testing phase. :dance:
Also Razkle swooped in at the last minute and helped out, so thanks for all the help.

OKAY! You know what to do. :woop:
 
Stupid question here I am sure, but I gotta ask. I assume EQMule, if he is so inclined and has time has to update his version to include these updates? I am not real sure how you guys do this.
 
Stupid question here I am sure, but I gotta ask. I assume EQMule, if he is so inclined and has time has to update his version to include these updates? I am not real sure how you guys do this.

He'll probably say something like his version is already stable and does things similar to this one. In the past his versions didn't really require huge updates because he makes any small changes as necessary and updates the main RG updater.
 
He'll probably say something like his version is already stable and does things similar to this one. In the past his versions didn't really require huge updates because he makes any small changes as necessary and updates the main RG updater.

What about Xtarget Healing? This version of kiss has redefined power-leveling with a healer outside of group.
 
What about Xtarget Healing? This version of kiss has redefined power-leveling with a healer outside of group.

True, although I found if you just assign xtargets to your individual toons it seemed to work. Not sure if that was intended or just lucky.
 
Hmm, ok the new version must have different starting arguments? My group setup hotkey is basically this...

/bct tank //mac kissassist mage

This has worked for the last 8 months but now all of my toons are giving the error "you have >> null << targeted. bla bla

Suggestions? for alternate ways to tell a group who to assist without having them target specific people?

/edit1
I am also getting some odd messages when starting kisassist 10.2.6.
on sham at start of KA
[MQ2] Using MoveUtil to move with Turgur's Swarm

/edit2
all of my toons are spamming the mq2 window with messages like.
'Chaotic Inferno' is not ready! when it clearly is ready and can be triggered with hotkey and mouse.
I am using the latest version of MQ2, just ran the patcher and it says I am up to date.

/edit3
did a report on my problems here.
https://www.redguides.com/community...nged-and-other-odd-things?p=359393#post359393
 
Last edited:
Wow that is a big code diff between 10.2.5 -> 10.2.6! :eek:

One undocumented thing I spotted as part of my merge is that you added support for MedCombat=2 (to sit you down after casting in combat). Thanks very much for adding that into the official release (I imagine you'll want to update the guide?). The default value of 6s for the SitToMedTimer might be a tad high? I have my guys sitting straight back down immediately after casting to get every med tick possible!
 
Last edited:
Noticed a bug (or my bad settings). Gift of Chromatic Haze, also fires as "gift of Mana" as far as the kissassist.ini. Anything you put under gift of mana will fire when the enchanter AA Gift of Chromatic Haze goes off (To include the AA Chromatic Haze). I fixed this with conditions to check the song window for Gift of Mana.

Side note. Love this, thank you.
 
6s was chosen because its a combat round and gives tanks time to get aggro say if the mob is hitting the chanter.
so its one tick that he waits to sit down, which for my testing purpose made the difference between running lom all the time on chanter, to being able to pull for 6 hours with no medding.

prior to 6s i had it at 12s, but that was too much for sure.

i suppose 3s would be aight too, but just felt it was more right with one combat tick.

but you know where to change it so can do that.

the reason why it wasnt announced with release currently, was that i kept having issues with my chanter and cleric not doing their job proper, if i had medcombat=2 if i took out the checks, and just used it hardcoded with medcombat=0 it worked flawlessly, so i think ctaylor wanted to give it a few more tests himself before annoucing it.




Wow that is a big code diff between 10.2.5 -> 10.2.6! :eek:

One undocumented thing I spotted as part of my merge is that you added support for MedCombat=2 (to sit you down after casting in combat). Thanks very much for adding that into the official release (I imagine you'll want to update the guide?). The default value of 6s for the SitToMedTimer might be a tad high? I have my guys sitting straight back down immediately after casting to get every med tick possible!
 
the reason why it wasnt announced with release currently, was that i kept having issues with my chanter and cleric not doing their job proper, if i had medcombat=2 if i took out the checks, and just used it hardcoded with medcombat=0 it worked flawlessly, so i think ctaylor wanted to give it a few more tests himself before annoucing it.

I'll give it a test too and let you know if I spot anything! This implementation is almost identical to what I've been running with for the last few weeks so hopefully it shouldn't be related to this feature.
 
Is there a new way to use //switchnow? With new version it doesn't do anything.

There was a check added if you are the MainAssist to just exit the routine. Why would the Mainassist need to Switch Targets? Also check your /aliases and make sure you don't have a /switch and/or /switchnow aliase. /switchnow is a bind.
 
Rich (BB code):
/if (${Timer.Equal[SitToMedTimer]}) {
   /if (!${MeleeOn} && ${Me.Standing} && ${MedCombat}==2 && !${Me.Mount.ID} && !${Me.Casting.ID} && ${Me.TargetOfTarget.ID} != ${Me.ID}) /sit
}

I'd recommend the ${Me.TargetOfTarget.ID} != ${Me.ID} check is removed, else a healer won't sit down after healing themselves, or an ench wont sit down after mezzing a mob (which has them targeted).
 
KissAssist Release Kiss10 (old version of KissAssist)

Users who are viewing this thread

Back
Top
Cart