Question - bard boastful bellow question

[Bolbod]

So, as most bards know (or should know), boastful bellow gives a wicked exit proc when it wears off. I would love to capitalize on this, but I have no idea how to configure my .ini to allow the skill to only reapply after a second or two after the skill wears off the target. Does anyone have a pointer for that?

 

[Myysterio]

use this condition on your boastful bellow. can use the AE one (stacks with the single target one) or not, or just mash it. Long as you got the endurance.

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

 

[Bolbod]

I'll give it a shot, thank you so much!

 

[Hanlons Razor]

I never could get anything using Target.Buff to work reliably with Bellow. It would often recast it too early even though the recourse had not hit yet.

Ended up making a simple LEM that watches for the recourse to hit and recasts bellow. Then I have KA just firing bellow with a |Once tag to get the first one out.

 

[ChatWithThisName]

I never could get anything using Target.Buff to work reliably with Bellow. It would often recast it too early even though the recourse had not hit yet.

Ended up making a simple LEM that watches for the recourse to hit and recasts bellow. Then I have KA just firing bellow with a |Once tag to get the first one out.

That's because more often then not, when it's fading the missing icon while it's flashing will cause it to incorrectly report that it's faded. May be better served with a timer. Which isn't really something that can be handled with a condition.

 

[Hanlons Razor]

That's because more often then not, when it's fading the missing icon while it's flashing will cause it to incorrectly report that it's faded. May be better served with a timer. Which isn't really something that can be handled with a condition.

True, I noticed that when I was trying to debug and /echo the Target.Buff while it was fading. Timers are tough because I found that the recourse hits in anywhere from 18 to 25 seconds instead of just 18 seconds every time... probably related to server ticks. The LEM to just fire it again when the recourse hits feels like redneck engineering, but at least it works.

Makes me feel bad for anyone trying to min/max necro output with a macro.

 

[Bolbod]

hanlons, I have no talent for writing this stuff out, mind sharing your LEM?

 

[Hanlons Razor]

hanlons, I have no talent for writing this stuff out, mind sharing your LEM?

I'm really bad at this stuff too, so mine is extremely crude. It hasn't caused any issues for me yet, but it probably could b/c it doesn't do any checks. I'd rather have someone who knows what they're doing update it before I encourage anyone to use it. But here it is, at least as a starter template.

#.#You hit #1# for #.# points of magic damage by Boastful Conclusion#.#

 

[BlankStare]

I also apply a Once tag on it due to the endurance resource it saps away after 30-60 minutes. Unless you're sitting down to med you won't have endurance for it most fights anyway.

 

[Hanlons Razor]

I also apply a Once tag on it due to the endurance resource it saps away after 30-60 minutes. Unless you're sitting down to med you won't have endurance for it most fights anyway.

I only use it on named/raid bosses, generally. Not worth using it on a trash mob that dies in 6s.

 

[Bolbod]

UPDATE: so the lem posted by Hanlons Razor works perfectly, I had about 5-10 minutes after downloading the lem program of learning how to input events, and it absolutely solves the problem for Boastful Conclusion procs. If you set it up as a text event, it will monitor your chat log for the specified command in the body of his reply, and then .Lua he shared will automatically recast boastful bellow after that chat line is observed!

 

[Searx]

I do the |once for exping, then on a raid fight audio trigger on Gina for the hit, then just made a Cwtn to tell bard to hit 3 to re-up. Probly the crudest of all but if your tanking on a raid what's one more AT to have to hit a button

 

[pascualito]

Using Kissassist
Can you guys please check if this condition for BARD Boastful Bellow works, to avoid recast before ends without damage, need more testers :-)
can use on [DPS] or [Burn] section:
; EXAMPLE
[DPS]
DPSOn=2
DPSSize=10
DPSSkip=0
DPSInterval=1
DebuffAllOn=0
DPS1=Fierce Eye|100|Cond7
DPS2=command:/pet swarm|100|Once
DPS3=Blade of Vesagran|100
DPS4=Unified Phoenix Feather|100|Cond2
DPS5=Miniature Horn Of Unity|100|Cond2
DPS6=Cacophony|100
DPS7=Lyrical Prankster|100
DPS8=Bladed Song|100
DPS9=Boastful Bellow|100|Cond1
DPS10=Selo's Sonata|10|Once

; This way im able to cast more than one time for battle (mob) doing DMG, and be sure that Boastful bellow do DMG before be recasted, cuz refresh timmer is short than dmg timer, that makes recast without dmg

[KConditions]
ConOn=1
CondSize=1
Cond1=${If[${Me.CastTimeLeft[Boastful Bellow]} < 32000, 1, 0]}

; Can you guys test this an tell me how it goes? thanks in advance, sorry bad english

 

[ctaylor22]

There was a change made a while back to help with this issue. Check out this Update.

 

[pascualito]

There was a change made a while back to help with this issue. Check out this Update.

Was my fault havent readed this update, THANKS

 

[SirMSDC]

There was a change made a while back to help with this issue. Check out this Update.

the problem with this update - it borked the twist - Restarts or fails on new mob...

 

[ctaylor22]

@SirMSDC I don't remember there being any changes to the twist code in this last update. I will check that out and get back.

 

[ctaylor22]

I check the last 2 versions of Kissassist and there were no changes to the Bard code.

 

[SirMSDC]

I check the last 2 versions of Kissassist and there were no changes to the Bard code.

Thanks i will try it here again and report back. i noticed some weird interactions when using MQ2Twist as primary over Twist in KA.

 

[reedreddington]

Are you sure it isn't just EQ being EQ? There is a known bug where it can just lock out all songs or items unless you /stopsong.