|
My intent wasn't to get into the whole "X class takes more skill than Y class" argument, it is, as you said pointless.
That said, the comparison still holds, as a tank, by using your abilities you cannot drop below a base value of x threat (basically autoattack +/- assiciated modifiers), using sunder, shield block, revenge etc only serves to improve your treat generation. This can be expanded to rogues also, the baseline is auto attack, using specials only improves upon this. Granted SS spam may not be the best idea, but it's still higher than autoattack.
Classes that DPS via cast times (Mages, Warlocks *sorta*, Elemental Shamans and Balance Druids) can happily spam a nuke until the end of time and not suffer a net loss of damage, granted, it may not be optimal, but there is still no net loss. It is only when you attempt to combine these two systems that you get the horrible system that is Hunter DPS.
As far as my limited knowledge of casting/melee-ing goes, casting anything other than an instant resets the swing timer. So casting a spell essentially functions as if you had swung your melee weapon, this is a system where melee is dependant upon the cast timers. Instants do not effect the swing timer, so your Fire Blast, SS, Revenge, Stormstrike, Shred, Swipe etc will not in any way affect the timing of your melee weapon damage.
Where this all falls down is the 0.5s "cast" that Autoshot has, which is intended, assumedly to prevent the use of a constant stream of ranged damage whilst moving which is understandable, (though with practice this can be achieved by stopping every [attack speed - 0.5 seconds] to fire an auto and resume running. This 0.5s cast is affected by anything the player does, any action that causes a GCD supersedes and pushed back this invisible cast timer, which is completely contradictory to the experience with any other "melee" ability (Slam excluded *shakes fist at special cases*).
In any case, the ability of your damaging specials to actually lower DPS below a baseline of doing nothing is counter-intuitive at best, making Steady an instant would alleviate a lot of the drama with clipping, but ultimately I believe the only solution is to remove the 0.5s cast on auto and be done with the whole argument, that way Blizzard gets to keep their "weaving" which whilst it was originally unintended, they seem to have fallen in love with, and allows the general hunter population a shit-ton more leeway as far as learning curve and latency goes.
Last edited by Elvandir : 11/02/07 at 1:18 AM.
Reason: *spelling*
|