• 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 (1 Viewer) 12.002.039

No permission to download
Join us with Level 2 access RedCents
Overview Commands Instructions Updates (69) Reviews (5) History Discussion
Is there a way to delay med somehow? Often, the macro will have me sitting to regain endurance. I want to use a clickly, but KA sits me down instantly, interrupting the spell.
 
OK, have setup a new group playing around so can have some of the other non-CWTNs except for Rogue, who is LDR and set as puller and uses puller assist. Rogue works fine. Druid, Necro, Ranger all seem to work fine, they assisting even though Pally just stands there doing nothing... Ranger seems to be doing Pally's job, he taunts and tanks. Ranger is set to assist Pally who is MT and MA, role is also set as Tank in ini. So 2 questions, how do i stop ranger from Taunting as it's not in his .ini. And where do I look for the setting to correct Pally to start Tanking... note this is low level group under 5 just started so the .inis are very basic.

1619927368585.png
1619928182723.png
 
Last edited:
You don't want to use the Tank role on any melee characters that are assisting the MA(Pally) The Pally should be set as Tank. When you start kiss make sure all your characters are targeting the MA(Pally).
 
raw said:
Is there a way to delay med somehow? Often, the macro will have me sitting to regain endurance. I want to use a clickly, but KA sits me down instantly, interrupting the spell.
Click to expand...

In this situation it is easier to just /mqp to pause the macro, then use your item, and then /mqp to get the macro running again.
 
ctaylor22 said:
You don't want to use the Tank role on any melee characters that are assisting the MA(Pally) The Pally should be set as Tank. When you start kiss make sure all your characters are targeting the MA(Pally).
Click to expand...

the SS are from pally, Pally was the MA, was using one of Sic's hotkeys for the Kissassist startup. Rogue was group leader and pullerassist. Was trying to run the group from the Rogue as Rogue uses CWTN all the others are KA toons. All seemed to be working except the Tank wasn't doing anything, was stuck in a loop, not targeting or attacking... Mob was already incoming at below assist value usually so the assists were assisting a non-tanking tank. I have since had to change this due to the Chase hotkey not working with rogue in the group leader. It seems Tank has to be group leader, which makees sense as chase works with the MA. Am i missing something with the roll modes for KA or did i imagine reading this.
 
Friends,

KA12 character with chaseon failing to begin DPS / AE sections. captured debug in MQ2 window (sadly didn't have /mlog on). will move to next mob but not engage.

thoughts
1620012848863.png
 
@Hylander Set your CombatRadius up some. The Distance of the mob has to be less than CombatRadius. Distance to Mob was 28.84 and your CombatRadius is at 23. Set CombatRadius to like 35 and see if that helps.

There was an issue with distance from camp that was found, but I am not sure if that fix made it into the current production version of kiss. Try making the suggested change and let me know.
 
CT,

23 is interesting.. i'd never set my campradius to that value. My Kiss INI looks like this
1620081675933.png

23 is suspiciously like half of 45, but my StickHow is
1620081737727.png

None of the above refer to CombatRadius ... is it something in MoveUtils ?
 
@Hylander

CombatRadius is a calculated field it should always be the same as or greater than MeleeDistance

${If[${Spawn[id ${MyTargetID}].MaxRangeTo}>${MeleeDistance},${Math.Calc[${Spawn[id ${MyTargetID}].MaxRangeTo}+5]},${MeleeDistance}]}

The other thing that I noticed, is your CampRadius is larger than your MeleeDistance. Kiss is designed for the CampRadius to be less than or equal to MeleeDistance. So I would change that around.

One more thing to be aware of. If MeleeDistance is equal to or less than CampRadius, then all the movement/stick code, to move your melee characters to the mob is ignored. This is so you can control your melee characters from running(Lunging) out to meet the mob and allowing for you to manually move your melee characters without having to fight the macro for positioning.

So just make sure your MeleeDistance is 1 more than your CampRadius. I would bump my CampRadius down to 35 and move my MeleeDistance to 45. If you need to keep your CampRadius at 45 then set your MeleeDistance to 46.
 
Draknocht said:
the SS are from pally, Pally was the MA, was using one of Sic's hotkeys for the Kissassist startup. Rogue was group leader and pullerassist. Was trying to run the group from the Rogue as Rogue uses CWTN all the others are KA toons. All seemed to be working except the Tank wasn't doing anything, was stuck in a loop, not targeting or attacking... Mob was already incoming at below assist value usually so the assists were assisting a non-tanking tank. I have since had to change this due to the Chase hotkey not working with rogue in the group leader. It seems Tank has to be group leader, which makees sense as chase works with the MA. Am i missing something with the roll modes for KA or did i imagine reading this.
Click to expand...

Still looking for some help on this. I have stripped the ini. to eliminate any problems with it. Pally is set to be MA, Rogue is set to Pullerassist (using CWTN) I use SIC's hotkey to start kissassist. Group is setup using autogroup. Rogue is Group Leader and puller. Pally is set to Tank, MA, and Looter. The issue is in the targeting when MOB comes into campradius, Pally doesn't auto target and attack. if i spam targeting and attack i can eventually get Pally to target & attack (target is usually flashing, see above for the debug pic i showed) but seems to not run the aggro sequence as she never taunts, but she does bash.
 
Please disregard issue was in the hotkey... was using bcga when should of been bcg. It was causing Pally to try and assist herself. :bang: :bang: :bang: :shrug:
 
Having some issues with Buff flags... Pet not getting buffed using |Pet, also Rog CWTN not getting the Buffed when using |Melee.
 
Bug report here with KA Cure section. Heads up that this is a very specific, and a bit of a niche scenario, but I don't have the ability to test on anyone else but the toon I currently have loaded. Here's the setup:
On the TLP Rizlona server, if you have a shammy who has remove greater curse, but does not have remove curse (not sure if that's significant or not, but it's my current scenario), and you put a "Cure6=Remove Curse|curse" line into your ini, (number of cure line irrelevant, just here as an example) it will cause the vast majority of the other sections of the macro to cease functioning. It took me almost 3 weeks to figure out what was happening, but my shammy would melee some times, but not always, occasionally buff some of her buff spells (usually not all), but would not DPS spell cast or Burn anything. As soon as I removed that line from the ini or commented it out, she returns to her normal buff/melee/dps routines without any issues. Debug mode was no help either. I ended up tracing it down by building a new INI from scratch by hand, and re-entering line by line until I found the one that broke it.
 
Why would you use Remove Curse if you don't have it?

[Cures]
CuresOn=1
CuresSize=1
Cures1=Remove Greater Curse

This works fine for me.
 
Because, out of my 18 toons all of the clerics have it, and I thought the shammy did too, so when I edited her ini, I added the spell. Ultimate this just highlights that the cure section doesn't check for the presence of a spell in your spellbook like elsewhere, or alternatively ignore a mistype. It can certainly confuse someone if they add a spell that doesn't exist to the curse section, and then not understand why nothing works right. It's one thing if it ignores a line for a spell it can't find, ergo a commented spell in your DPS section, but to just break the entire macro? That seems like a bit of an issue to me, which is why I brought it up.
 
@toadwart. Are you not getting the ...ERROR: ????? unable to find as a AA, Combat Ability, Item, Skill, or Spell when you start up Kiss? You should be seeing an error telling you you don't have the "Remove Curse" spell.
 
toadwart said:
Bug report here with KA Cure section. Heads up that this is a very specific, and a bit of a niche scenario, but I don't have the ability to test on anyone else but the toon I currently have loaded. Here's the setup:
On the TLP Rizlona server, if you have a shammy who has remove greater curse, but does not have remove curse (not sure if that's significant or not, but it's my current scenario), and you put a "Cure6=Remove Curse|curse" line into your ini, (number of cure line irrelevant, just here as an example) it will cause the vast majority of the other sections of the macro to cease functioning. It took me almost 3 weeks to figure out what was happening, but my shammy would melee some times, but not always, occasionally buff some of her buff spells (usually not all), but would not DPS spell cast or Burn anything. As soon as I removed that line from the ini or commented it out, she returns to her normal buff/melee/dps routines without any issues. Debug mode was no help either. I ended up tracing it down by building a new INI from scratch by hand, and re-entering line by line until I found the one that broke it.
Click to expand...

Cures have been a problem for quite some time. KA will run much better with Cures=0 and then build mq2reacts for the very few specific things you need to cure.
 
ctaylor22 said:
@toadwart. Are you not getting the ...ERROR: ????? unable to find as a AA, Combat Ability, Item, Skill, or Spell when you start up Kiss? You should be seeing an error telling you you don't have the "Remove Curse" spell.
Click to expand...
No, it reports nothing whatsoever, it just starts partially running KA basically in an erratic fashion, picking and choosing what it wants to work. I got keyed into it when my parses while running my 18 boxes consistently showed the shammy parsing below 15 other toons almost all the time, and I was frustrated with buffs not getting cast at all sometimes, or just partial buff lists. I started watching her and realized she wasn't using any of her dps routine at all, as in zero of them, even though turned on, and she wasn't using canni or healing right, though if I turned meleeon=1 she would melee. So I started digging through a few scenarios, and finally wiped her ini and added a few things in, it worked ok, so I copy/pasta'd sections and poof, no workie again. So I backed up and hand typed the spells into each section until I found the one that would cause it to stop working. Then I determined I'd added a spell to her cure section that she didn't actually posses yet. Once I removed that, problem solved, and it worked fine, albeit, as BigDaddy says, cures are problematic. If you don't have them memmed they won't cast at all, but aa's and clicky items still work, as they're always available to be checked. The oddity for me was that I could have Counteract Disease listed in the cure section but not have it memmed in my spell list and it causes no issues, but Remove Curse added in the same way, but not existing in my spellbook caused it to bork.
Cure.jpg
 
Last edited:
@toadwart This sounds like some glitch in MQ2. The macro is checking if you have the spell or not when it starts, just to let the user know there is a bad entry. Your screen dump shows you HAVE the Remove Curse Spell in your book or Combat ability, or Alt ability or Item, or Skill. See code below.


Rich (BB code): 
                    /if (!${Me.Book[${str_iniKey}]} && !${Me.CombatAbility[${str_iniKey}]} && !${Me.AltAbility[${str_iniKey}]} && !${FindItem[=${str_iniKey}].ID} && ${str_iniKey.NotEqual[banestrike]} && !${Me.Skill[${str_iniKey}]}) {
                        /echo ...ERROR: ${str_Section}${int_i}=${str_iniKey} unable to find as a AA, Combat Ability, Item, Skill, or Spell
                        /varcalc int_CountErrors ${int_CountErrors}+1
                    }

The code in the CastWhat routine will fail depending on what MQ2 is returning as the spells source(Book, AA, CA, Item, Skill). MQ2 is telling the macro you have the spell, even though you don't.

Can I get you to try one more thing for me. Try adding the debugall arg to your command for starting KA on your shamy. Be ready to end the macro because the spam will go be fast. PM me the log file if you will.
 
Not sure if it's a bug or misconfiguration.
On my Rogue if he hold the role: PullerTank he will "Hide" after a kill and he will not continue to pull before I remove the "Hide"
I'm fully aware of AutoHide=1 :)

Minor bug:
My Necro some times cast the AA: origin but it Interrupts ever time.

I even provide the fixed code if needed but not sure on how the process for KissAssist mac is :)

Beside that I love this Macro! Really nice work!
 
Last edited:
1625881125347.png

If I have 2 groups camping in the same area and 2 pullers chain pulling.....Can I turn this PCNear setting off?

I have turned off afktools, and posse. cant seem to find where its coming from.
 
I'm having an odd issue with Kissassist. I'm playing on an emulated server using the RoF2 client.

For some reason, my party will only assist me when I toggle Main Assist on the tank to Off. If I start KissAssisst on my tank, I have to make sure to turn off the Main Assist role or my party members will not assist me. They'll heal and buff, just not DPS or Melee.

The other issue I'm experiencing is with the PullerTank mode. Again, with the Main Assist role turned off, my tank will pull a mob, return to camp, then go back to pull another mob. The continue to pull mobs typically around 3 or 4 then might attack one before going to grab another. I was under the impression that PullerTank should only pull one mob. I did validate ChainPull is disabled. If I clear a whole camp prior to starting KissAssist, things work somewhat normally until a mob aggros another party member before it's pulled. When that happens, the puller won't attack or pull the mob even though it's within the default melee range. It behaves as if the mob doesn't exist.

Is there a specific KissAssist to use with RoF? I'm using the Emu build of VeryVanilla.

Thanks for your help!

EDIT: Also if I set another character as a Puller, the Tank will just sit there and not attack mobs, even when they're within the red radius.
 
Last edited:
I am not sure about the RoF2 Emulator, but you should only have one character assigned as Main Assist. Normally that would be your Tank/PullerTank. When Kiss starts up you should see a message from each character declaring their role and who they are assisting.
 
I haven't modified any of the files provided. To try and ensure I didn't change something, I used a new copy of ROF2 and a new copy of VeryVanilla EMU (4/28 version). I manually launched MQ2 then eqbcs2.exe.

I launched two EQ clients and logged in manually (WAR and ROG) after validation the MQ2 window appeared. I connected both clients to EQBC. I ran /mac kissassist with no target initially to generate the ini file. I made no changes to the ini files. I launched KissAssist with the following commands in this order:

Rogue - /mac kissassist assist TankName 98
Warrior - /mac kissassist PullerTank

The same behavior occurs where the Rogue won't assist the Warrior. When I disable the Main Assist role for the Warrior, the Rogue begins helping. With Main Assist off, the Warrior repeatedly pulls mobs and drags them around the map.

I also tried on a different computer and the same behavior.

Am I missing something in my setup?

EDIT: Is there a version of VV and KissAssist known to work with ROF2?
 
If the server I'm playing on doesn't have the extended target window enabled, would that cause an issue?

I keep seeing a message that a feature is not available to me and requires Underfoot. The emu server I'm on is in classic.
 
Last edited:
Kiss uses the xtarget auto hater entries to know when you have aggro from a mob. Without the Xtarget window open I don't think kiss will work.
 
@B_I_G__D_A_D_D_Y I still need to push the last version I had you helping me test. What has been holding me back from pushing the newest version to production is I wanted to get more users to test it first, but testers are hard to come by these days. Other than myself, you and deathlock were the only users I had testing. I might just push what I have to production and let the cards fall where they may.
 
ctaylor22 said:
@B_I_G__D_A_D_D_Y I still need to push the last version I had you helping me test. What has been holding me back from pushing the newest version to production is I wanted to get more users to test it first, but testers are hard to come by these days. Other than myself, you and deathlock were the only users I had testing. I might just push what I have to production and let the cards fall where they may.
Click to expand...

Oh Sorry for lack of feedback but the .010 version has been working really well for me. I have done a few tweaks like @Ladon's pet code but nothing that hasn't been discussed previously on the thread. And thus far I haven't switched to the new version of VV MQ2 so this is all on the legacy version. I should note that I mostly work in PullerTank or Hunter mode with a 6-man team. And I rarely run the macro for longer than 2 or 3 hours. So I wouldn't know if there are any long-term issues since I don't play AFK.

I'm happy with the way the macro is working. My biggest goof up is starting the macro and not paying attention that all my characters are INVIS and I'll be reading the forums on my 2nd monitor and 10 minutes later I realize that none of the team have even begun to buff or anything. I mean I'm glad the macro doesn't override INVIS, but sometimes I'm an idiot! :)
 
That is good to hear, I merged in @Ladon 's giving pet items to your pet functionality, to the latest test version, did you not get that version? Look at us @B_I_G__D_A_D_D_Y we have gone and hijacked this thread.
 
My toon is continuously trying to lay down a campfire in a new zone without destroying the old campfire. Using MQNext and KissAssist 12 (the latest download).
 
@cannonballdex Try echoing this information:
/echo ${Me.Fellowship.CampfireZone.ID} ${Zone.ID}

and see what is being returned while you have a campfire up in zone.
 
You must log in or register to reply here.
KissAssist Release KissAssist
Next unread thread 🦁

Users who are viewing this thread

Total: 2 (members: 0, guests: 2)
Back
Top
Cart

Cart

Total -