Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="Rechan" data-source="post: 5223933" data-attributes="member: 54846">Not true. I really hate this statement.The only way the controller prevents hits is 1) moving enemies around the battlefield, and 2) conditions/debuffs. The former doesn't prevent hits. It prevents OAs, and it slows down/eats up enemy movement, certainly, but it's not stopping the monster from charging. The latter has an impact because it eats up the enemy's round or actions, or makes it less likely to hit. A Defender defends simply by saying "If you don't do what I say (in almost all cases: attack me), I'm going to punish you". A Shielding Swordmage is a back row defender because SMes can run away and still do their thing. A back row defender then would punish a target for not attacking him or a designated target. A good example of this is the Shaman, whose pet can make OAs to enemies, and the shaman can funnel attacks through his spirit. So a back row defender would basically say "Hit my pet or else". And a ranged defender would say "Hit me, or hit someone I designate, Or Else". A better destinction than a Controller than being a Back Ranks Defender is that a Defender is a reactive Controller - controlling by the threat of attack or controlling when responding to an enemy. Controllers do less as immediate interrupts, but are pro-active in doing something to a target that thus limits their options (daze, immobilize, etc). I mean if we can have a melee controller (Druid), then a ranged defender isn't all that unreasonable, and it's just a matter of time before that class pops up.</blockquote>

Verification