![]() We usually can not fix issues that we can't see for ourselves and even when we can we can't verify if the fix works so sending a bug report that demands we just "trust you" on something doesn't make sense, whether we trust you or not doesn't matter. Include whatever you think might help us find the problem. If the bug refers to a file on your system (something like "savegame can't be parsed", "ini file can't be read") - include the file in your report. If the bug refers to mods, always include the name of the mod, the exact version and variant and a link. ![]() ![]() screenshots (if there is anything to see).What happens (in as much detail as you can)ĭepending on the situation these things are often useful.What are you doing (ideally with a step-by-step that triggers the issue).Does the error happen every time or was it only once.Just take a minute or two to provide as much information as you can, this improves the chance of getting the problem fixed a hundredfold. Don't send in a one line report "it don't work" and expect us to ask you personally for added information, that's a waste of time and it would require you have a github account. When you send in a report, provide all information that could be useful to us in the first report. ![]() You sent in a bug report that contains little to no information and is therefore not useful. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |