List of Bugs and issues with the Barbarian Class

[Shade]

PM from MadFloyd:

I thought I'd let you know that we fixed Supreme Cleave.

This was a curious situation:

1) we received NO bug reports on this from players.

2) Our QA thought it was working fine (as per description), but thankfully Eladrin took a deeper look and found & fixed the problem. It will go out in a patch to Update 1 (not sure of the timing at the moment).

QA sounds like they never actaully test anything. I think Turbine should be paying me more then what they pay them. I personally submitted the report on supreme cleave several times months ago.
Now I can't say anyone else has.. But I would think so? So question for forum goers.. Did you actually submit a bug report on supreme cleave?

[Strakeln]

I submitted the bug once on Llammaland and once on the live servers. Both on the first time I logged in after they were updated, if that helps.

[cforce]

PM from MadFloyd:
QA sounds like they never actaully test anything. I think Turbine should be paying me more then what they pay them. I personally submitted the report on supreme cleave several times months ago.
Now I can't say anyone else has.. But I would think so? So question for forum goers.. Did you actually submit a bug report on supreme cleave?

Sounds like bug reporting is broken. You should bug report that.... oh. Wait. Never mind.

But seriously, a bug in bug reporting explains a *lot* of stuff that seems to make it past the test server.

[Gunga]

PM from MadFloyd:


QA sounds like they never actaully test anything. I think Turbine should be paying me more then what they pay them. I personally submitted the report on supreme cleave several times months ago.
Now I can't say anyone else has.. But I would think so? So question for forum goers.. Did you actually submit a bug report on supreme cleave?

When did MF post that?

[Shade]

It's nice we finally got Supreme Cleave fixed. Hopefully a dev will read this thread and maybe fix some of the other glaring bugs we have.

re: Gunga - he never did, it was a private message just to followup our earlier conversation.

Updated bug 6 - as I've finally tracked down the cause and reason behind it. Doesn't seem intended but it may be: Dungeons scaling directly effects frenzy self damage. So solo on normal, often you take less damage from it, and in large groups on normal, you can take more then is normally possible.

Also dungeon scaling is in effect on elite (which devs have said was never intended), but it is quite clear to see if you adjust your damage scaling number colors - lotsa purple numbers floating around once you reach 5/6 party members. But this bug is more commonly seen on normal, as elite seems to scale a bit less the normal.

[Shade]

List updated.

FB set bonus bug added.

[Shade]

Listed updated.

Berserkers Fury (Barbarian pastelife selectable feat) added as bug number 8. (Hitpoints don't work)

Player concern that the feat is just poor overall added.

Related Warforged specific bugs section added.

No known bugs fixed at all in the last.. Ever?

They keep on piling up. Any dev responses to state that any work is ever being done on this heavily bugged class?

[eulogy098]

I would like to see something about the broken cleave mechanics in the ""Issues and Player concerns:"" area. Particularly regarding Cleave being one of our required feats, feats that are of a high cost to Barbarians whom have no bonus feats.

Neither cleave or supreme cleave have earned a spot on many barbarian hot-bars, and that is simply sad.

Easy fix- Remove cleave from requirement for Frenzy, replace with Toughness, Stunning Blow, or if they insist on this being a 90% loss feat even something like Iron Will.

Better Fix- Reevaluate all Cleave mechanics swing time. Have all of these abilities work more along the lines of a Paladins Smite. In the current state of the game, using cleave no matter how many monsters surround the combatant- it is always a DPS loss.

It is this players perspective that no feat should be a total, complete, and absolute loss. Cleave, for any class or build currently is.

[eulogy098]

bump for justice.


keep this post up front


even if we don'get fixes at least we can cry real loud like

[Monkey_Archer]

#5 Barbarian capstone should be updated to describe the 10% attack speed bonus they are apparently receiving.

Barbarian capstone speed

Fighter capstone speed

Clearly identical.

[eulogy098]

#5 Barbarian capstone should be updated to describe the 10% attack speed bonus they are apparently receiving.

Barbarian capstone speed

Fighter capstone speed

Clearly identical.

that doesn't look very clear to me

[Gercho]

Well, one thing i would really like to see, is improve standing THF attack speed to match twitching attack speed, i dont want to nerf the twitching speed, but make it unnecessary, its ok if you have to move for tactical advantage, but moving for a technical advantage when beating a portal to get more dps is stupid imho.

[Carpone]

This should be listed with the other bugs instead of classified as a player concern:

2. Rage animation time varies greatly depending on race and weapon style - and if interrupted will not activate, but will start a cooldown and waste a use.
This is really not acceptable as the PnP version doesn't have some way to interupt it, and it doesn't seem intended. Also there is no reason for the ability to have a 1 minuit cooldown - being you may not use it again while raged anyways, no cooldown is nessasary at all, its just an arbitrary artificial penalty we get for no reason.
Things that can interupt rage, wasting a charge and starting an unnessasry cooldown:
Pressing the movement keys after starting the animation.. Very common one that makes no sense.
Getting tripped... Melee, cometfall or otherwise.
Grabbing a ledge
Getting CC'd in any way really, hold, stone, etc.
Also how likely you are to get interupted depends on your race and weapon style.. Doesn't make much sense that a sturdy dwarf is more likely to be interupted by a trip then any other race.

It's so aggravating to waste a rage *and* then have to wait a minute to activate it again when, as a player, I didn't do anything "wrong".

The animation oddities with this bug is reminiscent of an older issue in Age of Conan. There, female models animated slower and subsequently had lower DPS compared to male models with the exact same stats+gear.

Thanks for keeping this list up-to-date Shade!

[Monkey_Archer]

that doesn't look very clear to me

Whats not clear about it?
Both the barbarian and fighter with capstone are attacking at the same speed (~112 attacks per minute)

[mediocresurgeon]

Excellent list, Shade. Thanks for keeping it updated and organized!

[eulogy098]

if someone capable of having any effect on the game development would read and respond to this thread, ddo would be a better place.

I'de settle for turbine public acknowledgment of these bugs, not even demanding fixes.

[Shade]

This probably won't surprise anyone:
Update 5 didn't fix a single barbarian bug or issue. It infact just added more.

It was entirely focused around nerfing the game so I guess there wasn't any tiime for that.

[BlackSteel]

This probably won't surprise anyone:
Update 5 didn't fix a single barbarian bug or issue. It infact just added more.

It was entirely focused around nerfing the game so I guess there wasn't any tiime for that.

well actually it did partially fix the 'bugged' capstone. took away what wasnt supposed to be there, but didnt fix the other broken aspects.

[eulogy098]

So they took away the effect that was probably only equaling the DPS the capstone is likely intended to give? Typical.

[BlackSteel]

So they took away the effect that was probably only equaling the DPS the capstone is likely intended to give? Typical.

doubtful.

you have any idea how much damage you'd have to increase glancing blows by to equal a general 10% swing speed or the now 10 % double strike?

enough for 100% weapon procs wouldnt equal a 10% jump. heck with the glancing nerf its not important anyway.