.png){kind=avatar}
Greetings Generals!
In order to help our QA 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:
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 as much information as possible.
Please do not report multiple issues in the same post. Make a single post for each issue. If you see that someone has reported what you have come across, add your information as a reply to their thread. I hope this will help you out as much as it will help us here in the office!
Kind regards,
Katten
Your Community Manager
In order to help our QA 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:
- Summary: Short and concise, but descriptive enough to be able to decipher what is meant at a glance.
- Platform: Which platform of choice do you use to play your game from?
- Operating system: Very important step! Let us know if you game from Windows, Mac or Linux!
- Game version & Checksum: In order to find the version number, start the game and you will be able to find it in the launcher. It can also be found in the in-game main menu. Easiest way is to click the version number in the main menu of the game!
- Enabled DLC: Which DLCs have you enabled?
- Do you have mods enabled?: Incredibly important! Let us know if you used mods when you experienced the issue.
- Description: Write a longer description if the issue is complex and/or you think it might be useful for us to know what you did before it appeared. Other useful information is custom game setup, what nation you are playing and any other relevant information.
- Steps to Reproduce: If you are able to reproduce the bug, please write down steps needed to be done in order to achieve the desired result.
- Are you playing on the save from the previous/older version of the game?: Yes/No.
- Upload Attachment:
10.1: Attach a save taken just before the issue happened: If you don’t have a save from before the issue occurred, attach one where the issue is already present. (Saves are really useful for us, please attach them as often as you can.)
10.2: Uncropped screenshot of the issue: If it is a static bug, take a screenshot of the entire 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
.hoi4, .pdf, .png, .jpg, .jpeg, .jpe, .gif, .7z, .crp, .rar, .sav, .dmpSee the example below for how a bug report might look like:
####Example Bug Report - Do not take the example as serious for obvious reasons####
Summary
AI - US joins Allies too early in Historical setting
Platform
Steam
Operating system
Windows 10
Game version & checksum
v.1.0.0.19830 [a467]
Enabled DLC
MtG, LaR, NSB, BBA
Do you have mods enabled?
Yes
Description
The US is supposed to join the war, and allies in 1941, due to Pearl Harbor. But they joined in 1940 due to the Netherlands/Belgium.
Reproduction Steps
1. Start attached save game.
2. Activate human_ai
3. Wait for a day.
4. Notice that the US joins Allies and subsequently the war.
Are you playing on the save from the previous/older version of the game?
Yes.
Upload Attachment
X
Summary
AI - US joins Allies too early in Historical setting
Platform
Steam
Operating system
Windows 10
Game version & checksum
v.1.0.0.19830 [a467]
Enabled DLC
MtG, LaR, NSB, BBA
Do you have mods enabled?
Yes
Description
The US is supposed to join the war, and allies in 1941, due to Pearl Harbor. But they joined in 1940 due to the Netherlands/Belgium.
Reproduction Steps
1. Start attached save game.
2. Activate human_ai
3. Wait for a day.
4. Notice that the US joins Allies and subsequently the war.
Are you playing on the save from the previous/older version of the game?
Yes.
Upload Attachment
X
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 as much information as possible.
Please do not report multiple issues in the same post. Make a single post for each issue. If you see that someone has reported what you have come across, add your information as a reply to their thread. I hope this will help you out as much as it will help us here in the office!
Kind regards,
Katten
Your Community Manager
- 19
- 5
- 2
- 1
Upvote
0