Bug Alert: Non-functioning parts of Sorceror Capstone

[Junts]

The .25 addition to critical multiplier from the sorceror capstone is presently either non-functional or non-stacking. I have now tested this extensively with polar ray (conveniently, using 2x cold damage targets, where polar ray does 880-1020 damage per cast).

With:

1.5 base crit
+.75 3 enhancements
+.50 major lore item
+.25 capstone

I should have 3x criticals

I do not; I have 2.75 criticals, maxing at roughly 2780 crits in this situation. I am having a harder time testing out the other two portions: the difference in 3% crit is very difficult to test, and I don't really wish to sit and crunch the numbers to determine the damage bonus.

Some assistance in testing these two sections, as well as drawing further attention to this bug, would be quite helpful. Lets get this fixed in the first patch.

[Borror0]

[...] drawing further attention to this bug [...]

Bug report if you didn't and PM the thread to 404error.

If he complains about getting too much PMs, he just has to start his own thread.

[Junts]

I already did bug report and the PM is next; however, I wanted to enlist some other sorcs helping me test the damage amp and crit-chance portions of the capstone, and let people know why it seemed like it wasn't that effective.

[Shade]

Bug report if you didn't

Wouldn't waste my time.

I bug reported that the Barbarian capstone was mostly non-functionaly too, months before this patch went live. It's as bugged as ever now on live.

It was never read, the devs probably still don't know or care.

I'd guess both crit parts of the sorc capstone aren't functioning. I got it on my sorc and not really noticing a difference. I think the +10% dmg seems to work tho.

I imagine none of this was tested at all.

Probably the same reason the new sorc savant item sets don't work (so i've read, don't have one yet). Turbine has no such thing as QA.

[Strakeln]

As sour as Shade's post is, I have to say that it echoes my sentiments. I've long been blown away by the number of things that somehow slip through QA's nets. I understand why some bugs affecting existing things may not be caught... regression testing only gets more and more difficult with each release... but I have to say I simply don't understand why the new features were apparently never tested, or tested in such a poor and ineffective manner.

On top of that, many of these problems were reported... so even if testing budget is so limited that not everything can be looked at, they have lots of free bug reports that may help direct testing budget to where it is needed.

[SimVerg]

As sour as Shade's post is, I have to say that it echoes my sentiments. I've long been blown away by the number of things that somehow slip through QA's nets. I understand why some bugs effecting existing things may not be caught... regression testing only gets more and more difficult with each release... but I have to say I simply don't understand why the new features were apparently never tested, or tested in such a poor and ineffective manner.

On top of that, many of these problems were reported... so even if testing budget is so limited that not everything can be looked at, they have lots of free bug reports that may help direct testing budget to where it is needed.

The worst is when 404 comes in and says "Thanks we knew about it but decided it was a Go Live bug." By itself, that is actually a really helpful statement and I appreciate him doing it. However, they have a known issues list. It would be really nice if they'd update it or fill it out with an actual list of known issues for once.

[Borror0]

However, they have a known issues list. It would be really nice if they'd update it or fill it out with an actual list of known issues for once.

Their use of the known issues list is questionable. Many, many times in DDO's history where there known issues that were... not official known issues.

[TechNoFear]

As sour as Shade's post is, I have to say that it echoes my sentiments. I've long been blown away by the number of things that somehow slip through QA's nets. I understand why some bugs affecting existing things may not be caught... regression testing only gets more and more difficult with each release... but I have to say I simply don't understand why the new features were apparently never tested, or tested in such a poor and ineffective manner.

On top of that, many of these problems were reported... so even if testing budget is so limited that not everything can be looked at, they have lots of free bug reports that may help direct testing budget to where it is needed.

I am sure Turbine (but not individual devs) know of the bugs, even if QAT has not yet verified them.

It is a matter of priorities, based on the most limited resource (money or time).

Right or wrong, it appears that for this release the store was the highest and content only accessable at endgame was the lowest priority.

[MrCow]

After hundreds of casts of magic missile I can verify that neither the critical rate modifier works (tested with a base of 0% and the capstone, never had a critical magic missile) nor the critical multiplier works.

Also, after comparing magic missiles between my sorcerer with Force Manipulation I and the capstone who made magic missile damage of 4 or 5 and my wizard with Force Manipulation II who made magic missile damage of 4 or 6 (both should be adding up to 20% and thus should have the same damage numbers), the base damage component seems to not be working either.

[Strakeln]

I am sure Turbine (but not individual devs) know of the bugs, even if QAT has not yet verified them.

Unfortunately, that is not always the case.

Here, allow me to point you to a thread that is a perfect example of what I'm talking about. This bug was reported during beta, both in-game and on the forums, at least four times. It was also bug reported during live, in game and on the forums. This thread I link to is the first time they became aware of it:

Starts at post 12

[Junts]

Wouldn't waste my time.

I bug reported that the Barbarian capstone was mostly non-functionaly too, months before this patch went live. It's as bugged as ever now on live.

It was never read, the devs probably still don't know or care.

I'd guess both crit parts of the sorc capstone aren't functioning. I got it on my sorc and not really noticing a difference. I think the +10% dmg seems to work tho.

I imagine none of this was tested at all.

Probably the same reason the new sorc savant item sets don't work (so i've read, don't have one yet). Turbine has no such thing as QA.

I have one; they don't.

[Shandi]

You know Junts I too thought that my damage was lower than what it should be with this capstone. I will do more intense testing when I get home from work today. I will post screens and what not.

By the way when you say 2780 max crit is that with a mob that is weak to fire or not? Dumb question I know but I would like to know so I know what to compare for myself

[Junts]

You know Junts I too thought that my damage was lower than what it should be with this capstone. I will do more intense testing when I get home from work today. I will post screens and what not.

By the way when you say 2780 max crit is that with a mob that is weak to fire or not? Dumb question I know but I would like to know so I know what to compare for myself

Double-cold damage weak (fire elementals, use the ts elementals for easy testing), polar ray with superior glaciation and all avilable crit enhancements and major lore item. If you dont have glacial assault III, use the3 minute clickies from the telvi's sash belt.

[Ulurjah]

Wouldn't waste my time.

I bug reported that the Barbarian capstone was mostly non-functionaly too, months before this patch went live. It's as bugged as ever now on live.

It was never read, the devs probably still don't know or care.

I'd guess both crit parts of the sorc capstone aren't functioning. I got it on my sorc and not really noticing a difference. I think the +10% dmg seems to work tho.

I imagine none of this was tested at all.

Probably the same reason the new sorc savant item sets don't work (so i've read, don't have one yet). Turbine has no such thing as QA.

Well ... if you go and read the "Elder game" blog (google is a great search engine isn't it?) ... you can read a former Turbine Employee's take on their QA. Apparently the problem isn't that they don't have QA so much as that the people in charge of managing and guiding the QA people have no real plan, organization or specs for it.

So you end up with QA reporting thousands of tiny problems that don't impact the players at all (like a building hovering just above the ground), when there are thousands of bugs that really do need fixing but get drowned out in the bug system because of all the nonsense.

[Shandi]

has anyone done some testing today? i went out with polar ray and again I am only doing around 190 with my super glaciation 8 item + 40% from the enhancements. I took the capstone which should bump me up to around 200 damage but it's still not working or at least doesn't appear to be

I am testing monsters out in the vale which are not weak to ice or have resistance to it i.e. the dogs, lions and rats. I also am not using Empower or Maximize, trying to get a base

[rest]

Pretty disappointing that this is still broken. Maybe tomorrow's downtime will address this.

[winsom]

make sure you are not testing cold spells on cold-vulnerable targets, such as fire elementals. Cold-vulnerability introduces other damage-multiplying elements which may themselves be unclear , or difficulty to quantify with testing, or partially buggy with in combination with the testing thus leading to unclear results.

[Junts]

make sure you are not testing cold spells on cold-vulnerable targets, such as fire elementals. Cold-vulnerability introduces other damage-multiplying elements which may themselves be unclear , or difficulty to quantify with testing, or partially buggy with in combination with the testing thus leading to unclear results.

Actually I find that the fire elementals in TS with cold spells are the best place to test, as they take exactly 2x damage and so magnify the variations in crit multiplier so much as to make them readily obvious despite any variation in damage die rolls. While the difference between a low-roll, 3.0 crit and a high rolled 2.75 may only be 30-60 points normally, it will always be over 100 points doubled, so it makes it much easier to see whether things are or are not working. Polar ray has the handy advantage of doing almost exactly 1000 damage on average to these mobs, making picking up on the multiplier differences extremely easy.

[winsom]

I just saying that a bug could be introduced because you are testing a crit multiplier enhancement against a creature that is getting a cold vulnerable multipler. You could test it on other monsters as well to make sure those fire elementals are not a special case problem.

[Junts]

I just saying that a bug could be introduced because you are testing a crit multiplier enhancement against a creature that is getting a cold vulnerable multipler. You could test it on other monsters as well to make sure those fire elementals are not a special case problem.

I did, its not there on anything.