devtrackers.gg
over 3 years
ago -
TinyWiking
-
Direct link
Greetings!
In order to help us in QA 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. { "lightbox_close": "Close", "lightbox_next": "Next", "lightbox_previous": "Previous", "lightbox_error": "The requested content cannot be loaded. Please try again later.", "lightbox_start_slideshow": "Start slideshow", "lightbox_stop_slideshow": "Stop slideshow", "lightbox_full_screen": "Full screen", "lightbox_thumbnails": "Thumbnails", "lightbox_download": "Download", "lightbox_share": "Share", "lightbox_zoom": "Zoom", "lightbox_new_window": "New window", "lightbox_toggle_sidebar": "Toggle sidebar" }
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!
What a bug report should contain:
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.
We would also like to thank @Imse Vimse for the original template and overall guidance.
In order to help us in QA 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. { "lightbox_close": "Close", "lightbox_next": "Next", "lightbox_previous": "Previous", "lightbox_error": "The requested content cannot be loaded. Please try again later.", "lightbox_start_slideshow": "Start slideshow", "lightbox_stop_slideshow": "Stop slideshow", "lightbox_full_screen": "Full screen", "lightbox_thumbnails": "Thumbnails", "lightbox_download": "Download", "lightbox_share": "Share", "lightbox_zoom": "Zoom", "lightbox_new_window": "New window", "lightbox_toggle_sidebar": "Toggle sidebar" }
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!
What a bug report should contain:
- Summary: Short and concise, but descriptive enough to be able to decipher what is meant at a glance. Examples:
CK3 - Interface - Religious icon is missing
CK3 - AI - Allied AI does not come to my aid in war
CK3 - Audio - There is no sound effect when I click a holding
CK3 - Gameplay - Cannot scheme murder on my sister-wife
- 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!
- Operating System: Very important step! Let us know if you game from Windows, Mac or Linux!
- Platform: Which platform of choice do you use to play your game from?
- Mods: Incredibly important! Let us know if you use mods when playing the game or not!
- Pain threshold: Tell us how badly found bugs hurt you! We’ll make them pay for what they have caused!
- 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.
- Reproduction: Be polite. Be efficient. Note down everything that led you to this point.
- 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. If you are using an old save after a new patch is released, please let us know.
(Saves are really useful for us, please attach saves as often as you can.
- Also, please attach an uncropped screenshot of the issue.
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.
We would also like to thank @Imse Vimse for the original template and overall guidance.