Do you a method for bug tracking during the Costume Creator/Alpha/Beta tests?
Since people will be reporting bugs, having a method to sort thru these could reduce the human time to sort the reports for duplicate errors.
If you don't have a method already in place, I suggest you give the public two methods to report any problems:
1) A free bug tracking software like Bugzilla.
2) For those who can't figure out the above software, a text based input form.
OR
When the user click a Bug Report menu entry, sub divide it into bug category sub-menus dealing with Costumes, Graphics, Mission Bugs, NPC errors, Annoying things, etc.
Then the Bug reports can have a bug category ID attached to make it easier to sort the bugs for the developers.
Mike
I would seriously hope that they (MWM) have a system in place long long Loooooooonnnggg before now to address this issue.
The most effective way to temper the user base (who do not have a sight line into the process or bug data base) is to promptly and regularly communicate expectations for the build. This informs people as to what is known ([I]to cut down on the noise >> eleventy bajilion duplicate bugs[/I]) and where to focus testing ([I]to steer people away from known deficiencies / missing code[/I]). I would seriously hope that they have a robust reporting mechanism (that could transition into the full Issue #1 release), as having to coordinate two or more reporting mechanisms (forums, external bug tracking, etc) can quickly get out of hand.
Since only KS Backers will initially have access, I can only assume that some of that information is being released, but I suggest that it be widely distributed so the entire user base can keep up to speed on what is going on. That way when/if they participate they can be productive.
"Just, well, update your kickstarter email addresses, okay? Make sure they're current?" - warcabbit
Thanks for the reply. It looks like you have previous experience with bug reporting.
As you said, there needs to be a way to cut down on the noise.