That's my understanding as well. I mean, think about it, you could even stop moving for a split second to cast an instacast and then continue to book it.

My main is a mage, so I'm naturally happy about this limitation of hex, and it's lack of limitation (more or less) on me.

For a rogue, I'm not even sure it would make much of a difference either, honestly. Snare you, run up to you, and stop so they can attack. Now they're next to you, and you couldn't move out of melee range before they stand still and eat you.

Of course, it might be one of those things where there is a .5 second transition period between movement and casting/attacking. That would make more sense to me.

Or. It's meant as a PvE crowd control primarily and a PvP crowd control for people that don't know how to work around it.

I'm sure it will be just like controlling a critter. You can attack, but it will do 1 damage or somesuch, like when crabs attack you after you fear them accidentally in SV.

The movement is there so the CC'd target can run back to their healer and get cleansed in arena.

zzzzz

The spell on the alpha wiki has a typo. It should say "while hexed you cannot cast or attack". It's CC that lets you still move at a slowed speed, but not attack or cast at all.

This was my understanding as well. The player will retain his freedom of motion, but will not be able to attack or cast spells.

I agree with this interpretation, that definately seemed to be what they were getting at. Its just that its been poorly worded that seems to have caused this confusion.

This seems to be what I thought it was then, basically the same spell that Shadowpine Hexers put on you - you turn into a chicken and they beat on you.

I am however wondering how (or if) this will be categorized in PvP diminishing returns, as this technically does not make you lose control of your character. Therefore I'd have to assume this would not be affected by Medallion of the Alliance/Horde at all. Seems like a pretty powerful spell to me.

I thought the panel at WWI actually reinforced this concept of the spell, whereas the tooltip was very ambiguous prior to that.

Simply a tooltip error, I expect. In general, when looking at alpha/beta spells, if there's a major disconnection between the tooltip and the reasonable and/or established behavior for the type of spell in question, it's a pretty safe bet that the tooltip is incorrect and will be fixed later.

Wont happen, stop asking. Threat shouldn't be a problem anyways if your running with a good tank.

Well, lets give you an example of the tanks on my server. When I would try to get in a heroic Magister's Terrace group I would find a group all ready to go but one DPS (a tank, two dps with cc, and a healer) and when I'd ask if they needed another dps the response I would usually get was "sorry, we need cc." Even when they already had 2 cc classes.

Hopefully that gives you more of an insight.

So if they can move and do damage, even if its only 1 point of damage, they can attack the shammy and break their CC on his/her lightening shield, or a druid (thorns) mage (molten armor) or Pally (ret aura) for that matter

One of the reasons this kind of mechanic is so poor, is that for any melee class you will have auto-attack on. So if we forget about damage shields for a moment, just having auto-attack on means that unless you cancel auto-attack just before you cast, you may end up breaking the CC if they run back at you into melee range.

So a key use for this spell will be to make sure you get out of range of the mob since there is a 75% slowing debuff added to the CC. (which was probably added to prevent a CC'ed mob from just running at the nearest person with a damage shield.)