aDifferentHandle wrote on May 31^st, 2012 at 1:42pm:


In all fairness to Axer, he has a point there. It's not really politic to ask people to go flag for a raid and then wipe their characters.

Turbine really need to sort their character copy tool out. At least allow people to recopy if it fails. It's ridiculous that we're being asked to test level 20+ content and it's a struggle to even get toons over to do so.

http://forums.ddo.com/showthread.php?t=375737

The days of spamming Supreme Cleave appear to be over.  I read about this last night but was too busy playing the game and poking a soul-scarred Russian with a stick.

Anyway, I believe this will generate some measurable drama amongst the melee player community.  But my agreement with the posts is tempered by laughing at Shade having his bag of tricks blow up in his face. 

All that said, it's still a messed up change.

AtomicMew wrote on May 31^st, 2012 at 4:57am:


see? made ya laugh!
so are we done here?

Can I ask you for a favor?

Madcow430 wrote on May 31^st, 2012 at 4:20pm:


I haven't bothered with the beta much since I'm working on a paper right now (even though yes I know that this would be the best time to go check things out, in terms of having input on the game) but this one caught my eye.

I suspected that the lack of cooldown with supreme cleave might've been considered a bug, and this seems to confirm it -- or at least, that Turbine saw fit to change it, like the original twitching or adding invisible walls to Big Top (i.e. not a "bug to ban over" but a "bug to go and fix").

The other cleave attacks have a lengthy enough cooldown to where you wouldn't bother spamming them in combat. Supreme cleave was different in that the cooldown was pretty small (but not zero), just long enough to get a regular attack in before you do another supreme cleave. I suspect that some programmer forgot to set the cooldown of supreme cleave to match that of other cleave attacks, and that thus it got pretty much the "default" cooldown time of ~1 second for doing regular things.

Supreme cleave is affected by the inherent speed of the weapon; greataxes and mauls are faster weapons, while falchions and greatswords are slower weapons. Thus you attack much faster spamming supreme cleave when you're using a greataxe than when you're using a greatsword (such as ESoS). Depending on your setup, it amounts to roughly 17% more DPS on your primary target than standing still and swinging (which I think is what publicly available DPS calcs assume) if you're using a greataxe (crafted HBoGLOB) whereas it'd only be about 6% more DPS than standing still if you're using a greatsword. So if the DPS calcs say you'd do around 320 DPS and you're using a greataxe, you'll really do 320 * 1.17 ~ 374 DPS when spamming supreme cleave. I'd have to go back and re-check my calculations, but if I remember right, using a crafted HBoGLOB greataxe and spamming supreme cleave will essentially be the same DPS as using a devil's ruin-slotted ESoS and spamming supreme cleave.

Some people have suggested using scleave -> attack -> attack instead of scleave -> attack, but although the attack speed is slightly faster, you lose out on the glancing blow during the second attack, and so you'll do less DPS overall (assuming you took the THF feats). It's better to just spam the supreme cleave hotkey.

It's been known for quite some time; in fact, I had already done the video analysis prior to Shade blabbing on the forums about knowing some super duper secret new buff for barbarians which was unquantifiable and showed how number-crunching doesn't work (actually, quantifying it was done in exactly the same way, you just video record the attacks and count up how long it took to do how many attacks, which is apparently beyond the comprehension of some people), but wasn't sure if it would be considered a bug. I also remember one of the other guys who did attack speed work posting that he won't really be posting numbers on it for the same reason, although I'd have to look around for that post. It's no coincidence that people in Over Raided favor greataxes though.

This whole mess of course could be avoided if Turbine went about normalizing all the attack speeds, such that the animation for each attack took exactly the same amount of time relative to each other (and then are modified by the same amount by attack speed modifiers), but it seems like they did such a pass a few years ago and failed at it, resulting in the current system. It may also be that it gets too much into the code, since graphics would be involved (since attack speeds are tied to the animations), and they figure that changing things would make it more of a mess, or bring about new problems.

<3

That post is hilar.

Ironical the Bionicle wrote on Jun 1^st, 2012 at 1:14am:


FlimsyFirewood
Quote:

This is because their designers can't play the game on casual.

Epoch wrote on Jun 1^st, 2012 at 9:31am:


Nah it was also made to keep us from whining every time we have to reflag for Kween.
At least ADQ1 on Casual is a 2 minute job if nobody pikes.

Eladiun wrote on Jun 1^st, 2012 at 8:13am:


Eladiun wrote on Jun 1^st, 2012 at 8:13am:


...just a post to piss off Maj! 

I read it as:
my ego brings all the little epeens to the yard
Damn right its better then yours,
I could teach you but I have to charge.

Epoch wrote on Jun 2^nd, 2012 at 8:58am:


Aw, c'mon now, he just wants someone to hold his OPnis. It's lonely at the top. Particularly when you're so clearly a bottom.

Honestly, there's typically a core nugget of truth to fish out of the sea of crazy. Unfortunately, he has a propensity for throwing in suggestions without considering the side effects. That's what makes him dangerous to himself and others.