Hit by Maelstrom with Obsidian Flesh up?

I was going to solo-run my new elementalist from THK to grotto, and I loaded up with obsidian flesh to get past ice imps. However, even with OF up they could cast Maelstrom on my ele. That shouldn't be possible, right?

I wasn't expecting any problems so I was using the standard vaettir farming build: OgVEMKGJz4I91GfVe4SwAkNWiA

Well according to maelstroms description - you create a maelstrom at the target foe's location.

I guess they were not targeting you with a direct spell but rather using you as a marker to designate a location for maelstrom to appear.

-edit-
no actually that doesn't make any sense to me either lol

Obsidian Flesh only blocks spells casted on you. If the spell was cast on anyone else and you get in it's area of effect, you get hit by it.

non targeting huh?
@OP:maelstrom does need to target you to be cast on you. if you got hit by it you were in the aoe of the spell from when it was cast on something else or obsidian flesh wasn't up.

This usually happens because of someone else being near you which ends up in you catching some of the aoe damage aswell

Well, you said you were solo-ing, so i'm going to assume you weren't bringing any henchies or heroes to get targeted. You said it was a new ele...you didn't use that new fire imp or w/e, right?

Only thing I can think of (assuming you did keep obby up) is any pets in the area? I don't know the run real well, but if you damage any of the green tamable creatures out there, they could become a target for the imps.

Should block Maelstrom. Perhaps you ran through just after one of those battles between monsters in the area. Check to see if there are any of those groups that will fight each other... your timing would have to be ridiculously bad but it could happen I suppose.

I know Ob Flesh and SF stop Maelstrom, as it has to have an initial foe to target at which to create the AoE. So either something was nearby or you walked into the immediate aftermath of a monster battle.

And don't forget, Obsidian Flesh might have simply been down for a couple seconds. Seems the most likely of the options.

Okay if you read Maelstrom's description it says: Create a Maelstrom at target foe's location.

So in essence it doesn't target the player, it targets the area around the player. It's the same with firestorm afaik.

So ya, seeing how it doesn't target the player itself Obsidian Flesh doesn't block it.

Maelstrom and Fire Storm both need a target to be casted. Obsidian Flesh prevents a player from being targeted by spells. While Obsidian Flesh cannot block Maelstrom which has already been cast in the player's location, it prevents any Maelstrom or Firestorm from being casted on the player.

It's not casted ON the player, it's casted on the GROUND the player is at. It merely uses the player as an indication for where it should go


Or something. It's not a bug or anything, just can't explain it very well.

to Earth:
it doesn't work like that
if you've ever played ele, you'll know that you still need to target a enemy to cast it on him, be it a AoE or normal spell

to OP:
they've probibly targeted a neutral pet, a hero/hench, or when your obby flesh is off
given that Maelstrom's casting time is 2 seconds, it is not very possible as Obsidian Flesh is 1 second casting time so it would be up before they could finish casting

That's exactly what I'm not saying, but I'm not sure how I can explain it any better. Too tired


Pretty sure I'm right though.

i think ur tryin to get at the fact that things like [glyph of immolation] doesnt work wit aoe spells since they dun "target a foe directly"

however, those rules do not apply to [obsidian flesh] [spell breaker] or [shadow form] afaik

too lazy to test
and dun care nuff to really find out

but im 99% sure, maelstrom will -not- cast on a target for these enchants


this guy is rite

the spell needs a target to be cast
but the dmg is not "target dmg"
if that makes sense

which i think is why it wont work wit [glyph of immolation]
it needs "target dmg" not "target cast"


only pbaoe will go thru these enchants (point blank aoe)
things like [aftershock] [flame djinn's haste] etc

think of it this way (because it does target the player, testing will show this) :
the spell targets the player. one property of this player is his location. maelstrom reads the location property of the target at the time the spell finishes casting and creates an area of effect on that spot.
people seem to be confusing "target foe's location" to mean "target location occupied by the foe you have selected but who isn't this spell's target". "target foe's location" literally means the location occupied by the foe you target. i don't see why this confusion arises but it certainly does. :/

if the spell description says "target", that spell will fail if the target has Obs Flesh or a similar skill in effect. all hostile spells need a target unless they are PBAoE like [[aftershock]. this is why a perma obs flesh/SF ele or sin can successfully kill coldfire nights, which have [[maelstrom] as one of their skills.

the thing about going anywhere in southern shiverpeaks is that the different species of foes are hostile to each other. so if there were any tengu, trolls, grawl, or anything else (sorry i don't really remember the area very well) around you, the ice imp can target that grawl, for instance, but since [[maelstrom] is AoE, you will still get hit by it if you are within the area of its effect.

My only explanation would be a monster casted maelstrom on another monster, and you were in the wrong place at the wrong time.

I know why you got hit by maelstrom. i get hit sometimes too

the thing is that you use ''Obsidian Flame + other skills + glyph + obsidian flame''

you got hit cuz obsidian flesh ended when you were recasting it. after you casted it you were already a target of maelstrom so the only thing you can do is just move out of it.

i bet thats what went wrong cuz sometimes it happens to me

hope you understood my english kinda sucks lol

My only guess is that they cast it on the King or one of the other dwarves while next to you.

This. Maelstrom was cast on you when your OF dropped, you didn't notice (perhaps the first hit hadn't landed yet, there is a slight delay between the casting of Maelstrom and the time the first hit lands), and your OF got interrupted.

The idea that Maelstrom and other AoE spells don't target the player is just wrong, period.