Has Conjure Bolts been changed?

[Livmo]

IIRC, there's a page on the wiki somewhere with all the tips on the splashscreens.

And, indeed, IRC! Loading Screen Tips

Edit: You're looking for #157:

Yay!

The +4 Enhancement bonus on the Doublecrossbow is greater than the +1 Enhacement bonus on the bolt.

[Kompera_Oberon]

Yes and no. A bit of history on this one:

For a long time the Conjure Bolts scroll simply failed to conjure bolts. The reason it was broken was that the scroll was unable to scale the enhancement bonus of the bolts based on the caster's level. We fixed this bug by having the Conjure Bolts scroll only conjure +1 bolts. The current bug is that if you learn Conjure Bolts on your Artificer from the scroll, you're getting the scroll version of Conjure Bolts instead of the Artificer spell version.

Unfortunately, though, while this is a bug, it - probably - doesn't rise to a level that beats out other bugs we need to fix. "Most" artificers learn Conjure Bolts during leveling, and "most" players tend to get their enhancement bonus from the weapon rather than the ammunition. So, for "most" people, this really isn't much of an issue. This is an issue, though, for people who learn Conjure Bolts on their Artificer through the scroll and depend on the ammunition's enhancement bonus rather than the (typically higher) enhancement bonus on the weapon. The "solution" is to either pick the spell during level up, or get your bonus from the crossbow itself.

Lovely. And where, other than in some obscure forum post which 90+% of your customer base will never see, is this information communicated to the players?
Please don't point to some third party wiki, Turbine is responsible for good communications with their customers.

When will the flawed Turbine concept of a "known issues" list be corrected, so that Turbine might actually communicate all of the game issues to their costumers? I mean, right now the status quo is to only list things which Turbine needs more detail about in order to fix. Which begs the question: If something isn't listed, meaning that Turbine does not need any more information from their customers in order to fully understand the problem, why does the problem still exist?

Is it so that Turbine can point their corporate bosses to the list and say "Look how small it is! What a great job we are doing!"? I would hope not, since the actual issues list is at least an order of magnitude, if not two, greater than what is listed.

I'd really appreciate hearing from a Turbine rep on this subject. Please educate me so that I might understand the methods behind your madness.

[Cordovan]

Lovely. And where, other than in some obscure forum post which 90+% of your customer base will never see, is this information communicated to the players?
Please don't point to some third party wiki, Turbine is responsible for good communications with their customers.

When will the flawed Turbine concept of a "known issues" list be corrected, so that Turbine might actually communicate all of the game issues to their costumers? I mean, right now the status quo is to only list things which Turbine needs more detail about in order to fix. Which begs the question: If something isn't listed, meaning that Turbine does not need any more information from their customers in order to fully understand the problem, why does the problem still exist?

Is it so that Turbine can point their corporate bosses to the list and say "Look how small it is! What a great job we are doing!"? I would hope not, since the actual issues list is at least an order of magnitude, if not two, greater than what is listed.

I'd really appreciate hearing from a Turbine rep on this subject. Please educate me so that I might understand the methods behind your madness.

The fix to the Conjure Bolts scroll was in the release notes, although the notes did not specifically state the outcome of the fix. IIRC, I was not aware of the nature of the fix until after it went live, so didn't clarify in the notes.

You are correct that the Known Issues list has never been properly named, and is largely outdated. Our "corporate bosses" do not use the Known Issues list to track bug count; we have internal tools for that. We've stated numerous times over the years that the Known Issues list is not meant to be, and was never intended to be, a complete list of bugs in DDO. It dates back to the days when we would get numerous bug reports on issues that we already had check ins for in the next game update, as a way to help filter our bug reporting list. It also gives Customer Service a place to guide people to who contact them with known bug reports.

That said, I completely agree that the Known Issues list is not very useful in 2016. I'm considering getting rid of it, and moving over to a "notice board" style post where we can put specific update information. No decision has been made. If you feel strongly about it, feel free to comment elsewhere or PM me. Note that we will never have a public list of all bugs in DDO, and maintaining a more accurate list is probably not realistic.

[Steve_Howe]

That said, I completely agree that the Known Issues list is not very useful in 2016. I'm considering getting rid of it, and moving over to a "notice board" style post where we can put specific update information. No decision has been made. If you feel strongly about it, feel free to comment elsewhere or PM me. Note that we will never have a public list of all bugs in DDO, and maintaining a more accurate list is probably not realistic.

That would be a welcome change, IMHO.

[DagazUlf]

I'm considering getting rid of it, and moving over to a "notice board" style post where we can put specific update information. No decision has been made. If you feel strongly about it, feel free to comment elsewhere or PM me.

Seems like a great idea.

[cdbd3rd]

...

That said, I completely agree that the Known Issues list is not very useful in 2016. I'm considering getting rid of it, and moving over to a "notice board" style post where we can put specific update information. No decision has been made. If you feel strongly about it, feel free to comment elsewhere or PM me. Note that we will never have a public list of all bugs in DDO, and maintaining a more accurate list is probably not realistic.

Anything that facilitates keeping what issues *are* listed as current as possible would be a win.

[Tlorrd]

Cordovan;5781901] Note that we will never have a public list of all bugs in DDO, and maintaining a more accurate list is probably not realistic.

Why?? At least with regards to bugs that affect races, enhancements, spells, abilities, EDs, items, quests, etc. I can understand internal bugs of computation or systems, but at least in game stuff that players interact with should be able to see a list of bugs.
1. It's transparent
2. Allowed players to better understand where focus is being spent. Oh course you'll get criticism for the order of which bugs get fixed and which don't, but who cares, you all do what do.
3. It can help players avoid certain builds that are busted based on current bugs.

[Amundir]

I personally would be interested in seeing an "Open Issues" or "Known Issues" forum section, provided that the security was setup so only a turbine employee could open one, while possibly players could reply. I only say that so hopefully there would be some sanity to being able to search to see if an issue is already listed.

[Shoemaker]

The fix to the Conjure Bolts scroll was in the release notes, although the notes did not specifically state the outcome of the fix. IIRC, I was not aware of the nature of the fix until after it went live, so didn't clarify in the notes.

I dug through the wiki looking for something concrete on this... I found [[Update 23 Release Notes]] which indicates that it was in the Update 23 release notes in the "Items" section that: "Scrolls of Conjure Bolts now actually conjures bolts."

You are correct that the Known Issues list has never been properly named, and is largely outdated. Our "corporate bosses" do not use the Known Issues list to track bug count; we have internal tools for that. We've stated numerous times over the years that the Known Issues list is not meant to be, and was never intended to be, a complete list of bugs in DDO. It dates back to the days when we would get numerous bug reports on issues that we already had check ins for in the next game update, as a way to help filter our bug reporting list. It also gives Customer Service a place to guide people to who contact them with known bug reports.

Those that have an interest in bugs should be advised that they have the option of helping to maintain [[Official Known Issues]], [[:Category:Game bugs]], and [[:Category:Minor game bugs]] which is likely more up-to-date than an "Official" list could possible be. I'd also make sure that CS is aware of those pages that they are welcome to guide people to who contact them with known bug reports.

That said, I completely agree that the Known Issues list is not very useful in 2016. I'm considering getting rid of it, and moving over to a "notice board" style post where we can put specific update information. No decision has been made. If you feel strongly about it, feel free to comment elsewhere or PM me. Note that we will never have a public list of all bugs in DDO, and maintaining a more accurate list is probably not realistic.

If it was a vote, and I had a say in said vote, I'd be on the side of "dump the official list" and let those interested in having a community list of those things give specific bug details (without disclosing steps to reproduce, which would be oversighted and sent to https://ddobugs.turbine.com on sight by me anyway) on the respective wiki pages for the things that are bugged.

[Shoemaker]

I personally would be interested in seeing an "Open Issues" or "Known Issues" forum section, provided that the security was setup so only a turbine employee could open one, while possibly players could reply. I only say that so hopefully there would be some sanity to being able to search to see if an issue is already listed.

I've personally advocated some kind of Bugzilla, Phabricator, Jira, etc bug tracking system to help people who are really interested in improving bug reports do so. Unfortunately, based on the developer feedback I got when I mentioned it at Turbine HQ on one of my visits, it's just not something that I ever see as being a reality. With that said, all community members and players of DDO are welcomed to mention bugs on http://ddowiki.com on the page of the quest/item/thing/etc that the bug effects or its respective talk page. As long as you're not detailing how-to-exploit, it would be much appreciated. Anything that I see that is a detailed how-to-exploit, I will remove on sight and warn/block the poster as is appropriate.

[Seikojin]

I've personally advocated some kind of Bugzilla, Phabricator, Jira, etc bug tracking system to help people who are really interested in improving bug reports do so. Unfortunately, based on the developer feedback I got when I mentioned it at Turbine HQ on one of my visits, it's just not something that I ever see as being a reality. With that said, all community members and players of DDO are welcomed to mention bugs on http://ddowiki.com on the page of the quest/item/thing/etc that the bug effects or its respective talk page. As long as you're not detailing how-to-exploit, it would be much appreciated. Anything that I see that is a detailed how-to-exploit, I will remove on sight and warn/block the poster as is appropriate.

This. Maybe Cordovan can give it some updates as well

[Kompera_Oberon]

Note that we will never have a public list of all bugs in DDO, and maintaining a more accurate list is probably not realistic.

Why?? At least with regards to bugs that affect races, enhancements, spells, abilities, EDs, items, quests, etc. I can understand internal bugs of computation or systems, but at least in game stuff that players interact with should be able to see a list of bugs.
1. It's transparent
2. Allowed players to better understand where focus is being spent. Oh course you'll get criticism for the order of which bugs get fixed and which don't, but who cares, you all do what do.
3. It can help players avoid certain builds that are busted based on current bugs.

The answer to why is easy: It would be embarrassing.

[Zachski]

The answer to why is easy: It would be embarrassing.

I'm pretty sure if anyone had all of their mistakes paraded in front of them, you and me included, we'd be embarrassed.