** Bug Posting Guidelines **

[Mr. Tee]

===============================================

1. The title shouldn't just say "Bug" or "Crash", it should take the form of:
[ZDoom_Version] Effect : Possible_Cause

Here are some examples:
[2.1.3] Bug : Backpack messes up items
[2.1.1] Crash : Decorate actors using A_Custom Missle
[2.1.0] Total Lockup : Dividing by zero in ACS scripts

===============================================

2. Do not copy&paste the crash log's contents in your post. Please attach the unaltered 'CrashReport.zip' that is saved.

===============================================

3. If your bug requires some kind of further explanation, please put this before the crash log.

===============================================

4. Only post bugs for ZDoom, i.e. not Skulltag, ZDoomGL, GZDoom or anything else.
(submitted by Randy and Graf)

===============================================

5. If you need to report something not working properly, use the Bugs forum. Do not send private messages to the developers! There is a high probability that such reports just get ignored without being investigated.

===============================================

6. Don't post bug reports for any version older than 2.4.0 (such as 2.3.1, 2.0.99x, 1.22) These versions are old and won't be updated anymore. If you encounter a problem with these versions please verify first with a more recent version that the problem still exists. If the bug happens with the latest official version, check with a recent unofficial SVN build if it happens as well. No need to report a bug that's already been reported and fixed.


==============================================

7. If you experience a crash with a custom WAD please post a link to a download location for that WAD if possible.

===============================================

8. If you post a bug for a self-compiled SVN version, please try to gather some information in the debugger yourself. Since you are able to compile it you should have access to one. Crash logs for such builds are of no use.

===============================================

9: If you need to attach something to check the bug (such as a test mod, demo, save, etc.), then DO NOT use a non-permanent host like Rapidshare, MediaFire, or similar. If the file is small enough, zip it and attach it. Otherwise, host it on your own webspace or on the DRD Team files service. Often bugs can't be examined right away. However, if by the time the bug is being examined the attachment is gone there is no way to address the issue and the report will be closed without any action taken as a result.

[Graf Zahl]

These are some really useful guidelines which should be stuck in a sticky thread at the top of the bugs forum. I think this is a response to the latest useless bug report from today, right?

[Vaecrius]

Sounds good to me, although I'd put the version number first to make it easier to sort out old vs new bugs in a search...

[Csonicgo]

These are some really useful guidelines which should be stuck in a sticky thread at the top of the bugs forum. I think this is a response to the latest useless bug report from today, right?

I was in a hurry, and it was on my mum's computer, so I couldn't stay on long after the crash.

[QBasicer]

Why limit it just to ZDoom information? What about system? Windows Version? Processor? Ram? Sound card? Video?

It all effects the way ZDoom runs.

[Graf Zahl]

It depends on the bug whether this is necessary. For obvious gameplay bugs this really isn't necessary. For crashes it should be included, though.

[Lexus Alyus]

If you just use the basic title suggestion that Mr Tee suggested and then, if it's relevent, stick the OS, computer specs, etc... in the actual post. This would keep the title reletively short, yet still important, and any additional information is contained within the post.

Good work Mr Tee .

[Xaser]

Go Mr. Tee! I hope this helps out alot!

Heh. I never knew a Cajun Bot could be so helpful (no offense).

[Bouncy]

This is EXACTLY what the Bugs forum needed. I waited for something like this...

[Giest118]

Perhaps another guideline should be posted saying that you should probably attempt to reproduce that crash/bug before posting it... 'cause if you can't reproduce it, then it's probably just a one-time thing that you'll never see again.

[Graf Zahl]

No. Even one time crashes may point Randy to a potential problem.

I once had a strange crash in one of my programs which I was unable to reproduce but investigation got me to a very serious error that only rarely resulted in a crash but could also silently destroy data.

[Csonicgo]

I get crashes every day like that.... maybe I SHOULD POST THEM.

[Mr. Tee]

Teh new guidelines... Simpler, and closer to the style most people like to bugs in.

Happy Holidays,
Merry ZDooming!

[Janizdreg]

I second that the title form recommended in the first guideline should be [ZDoom_Version] Effect : Possible_Cause. Most people seem to use it already anyway.

[doom2day]

Perhaps another guideline should be posted saying that you should probably attempt to reproduce that crash/bug before posting it... 'cause if you can't reproduce it, then it's probably just a one-time thing that you'll never see again.

If someone knows how to reproduce a bug then that would be useful