Beta Organization

Format, collection, etc.

With the beginning of the beta fast approaching, I think getting a basic framework setup for the community to discuss bugs and issues would be useful, as would the ability to keep it all in one place. For instance:

-----

ID: FunkyKong
Version: Demigod 0.01 (Beta)
Bug Status: Reported
Bug Type: Animation Bug
Description: The animation for the Queen of Thorns Demigod performs incorrectly when a specific attack is made against the Rook.
Reproducible: Yes

-----

In this way, the information can be portrayed effectively for everyone who is looking for it; devs will be able to make use of the simple similar layout to quickly ascertain bug types and importance, and us testers can quickly tell if the bug matches our own or if it can be reproduced. If we wanted to go a step further, we could organize a few threads for basic types of bug reports, all in one place; for instance.

[BUG THREAD] : UI Bugs
[BUG THREAD] : Skill Set Bugs
[BUG THREAD] : Freezes / Crashes
[BUG THREAD] : Specific Unit Bugs
[BUG THREAD] : Map Bugs

And so on. It's a bit more organized than a large master list of bugs stickied in a single thread, but also a bit more work to maintain effectively in multiple threads.

Thoughts?

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

would be nice if they just had a submit form for crashes that comes up automatically.

Successfully updated karma reason!

well the only flaw i see is that there will be a ton of identical reports because the thread will be overflooded quickly.

a standard report form is a good idea

i would requst bug subforums instead of threads for better overview and perhaps a info thread with all fixed bugs in it so you dont report already fixed bugs. usaly in a beta the beta server is not completly up to date so some bugs might be fixed already but the beta testers would still report the bug.

i would also request everyone that has a already reported bug but have new info on it posts it in a already exisiting thread that would give the team a better overview of the problem and saves them for hunting down clues in 200 diffrent threads.

Successfully updated karma reason!

I agree with Zyprezz, a category for each character so that way the devs don't have to sift through all the reports to find another on rook. Also it will be easier to see if the bug report was already listed for your character on that issue. I'm sure it won't be preferred if there are 30 reports of rook unable to hit ____ character. So the easier it is to see if the bug was reported, the less redundancy there will be.

Also date is very important of when the occurrence happens. Imagine, someone posts a bug and it gets "fixed" and then someone posts about the bug shortly after and the devs figure it was just someone who posted a copy and ignore it so the issue goes unfixed until someone else posts about it. Which might not happen because someone else posted about it. Then the world explodes... you get my point.

Thank you,
cos(Ө)

Successfully updated karma reason!

Quoting CosineofTheta,

reply 3

I agree with Zyprezz, a category for each character so that way the devs don't have to sift through all the reports to find another on rook. Also it will be easier to see if the bug report was already listed for your character on that issue. I'm sure it won't be preferred if there are 30 reports of rook unable to hit ____ character. So the easier it is to see if the bug was reported, the less redundancy there will be.Also date is very important of when the occurrence happens. Imagine, someone posts a bug and it gets "fixed" and then someone posts about the bug shortly after and the devs figure it was just someone who posted a copy and ignore it so the issue goes unfixed until someone else posts about it. Which might not happen because someone else posted about it. Then the world explodes... you get my point.Thank you, cos(Ө)

Date is basically covered in the version #. In fact, version # is much better than date since you know that the bug is on the current build and not just a bug someone sat on for a couple of days before posting.

Successfully updated karma reason!

Subforums would probably be preferable to threads given the plausible number of bugs. A bug report form incorporated into Stardock or Demigod would also be preferable, though the idea behind standardizing thread setups would be to also help[ users from posting the same bug multiple times by making it easier to find a bug that has already been posted.

Successfully updated karma reason!

Whats about Bugzilla?

Some developers are using this software in order to deal with bugs.

Successfully updated karma reason!