- Nov 5, 2013
- 923
- 1.135
Greetings soldiers!
In order to help us in QA, and rest of the Dev Team when writing a bug report, I'm providing you all with guidelines on how to write a "proper" bug report (might be useful to both veterans & newcomers on the forums).
This is to make a bug report more structured, and easy to read which in the end will help us to quicker reproduce the bug, and therefore hand in the correct information faster to the Dev Team so that they can fix it. I'll start with writing what a bug report should contain, and follow it up with an example to make things more clear.
What a bug report should contain:
1. Thread Title: Should always include the [platform], [version number] & [checksum] of the game and contain a brief description of the issue. In order to find the version number and checksum, start the game and you will be able to find it in the launcher. Can also be found in the in-game main menu.
2. Description: Describe the bug/issue in more detail - What occured and what you did in order to make the issue appear.
If you are using an old save after a new patch is released, please do let us know.
3. DLC Information: If you have any dlc's, unit packs etc, please state them here.
4. Mods: If you are using any mods, please state them here.
5. Reproduction Steps: If you are able to reproduce the bug, please write down steps needed to be done in order to achieve the desired result.
6. Please do not report multiple issues in the same post. Make a single post for each issue.
7. Attach if possible any screenshot of the issue, and/or a save of said game.
If you are having issues with CTD's (Crash to Desktop) try to always provide a save game, dump file, and logs. These files can be found in your Paradox folder, which is usually found in:
See the example below for how a bug report might look like:
Note that it is understandable that not all the bug reports are able to look like this, as there can arise occasions where it's hard to say what happened in order for the bug to occur. If that is the case simply try to provide with as much information as possible. I hope this will help you out as much as it will help us here in the office if used.
Best Regards,
Mr. Nibbles
Your QA Overlord & Drinker of Tears
In order to help us in QA, and rest of the Dev Team when writing a bug report, I'm providing you all with guidelines on how to write a "proper" bug report (might be useful to both veterans & newcomers on the forums).
This is to make a bug report more structured, and easy to read which in the end will help us to quicker reproduce the bug, and therefore hand in the correct information faster to the Dev Team so that they can fix it. I'll start with writing what a bug report should contain, and follow it up with an example to make things more clear.
What a bug report should contain:
1. Thread Title: Should always include the [platform], [version number] & [checksum] of the game and contain a brief description of the issue. In order to find the version number and checksum, start the game and you will be able to find it in the launcher. Can also be found in the in-game main menu.
2. Description: Describe the bug/issue in more detail - What occured and what you did in order to make the issue appear.
If you are using an old save after a new patch is released, please do let us know.
3. DLC Information: If you have any dlc's, unit packs etc, please state them here.
4. Mods: If you are using any mods, please state them here.
5. Reproduction Steps: If you are able to reproduce the bug, please write down steps needed to be done in order to achieve the desired result.
6. Please do not report multiple issues in the same post. Make a single post for each issue.
7. Attach if possible any screenshot of the issue, and/or a save of said game.
If you are having issues with CTD's (Crash to Desktop) try to always provide a save game, dump file, and logs. These files can be found in your Paradox folder, which is usually found in:
- C:\Users\XXXXX\Documents\Paradox Interactive\Hearts of Iron IV\save games
- C:\Users\XXXXX\Documents\Paradox Interactive\Hearts of Iron IV\logs
- C:\Users\XXXXX\Documents\Paradox Interactive\Hearts of Iron IV\dumps
See the example below for how a bug report might look like:
Note that it is understandable that not all the bug reports are able to look like this, as there can arise occasions where it's hard to say what happened in order for the bug to occur. If that is the case simply try to provide with as much information as possible. I hope this will help you out as much as it will help us here in the office if used.
Best Regards,
Mr. Nibbles
Your QA Overlord & Drinker of Tears
Last edited by a moderator:
- 5
Upvote
0
