Post by PaulV on Sept 19, 2015 11:01:13 GMT -5
To centralize the bug reporting, we will be using the github site:
github.com/Code60Home/fbs/issues
I know there is a fine line between a bug and a "Feature Request" but we need to keep bug reports to "things that don't woark, or don't work as expected, NOT things that "could be made easier". THose things should be posted to the "Game Play and Features" section.
When reporting a bug, please use the following format and post it in the "comments" section. Its common to be reminded of "something strange" in the midst of a discussion within a thread, but the odds of us becoming aware of a bug mentioned in passing in a discussion is low... discussing if something is a bug or not in a thread is a Good Thing, but once it is determined to e a bug, somebody needs to post it in the format below in the Bug Thread.
In the Subject line: always start with the bg sequence number in square brackets [123] followed by a short summery of the bug, then the severity in parens.
Subject Line: [XXXX] Summary of Bug (bug severity - see below)
When: Describe when the bug happens
Frequency:How often does it occur, or under what specific conditions or sequence of action
What: describe what happens
Comments: any amplifying remarks about the bug.
Recommendation: How you think it can be resolved or if there is a workaround.
Attachment: If a Crash To Desktop (CTD), include the most recent save game file (if a critical), or (if repeatable) a save just before the bug and one right after it. If there is need of a debug file John will let you know.
Disposition: This is where we will close out the bug report when it has been resolved.
The categories of bugs are below:
critical = game breaking - the game can't be played until its fixed - typically "crash to desktop" or "game freeze" events.
high = game not working as intended - a particular feature of the game is broken. It "works" as in the game doesn't crash, but is not providing the desired result or effect.
medium = game produces anomalous behavior - visual artifacts, units not performing expected actions, inappropriate combat results or events in the game log. Likely to cause significant player frustration.
low = annoyance - can be the same sort of issue as "medium" but there is a straightforward work-around to the issue. They can also be uncommon occurrences when the "game acts up" where you think something odd is going on, but its hard to identify exactly what the problem is and what causes it. These are often the most difficult to diagnose as they don't seem to have a distinct cause, don't occur regularly, and likely affect one particular platform exclusively.
Discussion of the bug and the debugging process will reply to this thread so we have that discussion attached as the body of the thread. If you can reproduce the bug, have any amplifying information on it reply to this thread to provide confirming, amplifying or other information you think might be helpful to resolving it.
Bugs sometimes rear their ugly head multiple times, so as we get further along, scan the bug report titles before you add a new bug that is actually a recurrence of a previous one.
github.com/Code60Home/fbs/issues
I know there is a fine line between a bug and a "Feature Request" but we need to keep bug reports to "things that don't woark, or don't work as expected, NOT things that "could be made easier". THose things should be posted to the "Game Play and Features" section.
When reporting a bug, please use the following format and post it in the "comments" section. Its common to be reminded of "something strange" in the midst of a discussion within a thread, but the odds of us becoming aware of a bug mentioned in passing in a discussion is low... discussing if something is a bug or not in a thread is a Good Thing, but once it is determined to e a bug, somebody needs to post it in the format below in the Bug Thread.
In the Subject line: always start with the bg sequence number in square brackets [123] followed by a short summery of the bug, then the severity in parens.
Subject Line: [XXXX] Summary of Bug (bug severity - see below)
When: Describe when the bug happens
Frequency:How often does it occur, or under what specific conditions or sequence of action
What: describe what happens
Comments: any amplifying remarks about the bug.
Recommendation: How you think it can be resolved or if there is a workaround.
Attachment: If a Crash To Desktop (CTD), include the most recent save game file (if a critical), or (if repeatable) a save just before the bug and one right after it. If there is need of a debug file John will let you know.
Disposition: This is where we will close out the bug report when it has been resolved.
The categories of bugs are below:
critical = game breaking - the game can't be played until its fixed - typically "crash to desktop" or "game freeze" events.
high = game not working as intended - a particular feature of the game is broken. It "works" as in the game doesn't crash, but is not providing the desired result or effect.
medium = game produces anomalous behavior - visual artifacts, units not performing expected actions, inappropriate combat results or events in the game log. Likely to cause significant player frustration.
low = annoyance - can be the same sort of issue as "medium" but there is a straightforward work-around to the issue. They can also be uncommon occurrences when the "game acts up" where you think something odd is going on, but its hard to identify exactly what the problem is and what causes it. These are often the most difficult to diagnose as they don't seem to have a distinct cause, don't occur regularly, and likely affect one particular platform exclusively.
Discussion of the bug and the debugging process will reply to this thread so we have that discussion attached as the body of the thread. If you can reproduce the bug, have any amplifying information on it reply to this thread to provide confirming, amplifying or other information you think might be helpful to resolving it.
Bugs sometimes rear their ugly head multiple times, so as we get further along, scan the bug report titles before you add a new bug that is actually a recurrence of a previous one.