The first time I see this thread...
Oh, I remember several discussions, trying to convince some (unnamed) GMs or DEVs that my bug report is not a duplicate, or even a valid bug report at all...
Well, I don't work on the PS code. I don't know the mechanics behind the courtain of CS. But nevertheless, I am a software developer, in general. So in my opinion, there is some level of knowledge I can base my theories on, why a bug may occur, and how it may get fixed.
A reply like "Works for me, closed" is quite annoying. At least because a "negative proof" has some prerequisites which have to match the case. You know - one counter example destroys only an "always", but not a "sometimes".
But over this year, I really must thank the developers and game masters. They really try to understand and discover the bug reports, and fix them - or prove them failing - before closing.
Keep up your good work. Especially Arianna, the "manager" of all bug reports!
