• 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

Question - condition syntax vs. what/how KA checks

timmy

Well-known member
Joined
Apr 1, 2014
RedCents
1,443¢
Version of KissAssist.mac?
11.001
When did your problem start?
when i attempted to add a condition to a group clickie buff
Character Role?
  1. Assist
What class is having this issue?
  1. Bard
How often does this issue occur?
Always
Can you reproduce the issue?
just find me a place to die and we can watch the clickie buff bounce together.
i have a clickie buff (nature's melody) that won't stick if the character has res sickness.

but this condition took care of it.

Code:
Cond1=!${Me.Buff[Resurrection Sickness].ID}

but then i ran into the problem where the clickie buff is a group buff and if someone other than clicker has res sickness, the buff will bounce, so i tried:

Code:
Cond1=!${Target.Buff[Resurrection Sickness].ID} || !${Me.Buff[Resurrection Sickness].ID}

i thought i was being slick there since i knew the second half worked, and the first half looked reasonable enough.

it does not work. trying to puzzle it out, i thought, actually, just the first part should be all that's required because isn't target.buff and me.buff the same thing when the clicker is checking a target? it's not, i don't think, but this pondering got me wondering why.

so i'd really like some help with getting a condition that works for both the clicker and the entire group, but i'd also like to know why the first code block works but not the second. if someone is so inclined to explain it to me, that would be great. i'm a bit daft, so small words would help. i know i could use a |me tag and make it work, but it would be nice to have the bard check the entire group and nicer still to know what part of that second condition i failed at. thanks!
 
The first one works because you have rez sickness and it evaluates that and realizes that it shouldn't cast.

The second one says "Cast this if my target doesn't have rez sickness OR Cast this if I don't have rez sickness." I think probably what you want is actually "Cast this if no one in my group including myself has rez sickness" but in the case you wrote the condition for you probably actually just want to change || to && (Cast this if my target doesn't have rez sickness AND I don't have rez sickness).

That said, I don't know if KISS targets a group member for a group buff or not, so even changing the condition to && may not fix what you're trying to do since what you really want to know is the rez sickness status of everyone in your group. Someone more well versed than me will have to answer that question for you.
 
You need something like MQ2Netbots to really do want you want:
Code:
cond#=!${Netbots[char1name].Buff[Resurrection Sickness].ID} && !${Netbots[char2name].Buff[Resurrection Sickness].ID} && !${Netbots[char3name].Buff[Resurrection Sickness].ID} && !${Netbots[char4name].Buff[Resurrection Sickness].ID} && !${Netbots[char5name].Buff[Resurrection Sickness].ID} && !${Me.Buff[Resurrection Sickness].ID}
 
That said, I don't know if KISS targets a group member for a group buff or not, so even changing the condition to && may not fix what you're trying to do since what you really want to know is the rez sickness status of everyone in your group. Someone more well versed than me will have to answer that question for you.

Yes and No. When checking buffs in the normal check buffs routine, group buffs target the caster. When reading the KissAssist_buffs.ini file to check for buffs, the individual that needs the buff is targeted.
 
Kiss conditions does not check anyone other that the target of the spell/aa/etc. It is not capable of checking multiple toons just one.
 
Kiss conditions does not check anyone other that the target of the spell/aa/etc. It is not capable of checking multiple toons just one.

Presumably you could also use mq2netbots, mq2dannet or similar though, if you have those plugins loaded and correctly configured, of course?
 
If you use
Code:
${Target.Spell[spellname].StacksTarget}
will check if the spell will stacks on the target, not at home but I believe that is the right one
 
${Target.Buff[Buff Name].WillStack[Spell Name]}

I don't think you need Target.Spell for the .StacksTarget member. ${Spell[Spell Name].StacksTarget} uses your current target and returns true or false.
 
Last edited:
Question - condition syntax vs. what/how KA checks

Users who are viewing this thread

Back
Top
Cart