• 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 12.002.039

No permission to download
@deathlock If I remember correctly you were the one who brought up the whole needing everyone to switch targets with the MA. That is where the whole TargetSwitchingOn was born.
 
@deathlock If I remember correctly you were the one who brought up the whole needing everyone to switch targets with the MA. That is where the whole TargetSwitchingOn was born.

@ctaylor22
I wanted the tank to be able to switch targets when there was more then one on extended target (Kiss always picked the target and you could not change it). The bots always switch to what the tank was tanking. I did ask for the pets to swap, because they always stayed on the initial mob Kiss picked for the tank, which was bad for certain balancing situation or Kael type events. Out of combat, I wouldn't think the bots would not do any kind of targeting, unless of course the mimic me button was being used. Out of combat is when you are typically doing trades, quest hailing, /inspecting stuff for quests etc... So why would you want your bot to be freaking out during this time trying to target something. All you do is fight it and have to use mqp to make it stop, until your done doing your business, then remember to turn it back on.
 

TargetSwitchingOn should allow your tank to swap targets without reverting back to your original target - helpful for changing mobs during combat for burning an add, or swapping to another named --- like in FF for example.

TargetSwitchingOn, however, seems to have several issues atm targetting group members and doing other odd stuff - I think its a work in progress

I found this post, it was a question about TargetSwitchingOn.

In my Opinion and yours may vary:

TargetSwitchingOn should only be used by the mainassist, so he can switch target if there are multiple's on extended target. Other toons should ignore TargetSwitchingOn as it was designed for the MA only and just follow the MA and make their pets follow the MA too . I believe this is the way it worked before, minus the pets not switching.. When out of Combat or there is nothing on Extended target window other toons should just not target anything or stay on the last thing that was targeted. I guess if they have to target group members to look at buffs, that too.
 
In my Opinion and yours may vary:

TargetSwitchingOn should only be used by the mainassist,...

Several current events require targeting different mobs among a selection on the Xtarget Window. Restless Assault, Avatar of War, and Griklor all come to mind. I think the current evolution in KA Beta 12.001 is working well at that. I have every character INI set to TargetSwitchingOn=1. I also use a "switchnow" [ /bcg //switchnow ] hotbutton on my MT to force the switch.

Now it can be a bit of a nuisance when you're in POK and all your chars keep following the MA's target, but that can also work in your favor for those times you have to target a quest giver and say Ready to zone in.

By hitting the ESC button on the MA before trying to do vendor or character trade stuff it pretty much solves the problem.

Now maybe I'm overlooking something. In what combat situations would you want the group DPS not to follow the MA's lead?
 
Several current events require targeting different mobs among a selection on the Xtarget Window. Restless Assault, Avatar of War, and Griklor all come to mind. I think the current evolution in KA Beta 12.001 is working well at that. I have every character INI set to TargetSwitchingOn=1. I also use a "switchnow" [ /bcg //switchnow ] hotbutton on my MT to force the switch.

Now it can be a bit of a nuisance when you're in POK and all your chars keep following the MA's target, but that can also work in your favor for those times you have to target a quest giver and say Ready to zone in.

By hitting the ESC button on the MA before trying to do vendor or character trade stuff it pretty much solves the problem.

Now maybe I'm overlooking something. In what combat situations would you want the group DPS not to follow the MA's lead?

If the MA doesn't have a target and the the bots do no targeting of their own at that point then would work great too. I guess the fact that the targeting is just freaking out atm is what drove these last couple posts. Typically I use the Mimic me button when I want the toons to assist me when out of combat and to say things to enter tasks "Ready".

The //switchnow works, but Kiss has been switching the bots every time them MA changes targets anyway, just not the pets (Which I think has been changed so they change targets too).

As far as the group dpsing something the "Main Tank" is not, you have to think of the "MT' and the "MA" being different group members. The set up is you would need to assign the MA to someone else in your group, not the tank. The tank would tank whatever, while the MA would direct the rest of your group to attack what you wanted to if the MT wasn't hitting it.? This is very specific, but works. We did this for the Cactikki event in ROS. Seem to work well there, when trying to get the achievements. But you then need to run/focus on 2 toons instead of one.
 
Last edited:
Figured out target spamming on the Shaman.

My shaman target spam is coming from the fact that group members are not at 100%, when out of combat. She will lock targets with my zerker whom is always at 88% health roughly. IF another group member goes below 100% she will spam between them. I do not have any heals set up to heal until group members reach 85% or less. Mainly cause you can't heal a bezerker past a certain % due to self inflicted damage they do to themselves to keep them below 90%.

Once everyone is at 100% she goes back to normal.

Spam targeting from no target to target self also happens on bots when MA targets them. Apparently they hate to target themsleves.

INI:
[Heals]
Help=Format Spell|% to heal at i.e. Devout Light Rk. II|50
HealsOn=1
HealsSize=17


// MA
Heals1=Reckless Renewal|79|MA
Heals2=Reckless Rejuvenation|78|MA
Heals3=Reckless Regeneration|77|MA

// Single
Heals4=Reckless Renewal|65
Heals5=Reckless Rejuvenation|68
Heals6=Reckless Regeneration|68
Heals7=Primordial Intervention|40

// Group
Heals8=Zrelik's Recourse|80|Cond11
Heals9=Spectre of Renewal|70|Cond10
Heals10=${InvSlot[Chest].Item.Name}|60|Cond13
Heals11=Staff of Forbidden Rites|0|rezcombat
Heals12=Dissident Roar|99|Cond18

XTarHeal=0
XTarHealList=Xtar slots here Example: 5|6|7
HealGroupPetsOn=1
AutoRezOn=1


Heals13=Soothsayer's Intervention|99|MA|Cond15
Heals14=Spirit Guardian|99|MA|Cond16
Heals15=Rabid Bear|30|Me
Heals16=Ancestral Guard|60|Me
Heals17=Union of Spirits|99|Cond17

[KConditions]
ConOn=1
CondSize=20
Cond1=${Me.CurrentHPs} > 160000 && ${Math.Calc[${Me.MaxMana}-${Me.CurrentMana}].Int} > 65000
Cond2=${Me.CombatState.Equal[COMBAT]} && ${Me.XTarget} > 0
Cond3=${Group.Injured[80]} < 1 && ${Target.Named} || ${Group.Injured[80]} < 1 && ${Me.XTarget} < 3
Cond4=!${Target.Buff[Turgur's Insects].ID} && ${Target.Named} || !${Target.Buff[Turgur's Insects].ID} && ${Me.XTarget} < 3
Cond5=${Me.XTarget} > 0 && ${Group.Injured[80]} < 1
Cond6=${Me.XTarget} < 3 && ${Group.Injured[80]} < 1 && ${Me.PctMana} > 70 && ${Target.PctHPs} > 60
Cond7=${SpawnCount[${Me.Name}]} > 1
Cond8=${Me.XTarget} > 0 && ${Group.Injured[80]} < 1 && ${Me.Song[Healing Twincast].ID}
Cond9=${Me.XTarget} > 2 && ${Group.Injured[80]} < 3
Cond10=${Me.XTarget} > 2 || ${Target.Named}
Cond11=${Group.Injured[80]} > 2
Cond12=${Group.Injured[70]} > 2
Cond13=${Group.Injured[30]} > 1
Cond14=${Me.XTarget} > 3 && ${Select[${Target.ConColor},BLUE,YELLOW,RED]} || ${Target.Named} && ${Select[${Target.ConColor},YELLOW,RED]}
Cond15=!${Group.MainAssist.OtherZone} && ${Group.MainAssist.PctHPs} < 35
Cond16=${Target.Distance3D} < 150 && ${Group.MainAssist.PctHPs} < 35
Cond17=${Group.MainAssist.PctHPs} < 35 && ${Target.Distance3D} < 150 || ${Me.PctHPs} < 40
Cond18=${Me.XTarget} > 0
Cond19=TRUE
Cond20=TRUE
 
Last edited:
Rogue Issue:

Buffs4=Conditioned Reflexes|Dual|Conditioned Reflexes Effect II

Conditioned Reflexes is a combat disc.. Kiss will spam "Casting Conditioned Reflexes Rk.II on me." But never does. I have to manually click the disc.
 
Rogue Issue:

Buffs4=Conditioned Reflexes|Dual|Conditioned Reflexes Effect II

Conditioned Reflexes is a combat disc.. Kiss will spam "Casting Conditioned Reflexes Rk.II on me." But never does. I have to manually click the disc.
I'd make sure you have the name of the disc and the buff correct.

1588258987383.png
 
I have my shaman healing and buffing out of group. Everything works fine except he won't buff Champion to the group. It's Group v1 but can be cast on other groups. Is there a way to get this working?
 
with the latest version of kiss12.. the /setdps spell 1 returns "SETDPS You need to mem a spell"
when rolled back to previous version it works again.
I can't find anything different from 11.5 and 12.1 when it comes to the /setdps alias and the /IniWrite bind routine. With that said, I did find an issue, but both versions of kiss had the same issue.
 
Spell TargetType of type Group V1 use to be for characters Group only and Group V2 was for any group. If we remove that check then you will have the caster trying to buff a group over and over again. Will have to see if there is another check beyond the Group V1 Targettype.
 
@Tiger and anyone else interested. We have 2 options to fix this Group V1 TargetType issue.

Option 1 would be to remove the Group V1 check. Now this will create the issue of casters trying to cast buffs, on characters that are out of group, over and over again. So with this option you would have to create a Condition, to check if the character is in group, and use that condition on all spells that would fail casting on other groups.

Option 2 would be to use a list of spell ID's for the Group V1 exceptions, and just treat the exceptions the same as Group V2 spells.

This is a shout out to everyone, I need a list of all the Group spells that kiss will NOT cast on other groups, when it should.

Somewhere along the line EQ made a change so that SOME spells, with a TargetType of Group V1, will cast on other groups. Group V2 will cast on other groups, but Group V1 would not. So I need a list of Spell ID's to use.

To get the spell ID you can use this command:

/echo ${Spell[SpellName].ID}

For Champion if would be /echo ${Spell[Champion].ID}

Ok will do some testing. Is it not all Group V1 can be cast on others now? The Ranger and Enchanter ones I just tested all worked.
 
Actually it looks like all Group V1 buffs work on others but not heals or cures.
 
@Tiger Are you sure? All Group V1 and Group V2 will now allow you to cast the spell on other groups? For all Classes?

No I'm not sure yet, I read it here: http://www.zlizeq.com/Game_Mechanics-Buffs_and_Debuffs

"Group v1 - Used to affect only your own group, and still holds true for non-buffs (such as heals and cures for example), but today, they too can be cast on other groups (example: Pack Shrew)"

I'll do some testing later with the toons I have available but the statement above seems to hold true from a few tests I just did on my ranger and chanter, the buffs hold on other groups, the cleric heals do not.
 
@Tiger I think they are correct, I don't know why that didn't hit me, kind of like, I couldn't see the forest because of the trees. I knew there were still Group V1 spells that only worked on Casters group, but for some reason I didn't catch the separation of heals and cures .VS. Buffs.

Starting to make a little more sense. I guess I was just being thick headed.
 
@Tiger I think they are correct, I don't know why that didn't hit me, kind of like, I could see the forest because of the trees. I knew there were still Group V1 spells that only worked on Casters group, but for some reason I didn't catch the separation of heals and cures .VS. Buffs.

Starting to make a little more sense. I guess I was just being thick headed.

No worries. Assuming that is the case and it only affects buffs, do you still require all the ID numbers or can you differentiate between them?
 
ctaylor22 updated KissAssist 12 Beta with a new update entry:

Beta5 Release

05-03-2020
Removed Group V1 TargetType check from the Buff routine. Group V1 is still checked in the Heals and Cure routines.
Fixed an issue in the Bind_IniWrite routine
Added a check for an ";" in the first position of any array in the LoadIni routine. Placing an ";" in the first position will keep the entry from being loaded.

Read the rest of this update entry...
 
Running beta5 with my MA in manual mode, other boxes in Assist. MA has BuffsOn. A few seconds after combat starts, MA targets himself and switches back to himself almost immediately if I try to change it. INI hasn't changed since Beta4, happy to post if it would be helpful.
 
1588578034453.png

same mob set multiple times on xtar, don't think that is intended. newest beta v5.
when i target a NPC to talk to it (requesting mission) it sometimes gets added to xtar, that intended ?

Disregard I had a mysterious keybind in option ... adding to xtar

1588581310122.png
spammed this so much and so quickly that the client locked up
 
Last edited:
View attachment 21297
spammed this so much and so quickly that the client locked up

I saw this a few times too. My bard went crazy with this when we dropped down into the tunnels in Velk's Lab. I figured it had something to due with the weird pathing down there because you can get aggro on those mobs when you're half the zone away sometimes. This flew by so fast it was almost impossible to read but I know it showed something like 70 mobs it was tracking.

Other than this I haven't had any issues with Beta 5!
 
View attachment 21294

same mob set multiple times on xtar, don't think that is intended. newest beta v5.
when i target a NPC to talk to it (requesting mission) it sometimes gets added to xtar, that intended ?
Not sure if this is being done by Kiss anymore. Ran without it and still happening, no clue what is causing it, started after last vv patch, it is not had a keybind /puzzled
 
Last edited:
Hello, new user here :)

I'm learning using KissAssist 11, first started with MQ2Melee and now i like to use both if possible because i love the downshit & holyshit of the latter.

I'm just trying first moloing my SK with with my merc and automating all possible tasks playing this way, latter i will add more accounts, but for now i want it simple.

Now the questions if you dont mind :)

For the merc to follow & heal me i have to remove the Puller role from my SK manually each time i start the game, is there any automated way of assigning roles?

Now, i really dont like the stick & face to mob features, i just want to automate some spells & abilities but i want to move free.

No matter what i have tried, my SK always keep facing the mobs after i turn. Is there any way to remove this feature?

Thanks a lot.
 
That was some debug messages I added to the AECheck routine we I was trying to find an issue in the AE routine. I will be removing those lines.
 
Hi Zangano. Not sure I can help cause I am still learning but when I started I just 2 boxed ... The reason is just running one character you don't see what KA can do for you unless you run with two or more. With that said. Have you tried to just ( /mac KissAssist manual ) with you as the target. Then assign your role as (Tank, Puller, PullerTank ect.) when you right click on your character name. I think the manual will stop or cancels some of the things in KA and returns control over to you and keeps most of KA running.

From what you said I take it that your SK has a healer merc that goes with him. If so then you don't need to assign the role as puller. If your merc is a tank merc and you have assigned the it the role of Tank for your two person group then you should be assisting the tank (where you control the SK and pull what you want and the merc goes to tank it and grap aggro. But here again with the set up you are suggesting you still don't need to be assigned the Puller role.

From Maskoi's Guide--KissAssist Insturctions and Settings
StickHow Tells character how to stick to mob when fighting. !front, behindonce, snaproll rear, front. See mq2moveutils for more valid commands and descriptions. The default is snaproll. You can edit it in your ini file for this character.

I hope this helps a little. Again I am still learning the fine details of KA and what it can do. I think is rates right up there with PBJ. Thanks to Maskoi for what he has done.
 
is there a way to stop nav from moving tank when mob is incoming to camp from a puller?

hehe maybe just me but i kinda liked the adds showing up telling me how many mobs in AE range has helped me figure out a few times hey there is a mob above/bellow or on other side of wall. this has saved me a few times. also knowing what the name are so i can figure out where the mob is (have had one Directly under group) to adjust group is nice, maybe make it a toggle option for those who want?

INI:
[Melee]
AssistAt=95
MeleeOn=1
FaceMobOn=1
MeleeDistance=21
StickHow=Loose
AutoFireOn=0
UseMQ2Melee=0
TargetSwitchingOn=1

tank still moves even with melee turned OFF
 
Last edited:
is there a way to stop nav from moving tank when mob is incoming to camp from a puller?

hehe maybe just me but i kinda liked the adds showing up telling me how many mobs in AE range has helped me figure out a few times hey there is a mob above/bellow or on other side of wall. this has saved me a few times. also knowing what the name are so i can figure out where the mob is (have had one Directly under group) to adjust group is nice, maybe make it a toggle option for those who want?

INI:
[Melee]
AssistAt=95
MeleeOn=1
FaceMobOn=1
MeleeDistance=21
StickHow=Loose
AutoFireOn=0
UseMQ2Melee=0
TargetSwitchingOn=1

tank still moves even with melee turned OFF

Campradius determines the distance your tank moves. He'll react and move towards an incoming mob when it comes in the camp radius under General settings. I usually have mine set to 25-30 with meleedistance at 40-50.
 
putting camp radius that small gets my ranger killed being as my ranger sit around 31 - 50 means i have to set it for at least 55 to have any type of coverage hence the problem because i cant always have my back to a wall.
 
@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.
 
DPSMeter=1 causes a macro pause as it is trying to use mq2dpsadv. Could just give an error message and turn it off if it is not loaded ?

Got me killed a few times as kiss did not require it in the past then I start using kiss12 beta and assume everything is ok, engage mob and nothing happens.
 
@jande The macro loads the plugin if it is not loaded, and you have DPSMeter turned on. Are you unloading the plugin? I will look at adding some additional code, but it will only check when you start the macro.
 
@jande I checked and the macro already has the code to do what you suggested. I am not sure what is causing your setup to fail loading the MQ2DPSAdv plugin.
 
@jande I checked and the macro already has the code to do what you suggested. I am not sure what is causing your setup to fail loading the MQ2DPSAdv plugin.
I do not use mq2dpsadv and have it setup that if I zone it unloads it,
Honestly all these new windows are proving more of an distraction than anything else and the autoloading of it is driving me nuts.

a dps meter has no place in a assist macro.

ps once I see its on I turn it off.
 
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.
 
KissAssist Release KissAssist

Users who are viewing this thread

Back
Top
Cart