i didn't see it, but may have missed it
the WF extra glancing blows don't work when raged
As expected, zero bug fixes or even mention of this in known issues for lamannia update 1.
Personally, I feel that the only fix needed for the various boosts is to just get rid of their activation time; if you only lose a fraction of a second (time to press the button), then they would be fine.
One real problem with frenzied berserker is that it requires the boost, as other PrEs do, but does nothing with it. I'd really like to see those put to some use via the prestige enhancement the same way they get used by paladins and fighters. Maybe change Frenzy to costing a boost? Or add something else? I hate seeing prerequisites that are just included as filler.
The PnP version has Inspire Frenzy, which causes your allies to gain some of the benefits (and penalties) of frenzy as well. Perhaps barbarians could gain this feature? Inspire Frenzy could eat an action boost to grant allies +2 Str and Con and the vicious ability. Maybe add an accept dialogue for this?
Useful links: A Guide to Using a Gamepad w/ DDO / All Caster Shroud, Hard Shroud, VoD, ToD Einhander, Elochka, Ferrumrym, Ferrumdermis, Ferrumshot, Ferrumblood, Ferrumender, Ferrumshadow, Ferrumschtik All proud officers of The Loreseekers. Except Bruucelee, he's a Sentinel!
Camp Naughty Bad FunJichael Mackson
Some news on supreme cleave.. Most of the devs still don't believe the bug exists.. But I spoke to one of them (Madfloyd) ingame on Lamannia so at least he knows now and said he would try to get it fixed by the first patch after update 1 (update 1 being pretty much done now).
Here is a pic of the conversation.
Would really like to see point #6 in the OP adressed at some point in the future.
Interesting conversation you had there Shade.
970 sp and counting
Help Fix Ranged Combat for Everyone. Come help complete the DDO Wiki
Yes, very. It shows what we pretty much all thought: there is a serious flaw somewhere in their bug gathering process. In this case, not only the bug had been bug reported certainly over a thousand times but it has been repeatedly bought up on the forums.
There are so many bugs that have been around that have just never been fixed. Maybe we should start another thread and just list them all there.
DDOwiki.com, #1 source for DDO information.
My guess is that Madfloyd does not work with bugs in general or bugs of this sort. He works on developing systems as evidence by his involvement with Dungeon Alert, the Combat system (both changes), etc.. He is heavily involved in Reincarnation which is another systematic change. There is mention of a database where presumably errors are stored, but who knows how comprehensive that really is. I wonder if the appropriate person to pin down is 404 Error. He probably fixes or is involved in this bug work in some fashion.
Norg Fighter12/Paladin6/Monk2, Jacquiej Cleric18/Monk1/Wiz1, Rabiez Bard16/Ranger3/Cleric1, Hangover Bard L20, Boomsticks Fighter12/Monk 6/Druid 2, Grumblegut Ranger8/Paladin6/Monk6, Rabidly Rogue L20, Furiously Rogue10/Monk6/Paladin4, Snowcones Cleric 12/Ranger 6/Monk 2, Norge Barbarian 12/FVS4/Rogue4. Guild:Prophets of The New Republic Khyber.
404 is the one in charge of reading our bug reports (well, there are most likely more than one but he must have the senior rank among those since he has been playing DDO for over three years and can parse over our bugs quicker than anyone else in the QA team) and submitting it to the programmers (like Codog). So, yes, he's the best one to talk with about that kind of stuff since he is the one reading our bug reports.
But, from the tell exchange, it seems that MadFloyd was at his office looking at the list of acknowledged/reported bugs within Turbine...
DDOwiki.com, #1 source for DDO information.
Brings up my idea that all bug reports, minus exploitive ones, should be open for players to look at. They should remove all player information though.
In this case I am sure Shade had bug reported the issues he brings up here but then we could see what exactly was reported and if its not a "known" issue the bug finders amoung us will kinda know what other information to send in, if only for someone else to confirm that they have the same issue via official communication lines.
Though given all the stuff we manage to spade out I find it hard to believe that we aren't providing enough information.
970 sp and counting
Help Fix Ranged Combat for Everyone. Come help complete the DDO Wiki
This has to do with how they allowed us to use potions on other players by making them function as a clicky rather than a potion. I personally think they should fix it so that raged characters can't use potions at all. They're raged, which doesn't make it very likely they'll rationally pick out which potion they want to use.
970 sp and counting
Help Fix Ranged Combat for Everyone. Come help complete the DDO Wiki
When I worked as a software engineer some years ago I can recall one of the primary duties of management was to keep the junk away from the software engineers so they could continue to develop new product. QA is more an extension of management then development. As a part of management QA's role is in part to screen junk away from the developers. Supreme cleave is not junk by any means but the PRE bugs seem to have a lower priority then some of the other bugs. I wonder if that list the devs have is a comprehensive one or more just a list filled with higher priority bugs. We just do not know its Turbine's shop to run.
Norg Fighter12/Paladin6/Monk2, Jacquiej Cleric18/Monk1/Wiz1, Rabiez Bard16/Ranger3/Cleric1, Hangover Bard L20, Boomsticks Fighter12/Monk 6/Druid 2, Grumblegut Ranger8/Paladin6/Monk6, Rabidly Rogue L20, Furiously Rogue10/Monk6/Paladin4, Snowcones Cleric 12/Ranger 6/Monk 2, Norge Barbarian 12/FVS4/Rogue4. Guild:Prophets of The New Republic Khyber.