#11 - Feb. 17, 2015, 9:34 p.m.
02/17/2015 01:23 PMPosted by
Kane It still raises the issue that Fierydemise pointed out at the end of the post - unless you go screaming on the forums, or raise a big "hey! hey! bug!" this stuff doesn't appear to be even looked at. The fact it got such a speedy response and incoming hotfix lends credence to it.
To speak to this, if it was indeed reported using the in-game feature, I'm not sure how it slipped through the cracks. I don't handle the in-game bug reports myself so I can't speak directly to how it could have happened, but it's definitely a fail on our part if we got reports on a bug like this and managed to miss them somehow.
We're extremely grateful to people like Fierydemise for pointing stuff like this out, but you're correct that it shouldn't be necessary. In the vast majority of cases, it isn't. In fact, I'm not 100% sure that the Ravenholdt post was what got this bug fixed (it seems likely, but I haven't asked the developer who's working on the fix where they heard about the bug because, well, it seems like actually working on the fix would be a better use of their time).
But we identify and fix a ton of bugs due to player reports -- this one just slipped through the cracks somehow. That sucks and is obviously our fault, but it's definitely the exception and not the rule.
