Bug report structure?

[imded]

It was pointed out to me what you don't want in a report.

So, I ask you. How do you want a report?

• Please give a outline for a report.
  
• also I suggest make it a separate post and sticky it for all to know.
  

Thanks

PS: for those that wish to know this too, plz post here.

[DOC]

1. The nature of the issue pertaining to what is wrong or broken (ie: bugged)

2. If necessary use bullet points in place of paragraphs since being concise and to the point helps us do more faster

3. Be sure to include details on how to replicate the issue and/or bug

4. Testing methodology and results of that testing if the issue is one of incorrect performance

5. All testing should be controlled testing and not simply attempts to prove your opinion is right. Proper testing isn't performed to support opinions a person may have already formed. Opinions should be formed as a result of what the controlled testing reveals, rather than a pre-held opinion about something telling you how to test that something. A lot of people get this part wrong and we need you to be right if you want to help us

6. Do not guess and do not repeat "what someone told me" or "that's what I heard" and expect it to act as a bug report

7. Leave side based claims or complaints out of bug reports, bug reporting doesn't care about sides or what seems fair on one side or the other

8. Bug reporting and the CRS responses to it or their forum thread management of these reports; are not openings for player arguments or rabid disagreement like say, people tend to make things over in the regular player forums. When we talk to you it's because we want you to know our view based on how things are here. We aren't trying to annoy you or anything, but here at CRS is not there in your room, if you know what I mean.

9. Bug reporting is not complaining. Yes there is room for complaint here as there would be anywhere that it is valid, it just doesn't belong in the bug reporting area. Try to keep this area strictly bug reporting and client testing and nothing else really.

There are valid places for those other things. Putting the wrong stuff in here just slows us down sorting it out. That means less game dev. and progress for you out there, and we'd like to maximize that rather than minimize it.

Thanks for all the help, past present and hopefully future! We really do value your feedback but in this response we're just trying to structure it a little. Don't get upset! Everything needs structure and good game development is no exception.

[imded]

Thanks DOC.

Just what I am looking for.

Oh! need to put this somewhere so that all can refer to it.

[GOPHUR]

Oh hell DOC that's too long. This isn't the beta forum!

A bad post:

- ramble on for more than a paragraph so you're sure I won't read it and it won't get tested and then it won't get fixed.

A good post:

- explain what you did

- could you repeat it?

A great post:

Here is my problem. When I do this that happens.

test:

• launch
  
• spawn
  
• do thing
  
• see thing
  

I think this is a video issue so here's my sys spec

CPU Core2Duo E4500

RAM 4GB

GPU Ati HD2400 Pro*

*whatever it is that is your problem

[imded]

Put the claws away guys.

Both posts are usefull.