Roland said:
Normally I would agree and once the A20 dev diary starts obviously there will be zero tolerance for anyone posting A19 bug reports in the A20 thread. But this A19 thread is a somewhat lame duck thread and Blake and
@faatal seem to have a dialogue going that faatal hasn't seen fit to discourage. Obviously we can't have everyone start flooding this thread with bug reports but so far it hasn't really happened and if it does then we will have to enforce that rule. Personally, I have enjoyed reading faatal's solutions to the issues Blake has brought up so until it becomes a problem I am inclined to let it continue until the A19 thread closes or until faatal wants it to stop.
I hope everyone is noticing the pattern of post removal. What stays is predominately direct questions to the developers and direct comments and reactions to what the developers say. As soon as you start commenting on other people's comments then that is a discussion that is tangential to the direct interactions with the developers. So those are what I am shifting over to discussions.
I am not giving infractions for it because it is natural to comment and react to what others post. I am just informing everyone that those posts will get moved out so they do not clog and overwhelm the direct questions that people are hoping the developers will answer. I mean, I am sure people are on the edge of their seat to find out what YOU think about their question but they probably also want to hear from the developer they were asking and sometimes their questions get lost in all the debate and discussion that ensues.
Here's my take on this:
Performance feedback is not specifically related to the ideal "bug" report tickets because it needs constant back and forward and, what's more important, more times than not, it gets buried in hundreds of other posts and delays the most important issues (optimization on minimum and recomended systems).
Also, sometimes testers overlook a valid report due to the constant bombardment of non-canon tickets generating a bureoucratic hell, like in this particular example in which with just a look at the armor mods you could reproduce it in a19, yet he asked me for useless feedback probably from experiencing false statements daily, resulting in him just moving it to the "never gonna try" section (incomplete reports) forcing me to create a new one (can't edit old ones).
Another problem that the bug report section has for us general people, is that
WE CAN'T EDIT OUR OWN POSTS (at least, me, in the bug report section) . Only official testers can do that, apparently. That is crutial for fixing, improving the ticket and reporting correctly.
So what we need:
-To be able to edit our own posts on the bug report section.
-A proper forum entry for the bug report forums and not a green spam on the top of the screen. That's just awful.
-We also need testers that waste time testing seemingly incomplete reports that have at least repro steps. Testers that review ALL the reports if they have the minimum amount of feedback ( in my example, I had repro, some info and screenshots, MORE THAN ENOUGH for a report in many cases, and certainly a "good enough" in this case.
Minimum amount of feedback is just: General info and REPRO STEPS . They should test it and waste time for the good of finding the bug because that's what testers are meant to be; if they can't reproduce then ask for an output log OR they should move it to incomplete if no answer in, like 24 hours.
The unability to edit in the bug report section forces me to engage here in fast feedback with
@faatal , because in the case of some performance issues, an Output log wouldn't really be enough without the wall of text pointing out the problem in real time and with shorter notice. In the future (a20 and forward), I will create a whole thread to avoid clogging this "interesting thread of inconspicuous theme" with offtopic banter.
I do nevertheless use the bug report forum for reporting proper bugs/issues. Pointing out a problem with the AIDirector seldom counts as a bug if not properly tested, which I'm unable to do due to the fact that I don't know how to make wandering Zd hordes happen faster for testing purposes.