Bugs: Difference between revisions
m recat |
→How to report bugs: bit nicer |
||
| Line 15: | Line 15: | ||
To report a bug, please give a description, what is going wrong and '''how it can be reproduced'''. what steps are required to reproduce it? If required to reproduce the bug add a script or/and a link to the Game/Map. | To report a bug, please give a description, what is going wrong and '''how it can be reproduced'''. what steps are required to reproduce it? If required to reproduce the bug add a script or/and a link to the Game/Map. | ||
==Logfiles, screenshots, replays== | |||
* Always attach [[infolog.txt]], as it contains system/driver/version info and if spring crashed. Click the link to see what it is and how to share it. | |||
Attach a replay: often Bugs can't be reproduced, its often better to see something than to only read about that. | * Attach a replay: often Bugs can't be reproduced, its often better to see something than to only read about that. | ||
Screenshots are taken with the F12 key and saved in the \screenshots\ folder. | * Screenshots are taken with the F12 key and saved in the \screenshots\ folder. You can attach them to postings or upload on site such as: [http://www.imgur.com imgur.com] , [http://www.abload.de abload.de] | ||
If a dev asks you for more information, please answer his questions. | * If a dev asks you for more information, please answer his questions. | ||
Try to avoid endless discussions why a bug was introduced, be polite! | * Try to avoid endless discussions why a bug was introduced, be polite! | ||
If you want more tips for a good bug-report, please read "[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively]" | * If you want more tips for a good bug-report, please read "[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively]" | ||
'''The better the bug-report, the better the chances, that it will be fixed!''' | |||
[[Category:Engine Dev]] | [[Category:Engine Dev]] | ||
Revision as of 13:52, 24 August 2013
See if the bug and a solution are already known
You can do so in the FAQ
You can also have a look at recent and stickied threads in the Help & Bugs Forum
Where to report bugs
In general, the forum is a bad place to report a bug. Often ofter people will add comments, which confuse others and don't help to understand, whats the real problem. So, if you found a bug in the Spring Engine, please report it to the bug tracker.
This is a open-source project, so devs don't get money, they do this in their free time. So don't waste time with disscussions in the forum, instead report it in the bug tracker and describe exactly whats wrong with Spring and how to reproduce the bug.
How to report bugs
Before filling a bug, please look if someone else already has reported this issue.
To report a bug, please give a description, what is going wrong and how it can be reproduced. what steps are required to reproduce it? If required to reproduce the bug add a script or/and a link to the Game/Map.
Logfiles, screenshots, replays
- Always attach infolog.txt, as it contains system/driver/version info and if spring crashed. Click the link to see what it is and how to share it.
- Attach a replay: often Bugs can't be reproduced, its often better to see something than to only read about that.
- Screenshots are taken with the F12 key and saved in the \screenshots\ folder. You can attach them to postings or upload on site such as: imgur.com , abload.de
- If a dev asks you for more information, please answer his questions.
- Try to avoid endless discussions why a bug was introduced, be polite!
- If you want more tips for a good bug-report, please read "How to Report Bugs Effectively"
The better the bug-report, the better the chances, that it will be fixed!
