It’s pretty obvious, and nobody’s impressed.
Call to service
It’s pretty obvious, and nobody’s impressed.
I was thinking about doing this too, an up-to-date bug thread would be very helpful. I am willing to help you out with testing each of the listed bugs in that thread and starting a new one.
It’s a nice idea, but I think the original list was something of a placebo.
We all put a lot of effort into cataloguing the bugs we found, and indeed testing them, only for ANet to fix a pathetic handful and not in an order we found particularly good.
I don’t believe we’re discovering bugs ANet don’t know about. Either:
a) ANet really don’t know their own product or have acceptable QA testing
b) ANet knew all along and thought if they could get the community to “join in” they’d buy themselves some time before some players ragequit
Given the simplicity and obvious nature of the bugs, and the fact we’re dealing with professional developers, I’m going with b).
I was thinking about doing this too, an up-to-date bug thread would be very helpful. I am willing to help you out with testing each of the listed bugs in that thread and starting a new one.
This would be much appreciated!
It’s a nice idea, but I think the original list was something of a placebo.
I don’t believe we’re discovering bugs ANet don’t know about.
The purpose of the list isn’t just to notify the dev team of what is / isn’t working, it’s also to notify players of some unexpected effects or traits that are simply non-functional. Right now, that list is doing a huge disservice because of its inaccuracy. For example: this post by Aboriginal. As far as I can tell, Plague Signet works fine, but it still caused confusion due to its inclusion on that list.
It’s pretty obvious, and nobody’s impressed.
Or the bugged tooltip of Signet of Locust.
Problem is that people have this urge to create a new topic instead of reading a sticky post.
- Piken Square, [REN][DKAL]