Welcome to the Victoria 3 Bug Reporting Forum!

[PDX_Maciej]

In order to help our trusteed QA team, we wanted to provide you with some guidelines on how to write a bug report. If your reports follow the same structure it will help us quickly identify (and hopefully reproduce) the issues, which in turn will make us more efficient.

We will start with writing what a bug report should contain, and then give you an example to make things more clear.​

Our motto is “Less is More” - the shorter and more concise the description, the easier it is for us to log it in our system and, ultimately, fix whatever is bugging you! At the same time, the better quality screenshots and saves you provide, the better we’ll be able to narrow down the issue and get it logged in our system.

Alright, now let’s get down to the specifics:

1. Game Integrity and Steam Files
   Verifying files on Steam helps QA and You to make sure that the game has all the files that it needs, and replaces any that are missing. You can easily do that by:
   - Either right click the game in your Library, or click the gear icon from the game's Library page on the far right
   - From the drop down menu, select. Properties...
   - Select the. Installed Files. ...
   - Steam will verify the game's files - this process may take several minutes.
2. Disabling Mods
   Mods become an increasingly important factor in our games, as they add depth to the original work, and can be fun for players we do, however, ask to disable them if you found significant issue. It is asked due to help developers to make sure that the issue is not caused by the mods but rather by inconsistency in authentic design.
3. Summary
   Short and concise, but descriptive enough to be able to decipher what is meant at a glance. Examples:
   Interface -Text overlaps in Technology Tree
   AI - Allied AI does not come to my aid in war
   Audio - There is no sound effect when an event pops up
   Gameplay - Revolutions never end
4. 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.
5. Step To Reproduce
   STR as we call it in our QA department means everything. The more accurate one can be with backtracking the steps in the playthrough the better. It will increase the chance to reproduce the issue internally by developer and fix it.
6. Game Version
   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!
7. Operating System
   Very important step! Let us know if you game from Windows, Mac or Linux!
8. Bug Type
   It is simply better if you narrow it down by ticking the area which is affected by the issue. If you are not sure, just tick 'Other'.
9. Attach a save taken just before the issue happened
10. 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.)
11. Attach an uncropped files
    If you have any other additional material to help identify the issue please attach it. It may be a recorder video of the issue happening, just a screenshot, or other material.
12. Level of Pain
    The audacity of this bug to cause you pain! Tell us how annoying you’re finding it, on a scale of 0-10.
13. Lastly…

If you run into the same bug that someone else has reported, please use the upvote option that is accessible in the thread and add any additional, relevant information that you possess.
This will ensure that we are notified on the most common, most pressing issues that you might be experiencing!

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 the thread.