• 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 - Boastful Conclusion

Goober24

Member
Joined
Feb 27, 2024
RedCents
50¢
Version of KissAssist.mac?
12.002
When did your problem start?
2/28/24
Character Role?
  1. Assist
What class is having this issue?
  1. Bard
How often does this issue occur?
Always
Bard's get the Boastful Bellow line that does initial damage and then when it falls off it does damage. Kissassist will fire this off in the dps section no problem, however it will come off cooldown before the debuff wears off, so KA will fire it off before you get the conclusion damage.

I thought maybe I would try to use the interval for this, however if you look at the KA docs, it says "interval" is only for cast time abilities, so when I played around with specifying different lengths it didnt do anything.

My question is, is there a way you can set a time interval on this skill in the DPS section to stop it from cutting it short?
 
Bard's get the Boastful Bellow line that does initial damage and then when it falls off it does damage. Kissassist will fire this off in the dps section no problem, however it will come off cooldown before the debuff wears off, so KA will fire it off before you get the conclusion damage.

I thought maybe I would try to use the interval for this, however if you look at the KA docs, it says "interval" is only for cast time abilities, so when I played around with specifying different lengths it didnt do anything.

My question is, is there a way you can set a time interval on this skill in the DPS section to stop it from cutting it short?
You can try this

DPSX=Boastful Bellow|99|CondX

CondX=!${Target.MyBuff[Boastful Bellow].ID}
 
You can try this

DPSX=Boastful Bellow|99|CondX

CondX=!${Target.MyBuff[Boastful Bellow].ID}
I've tried to do this as well, and I think I tried the following condition:

Cond2=${Target.BuffsPopulated} && !${Target.Buff[Boastful Bellow].Caster.Equal[${Me.Name}]}

But when I actually tried it on mobs, it seemed to me I still wasn't getting the conclusion to happen. It's like the code was seeing that the buff was gone but there was still some delay for the damage to happen and my kissassist section was then still getting the bellow buff back on it too fast, so I was losing the conclusion damage. I didn't do a very big sample in my testing and I may have been incorrect...I feel like I was manually looking for the damage in my log file rather then looking at my parse (which was silly). So I should give this another try and see if Psy's suggestion works, or if my condition actually worked, and I only thought it wasn't.
 
unfortunately, eq appears to have a bug where even if the debuff is gone, you still need a couple of seconds for it to consistently fulminate. it is really annoying
 
Only way I've gotten Bellow to work consistently is by making a LEM that watches for the conclusion to do damage, then recast bellow.
I basically had been using a GINA trigger start a timer on bellow cast and then ends the timer when it sees the damage from conclusion. Then on my driver manually doing a /dex <bardname> /alt activate <bellow id>
 
Only way I've gotten Bellow to work consistently is by making a LEM that watches for the conclusion to do damage, then recast bellow.
If you have a sec could you share more on this setup? I thought about using a pixel checker alongside Gina and then autohotkey or something to retrigger it, but it seems clunky so I was trying to find a solution in KA if there is one.

edit* In my head, I imagine it being a condition that just says (check for debuff, If the debuff is gone, wait 5 seconds, and do this ability) but I'm not great with programming, and I'm not sure that's within the realm of doable.
 
Question - Boastful Conclusion

Users who are viewing this thread

Back
Top
Cart