• 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
Join us with Level 2 access RedCents
Overview Commands Instructions Updates (69) Reviews (5) History Discussion
Knightly said:
I believe you would do:

INI: 
DPS#=Dissident Fang|98|Cond20
Cond15=${Me.PctHPs} < 45
Cond19=!${Me.XTarget} > 2
Cond20=${Cond15} && ${Cond19}

But it might be ${Cond[15]}. Whatever way you reference conditions.
Click to expand...

I went through this a few months ago and was instructed that Conditions are saved in an array so we need to use an Array Identifier to reference them in another condition using [ ] (brackets)... so it should look like this instead!

INI: 
DPS#=Dissident Fang|98|Cond20
Cond15=${Me.PctHPs} < 45
Cond19=!${Me.XTarget} > 2
Cond20=${Cond[15]} && ${Cond[19]}
 
B_I_G__D_A_D_D_Y said:
I went through this a few months ago and was instructed that Conditions are saved in an array so we need to use an Array Identifier to reference them in another condition using [ ] (brackets)... so it should look like this instead!

INI: 
DPS#=Dissident Fang|98|Cond20
Cond15=${Me.PctHPs} < 45
Cond19=!${Me.XTarget} > 2
Cond20=${Cond[15]} && ${Cond[19]}
Click to expand...

I just went with specific conditions as to not confuse myself.
 
Well do you have GroupWatchOn? if you have groupwatchon the puller will pause if someone in the group needs to med, so we have the puller med now while waiting on your team member.
 
I am having a problem since moving to this from KA11 - my puller doesnt stop when group is low on mana.

I have GroupWatchOn=1 and GroupWatchCheck=False (this is just an additional/optional condition check right?)

I have changed MedStop to 90 to see if that make a difference. Was using just EQBC, loaded DanNet and set DanNetOn=1 to see if that helped. Turned EQBC to off so it was just DanNet. Nothing seems to be changing.

Puller will detect that they have to stop and I get the message 'Waiting for >> X << to med up to Y mana'
but then straight away it wil say 'X is above Y mana resuming activity'
and then go and pull giving the 'Pulling X at whatever feet'

The character needing to med will still be at 5% or 10% mana so it shouldnt be pulling.

Any ideas?

Edit: After reading of deathlock's problem above, he was basically having the opposite problem to me. I set MedOn=1 on my bard who is pulling and he is now waiting for characters to med properly again with GroupWatchOn=1 - that's fine just not how KA11 used to perform. All solved, set MedStart=1 on my Bard so he shouldnt ever stop to med as should be the case. I like the addition of MedStop aswell that's great!
 
Last edited:
@methodx great catch. That is one of those things that was overlooked. I added code to switch on and off MedOn when the GroupWatch routine calls the Med routine. So you can now have MedOn=0 and GroupWatchOn=1 and it should work. We added to use the Med routine when waiting on a group member to med up, but I totally overlooked that the MedOn flag has to be turned on for it to work.

Just watch for an update later today.
 
Occasionaly I have found Kiss gets stuck on group pets trying to kill them. Has happened on cleric hammers , enchanter pets and BL pets. The only thing I have found to stop the MA from attacking is restarting the macro. Anyone have any other suggestions have been running in hunter mode recently and it's a pain to need to go back to your starting point to restart the macro. Has doen the on SK and War

1592242244144.png
 
Well it only matters on the MA, the macro sets TargetSwitchingOn=0 for all non MA characters. If you have TargetSwitchingOn turned on then it will let you do just that. Whatever you target with your MA will be targeted by your supporting characters. Just change targets on your MA, to a valid target and everyone should switch targets.

I think I might see where you could target a PC's pet from the MA. I know I check to NOT let you do that, but I think I got the logic a little whacked.
 
Hello all, im trying to make my ranger heal only out of combat because he is the tank (i know, been playing in Rizlona)

so i put some conditions for him:

HealsOn=1
HealsSize=5
Heals1=Healing|80|Cond2

ConOn=1
CondSize=5
Cond1=${Target.PctHPs} >90 && ${Me.PctMana} > 80
Cond2=!${Me.CombatState.Equal[COMBAT]} && ${Me.PctMana} > 70

i dont know whats wrong, sometimes he just stays there looking at the wall and i have to make him attack a mob or something, this is specific when there are more than 1 mob on xtarget

can n1 point me where its wrong pls??

thx in advanced
 
ctaylor22 said:
Well it only matters on the MA, the macro sets TargetSwitchingOn=0 for all non MA characters. If you have TargetSwitchingOn turned on then it will let you do just that. Whatever you target with your MA will be targeted by your supporting characters. Just change targets on your MA, to a valid target and everyone should switch targets.

I think I might see where you could target a PC's pet from the MA. I know I check to NOT let you do that, but I think I got the logic a little whacked.
Click to expand...
When it happens I cannot change targets at all. I do the Restless Assult mission daily and have no problems changing targets on the last name, but when I locks onto a pet restarting the macro is the only way I have found to stop it.
 
Zeeeeeee said:
Hello all, im trying to make my ranger heal only out of combat because he is the tank (i know, been playing in Rizlona)

so i put some conditions for him:

HealsOn=1
HealsSize=5
Heals1=Healing|80|Cond2

ConOn=1
CondSize=5
Cond1=${Target.PctHPs} >90 && ${Me.PctMana} > 80
Cond2=!${Me.CombatState.Equal[COMBAT]} && ${Me.PctMana} > 70

i dont know whats wrong, sometimes he just stays there looking at the wall and i have to make him attack a mob or something, this is specific when there are more than 1 mob on xtarget

can n1 point me where its wrong pls??

thx in advanced
Click to expand...
I seem to remember having a similar problem with one of my configs in Kiss12. I think by preventing him from casting the heal when in combat you are kinda locking the macro up. I think you will need to allow him to heal in and out of combat. I know there were some update in Kiss12 to prevent lockups when using conditions in heals. You may want to upgrade.

This was in the Kiss12 notes

27. Added logic to the single heal routine to help keep from getting locked in the heal loop when using Conditions.
This issue would keep healers from rezzing.
 
drawthow said:
I seem to remember having a similar problem with one of my configs in Kiss12. I think by preventing him from casting the heal when in combat you are kinda locking the macro up. I think you will need to allow him to heal in and out of combat. I know there were some update in Kiss12 to prevent lockups when using conditions in heals. You may want to upgrade.

This was in the Kiss12 notes

27. Added logic to the single heal routine to help keep from getting locked in the heal loop when using Conditions.
This issue would keep healers from rezzing.
Click to expand...
Tyvm man...tried kiss12 and its working flawless until now

guess im gonna upgrade all my toon to KA12 already
 
I have ranger pulling and set to use bow rather than melee. How do I set the distance? Message he is too close keeps popping up. Below is the section of INI I thought controlled it.

[Melee]
AssistAt=100
MeleeOn=1
FaceMobOn=1
MeleeDistance=150
StickHow=snaproll
AutoFireOn=1
UseMQ2Melee=0
TargetSwitchingOn=1
 
Damn, I am about ready to pull my hair out. I can not get the new begfor buff system to save my life. I've tried every way possible to get shm frenzied growth, shm ennui, and clr shining aegis/shining defense to work to no avail.

Normally, this would be fine and I'd just use the normal buff method, but it seems the new KA has messed up my cleric's ability to buff shining. I've tried every iteration:

Shining Aegis|MA (this used to work)
Shining Aegis|dual|Shining Defense|MA
Shining Aegis|dual|Shining Defense|class|war
Shining Aegis|alias|Symbol
Shining Aegis|dual|Shining Defense|alias|Symbol
Shining Aegis|class|war

Every time, the cleric will buff everyone else in the group and often buff herself multiple times. Even when I go back to KA11, it's still broken! And, I swear it was working before
 
Having problems with enchanter mez invis checks with 12.001. He will sit and spam MEZZING <target> messages, but never breaks invis to cast. This happens a lot when moving camps in a dungeon and catching see invis mobs along the way.
 
@nerp Yea, should I fix the spam and keep the mezzer invised, or should I change the logic to break invis and continue mezzing?
 
ctaylor22 said:
@nerp Yea, should I fix the spam and keep the mezzer invised, or should I change the logic to break invis and continue mezzing?
Click to expand...

My opinion is to just fix the spam for now. Otherwise, a better solution is to implement an option or setting in KA ini files to allow the player to choose to break invis to mez with something like that ie: =0 vs =1. I feel it can cause a yucky situation in some scenarios otherwise.
 
Last edited:
Break invis. If you're running around invis with pause off, its' because you don't want to wipe when spotted.

Edit: This was also the behavior in previous versions, not sure what changed.
 
Last edited:
Look in you kissassist_CharacterName.ini file for the section

[Pull]
PullWith=Melee
PullMeleeStick=0
MaxRadius=350

That is the section to look at and copy and post.
 
Running a group I haven't played much lately. Using a druid to pull and a mage pet tank.

Periodically I'll find my puller dead. I finally caught it happening once. The mage set to MA had his pet targeted and nothing was happening. He was very close to OOM so I'm guessing he didn't have enough mana for the spell but then he wouldn't drop out of the buff mode to engage the mobs on Xtarget! Even the druid wouldn't heal himself because the MA's target was his pet and combat assist hadn't been called. So the druid was just standing there getting beat on.

I found an older thread https://www.redguides.com/community...d-a-cond-to-any-kind-of-buff-construct.70446/ where somebody else had this happen.

I suspect that poster is correct, the MA is attempting to buff his pet but he's OOM so the macro just seems to spin in that mode. Like that other poster said, it doesn't happen very often.
 
When I want to cast bard invis I do this command

/noparse /bcg //if (${Me.Class.ShortName.Find[BRD]}) /multiline ; /mqp on ; /twist off ; /alt activate 3704 ; /alt activate 231

About 50% of the time if I unpause the Bard before I get to where I'm going the bard will start twisting again and break invis. Any thoughts on why this is happening?
 
@drawthow any plugin can override the macro. So I would assume something like /twist is breaking invis. We are checking all through the macro to stop casting or don't cast/twist if your invised. If you could ever reproduce the issue and get a debug log of this happening it would help in tracking down the issue.
 
Zebadiah said:
Look in you kissassist_CharacterName.ini file for the section

[Pull]
PullWith=Melee
PullMeleeStick=0
MaxRadius=350

That is the section to look at and copy and post.
Click to expand...
Sorry late with the reply Zebadiah. Started using ranger to pull manually and the grp worked so good I was doing ToV quest! All leveling up nicely. Pulling in some zones is fine others not so good. I believe the issue is when you are in a tunnel like Howling Stones the "closest actual" mob is targeted instead of the "closest accessible" mob. So auto puller goes to the closest actual mob which requires he run past 6 other mobs to get there. Instant train.

Here is the section you requested. Any help is greatly appreciated.

[Pull]
PullWith=Ice Burrower Swarm Rnk.II
PullMeleeStick=0
MaxRadius=350
MaxZRange=50
UseWayPointZ=0
PullWait=5
PullRadiusToUse=90
PullRoleToggle=0
ChainPull=1
ChainPullHP=90
ChainPullPause=30|2
PullPause=30|2
PullLevel=0|0
PullArcWidth=0
 
Well all I can see is in the line PullWith=Ice Burrower Swarm Rnk.II <-------You need to put a space after the period. How does it work with using a spell instead of a bow and arrow?
 
Ice Burrower Swarm Rk. II

Note the lack of "n" in Rk, and the space after the period. Not sure if there are other issues, but that stood out.
 
drawthow said:
/noparse /bcg //if (${Me.Class.ShortName.Find[BRD]}) /multiline ; /mqp on ; /twist off ; /alt activate 3704 ; /alt activate 231
Click to expand...
off topic, but why the convoluted noparse ifstatement command when you could just /bct BardName instead? Are we just trying to show off how fancy our command structure is?
 
Many_Whelps said:
off topic, but why the convoluted noparse ifstatement command when you could just /bct BardName instead? Are we just trying to show off how fancy our command structure is?
Click to expand...
that looks like from my hotkeys.

I have it that way because i run multiple different groups, and test all sorts of setups and configurations, and i can keep my hotkeys the same without having to swap around which toon i'm msging to
 
Sic said:
that looks like from my hotkeys.

I have it that way because i run multiple different groups, and test all sorts of setups and configurations, and i can keep my hotkeys the same without having to swap around which toon i'm msging to
Click to expand...
Yeah, I get why you do it. The average user doesn't need all that, though.
 
Many_Whelps said:
off topic, but why the convoluted noparse ifstatement command when you could just /bct BardName instead? Are we just trying to show off how fancy our command structure is?
Click to expand...
I did copy Sic and use it for the same reason. I have two different 115 groups with a total of about 30 toons that I'm always switching out to try out different combinations.
 
I keep getting an issue -

I do /macro kissassist - It spits back

failed to parse /if conditionm (1 && 0) non numaric encountered
Kissassist.mac@362: /if ($(EQBCCon) &&& (Danneton)

How do i fix this?
 
You must log in or register to reply here.
KissAssist Release KissAssist
Next unread thread 🦁

Users who are viewing this thread

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

Cart

Total -