Bug reports help make the game better for everyone, but the quality of the bug report will dictate whether or not we can do anything to correct any potential issue.
Information is key. Remember this; The key to fixing any software issue lies in being able to reproduce the issue on our development systems. Without proper information it is a waste of time to try and duplicate the problem.
Example:
Hey, the game crashed, fix it!Okay, this will simply be ignored as there is nothing there to help point us in the direction of the potential problem.
versusI was on [terrain name], in [specific arena] performing [specific action] when the game crashed to the desktop. I have attached the dmp file, and [optionally] the .psave file "cmepos.txt".I'll break it down. We almost always need the terrain name, as the problem could be terrain related.
We need the arena name, as different arenas have different configurations.
The dmp file is very important. If there is one, it will be the best tool available to us for debugging a problem. See the
post for details about it in this thread.
The .psave information file "cmepos.txt" gives us your exact location on the terrain. Also important.
Optionally, we may need the
DXDIAG output from your computer.
It never hurts to provide it. When used in conjunction with the dump file, it may point to a potential conflict with some piece of hardware we need to resolve.