1st Savage Warrior Warning

[SpookyGhost]

Is it: Max HP + Thrill -> get brought to 1 -> Thrill wears off -> die?

[Ekimmak]

Is it: Max HP + Thrill -> get brought to 1 -> Thrill wears off -> die?

No.

What happens is, he finishes the cast of the attack, then thrill wears off, then the damage hits and I die.

Because I suddenly lose 20% of my health just before an attack worth 99% of my health hits.

A slight tangent from the post, but for the same attack I believe, cover also gets you killed as a PLD. The person you are covering will take no damage, and you will take "your total HP - 1" + "targets HP - 1" in damage, instantly killing you.

This is more deceptive than thrill because thrill makes sense, whereas this attack should ignore cover in theory.

I say they need to take another look at these HP to 1 skills. Either change them to bypass cover, or change how they actually take effect so we don't end up with these unfair deaths.

[SpookyGhost]

No.

What happens is, he finishes the cast of the attack, then thrill wears off, then the damage hits and I die.

Because I suddenly lose 20% of my health just before an attack worth 99% of my health hits.

Ahh gotcha. Sorry, still at 64 so I've no idea what's going on in Omega outside of an O4S stream I watched. P:

[Lambdafish]

What happens is, he finishes the cast of the attack, then thrill wears off, then the damage hits and I die.

Which makes sense because the damage that you will take is calculated when the cast finishes, which affects any buff/debuff on any move. If I hallowed after the cast time of a tank buster is finished but before the attack hits, I will still die.

[Ekimmak]

Which makes sense because the damage that you will take is calculated when the cast finishes, which affects any buff/debuff on any move. If I hallowed after the cast time of a tank buster is finished but before the attack hits, I will still die.

I know why it happens. But it still shouldn't happen.

An expiring cooldown is killing me. Not clicking a cooldown too early, the cooldown wearing off in a very specific time frame is killing me, when a fraction earlier or later would let me live.

This isn't even like dying to a tankbuster because Bulwark wore off, this specific mechanic is designed NOT to kill you, because it's timed so that it gets no chance for an auto-attack. Make the healers panic, yes. But it's not supposed to kill you.

[Lambdafish]

An expiring cooldown is killing me. Not clicking a cooldown too early, the cooldown wearing off in a very specific time frame is killing me, when a fraction earlier or later would let me live.

This isn't even like dying to a tankbuster because Bulwark wore off, this specific mechanic is designed NOT to kill you, because it's timed so that it gets no chance for an auto-attack. Make the healers panic, yes. But it's not supposed to kill you.

Can't you turn the buff off by clicking on it when the ability starts casting?

[Quor]

Can't you turn the buff off by clicking on it when the ability starts casting?

That's the issue I believe. For the sake of example I'll use smaller numbers just so it's easier to show.

WAR has 1k life. He uses ToB to get 20% more life, putting him at 1200.
Boss begins to cast the 99% dmg skill. It sees that this WAR has 1200 HP, so the game sets the damage at 99% of 1200.
ToB wears off, placing the WAR at 1000 HP.
Because the cast from the boss started when ToB was up, it was calculated for 99% of 1200 HP, meaning it deals more than 1000 points of damage, killing the WAR now that ToB has worn off in during the narrow window of the cast bar.