Cursed Ground Support + Hexblast

"

SirGuySW wrote:

"

Crevox wrote:

Probably exclusively for the reason that spamming Hexblast on Cursed Ground would be too powerful.

Is Hexblast + Blasphemy not just as powerful?

Hexblast + Blasphemy is actually more powerful than this would be if it worked, because the re-applied hexed area moves with you.

I predict that the blasphemy behavior will most likely be chnaged to match this cursed ground behavior sometime in the future, probably best to enjoy it this league while it lasts.

"

Mark_GGG wrote:

"

aggrofee wrote:

As far as i am aware with the old "Doomsday"-keystone the hex was instantly reapplied after you hexblast the enemy, as long as the Doomsday-area persisted.
(correct me if that´s wrong please)

You are indeed wrong. Doomsday had the same behaviour as the cursed ground - the doom-related parts have been removed and the duration extended, but the core implementation is still the same as the keystone was. This is the same behaviour as Lightning Conduit with things like Skitterbots applying shock in an area around them.

This is not a bug.

Thank you for the answer!

Is it possible that something in Hexblast's behaviour changed then?
Because it now removes either the blasphemy-applied curse or the cursed-ground-curse. (just tried it, it seems to be random which one)
Whereas with Hexblast in the past (3.17 for me - maybe it changed after that) it always chose the blasphemy, because when i spammed Hexblast, while the Doomsday-Keystone was "charging" i always got the massive hit at the end.
With your above explained mechanics, it must never have chosen the Doomsday-Curse then, or else this wasn´t possible.

I think it would be cool, to have a consistent order (Cursed Ground > Blasphemy or the other way around - even though both have "no duration"), to better plan and use builds around Hexblast/Blasphemy/CursedGround.


Like some people pointed out, the behaviour with Blasphemy seems inconsistent then and it shouldn´t reapply either?

"

Mark_GGG wrote:

now it picks the one with the highest remaining duration.

Isn't it "lowest remaining duration"?

Curses FAQ

"

Can you change Hexblast so that the Hex it removes isn't random?
Yes, instead of removing a random Hex, Hexblast will remove the Hex with the lowest remaining duration. (i.e. whichever one would naturally expire first.)

I just did some quick tests and it does appear to be lowest.