Why impose Slow in melee?


log in or register to remove this ad



I understand Slow from a Defender.

What I don't understand is a power that inflicts Stunned and Immobilized (save ends both). Stunned creatures are already immobilized by virtue of being unable to act.
 

Zurai said:
What I don't understand is a power that inflicts Stunned and Immobilized (save ends both). Stunned creatures are already immobilized by virtue of being unable to act.

What if you're immune to one condition or the other? Are undead still immune to stunning?
 

Zurai said:
I understand Slow from a Defender.

What I don't understand is a power that inflicts Stunned and Immobilized (save ends both). Stunned creatures are already immobilized by virtue of being unable to act.

Some monsters can negate stun but can't negate immobilize. Still there are only a few like that so it is odd.
 


In regards to Zurai, maybe you still have to roll against each effect separately, and they say (save ends both) because a save to each effect will end both effects and they felt Stunned (save ends) and Immobilized ( save ends) was too redundant. That's the only logical reason I can think of. Same for when a power stacks weakened and stunned.
 

The phrase (save ends both) means that you save for both effects as if they were one, and one save ends both conditions.

So really the only reason for Stun and Immobilize with the same power is if something is immune to Stun.
 

sfedi said:
When is it useful for a Defender to impose the Slow condition on an enemy?

1. Against a lurker or skirmisher that's bouncing in and out of the fight.

2. When you really don't want a target to slip by you and get to the squishy back line.

3. When you want to do a strategic retreat. You hit, you back away (probably suffering a free strike). Hopefully a slow enemy won't be able to close the 5 square gap, and next turn, you book it.
 

Pets & Sidekicks

Remove ads

Top