#Pressure on War Scream

1 messages · Page 1 of 1 (latest)

queen ore
#

So far as I've seen, the damage boost from Pressure on a Generalist-affected War Scream only applies if at least one enemy was hit by the damaging effect of the spell. I don't see why this would need to be the case, other than code jank reasons. It really should just apply by default imo

summer obsidian
#

I think sometimes it just decides not to work

#

earlier I was repeatedly using it in tcc and at no point got the stronger effect

#

only ever have the 8% from emboldening cry or vengeful spirit, when I should be getting 22% strength

queen ore
#

wait thats so so weird... it was working fine for me in notg, even against the boss

#

maybe the colossus is just bugging it out?

summer obsidian
#

no this was happening in other raids on the beta

#

sometimes it works sometimes it doesnt

queen ore
#

well that sucks :/

summer obsidian
#

you can actually see it work when I accidentally cast bash at the start of the clip but it never worked on any of the war scream casts

#

but Ive had times on the beta where bash wasnt working either when I was testing

#

though I think I will test bash casts a bit more to make sure that Im not just misremembering

queen ore
#

huh. well i guess this isnt really a feedback post anymore if the whole time it was a bug

summer obsidian
#

1 raid later and I can note that Ive now seen it say 22% strength in the chat message but only show 8% in the tab menu, however the duration was correctly showing 12 seconds for both resistance and strength, which is not happening in the video above

#

got a screenshot of the above behavior

#

also noticing that bash seems to be working consistently, even in run where war scream seems to not

#

so it seems to just be a war scream problem I guess?

#

Ive also had times where I casted war scream more than 12 seconds after a generalisted war scream that did not get the pressure effect and did not get a chat message of the war scream buff, implying it really did give 30 second duration (and therefore not just bugged in the tab menu)