ATTENTION!!
Dear testers
You all are greatly help us and do a lot of things to our mod. But you can help even more if u will write your bug-reports by certain pattern.
Why is this so important? If we want to be short, thats so because good bug-report allows:
1. reconstruct the problem(its not always possible but we must press for it
).
2. understand, what is the nature of the problem and how important it is.
How to write a good bug-report?
At first, you must prepare yourself. If you discover a bug, dont run immidietly to the forum and type "its dont working!!!". Try to reconstruct error. Success? Good. If not, then you missed something. Try to remember, what exactly you did before it. Error happend again? Yay! Now try to minimize number of steps for reconstruction, and be shure, that there is nothing unnecessery there.
When you realized what data and wich actions caused the problem, briefly specify the essence - create a title of bug-report. Explain the problem as much detailed and concretized as the title says, but do not make it footlong
Example of a "bad" title: "Everything is freezing, when i attack the enemy"
Example of a "better" title: "Game is freezing when dwarven army attacks goblin settlement"
Try to avoid frazes like this: "i recruit a unit", "i press the button" etc. Title and steps description is manual for those, who will be fixing the problem, so it is better to say how to "recruit a unit" or "press the button".
Now start to fill the form of bug report:
Create the title:
After that: Detailed description, type here all info about the error - clarify here those details, that cannot be mentioned in title. If you understand, what the deal(used old calculation formula, some extentions missed, error in some specific script etc) - write it too. If you dont know - try not to wonder what it is
Steps for reconstruction - main field to fill in bug-report.
Write those steps, that you defined. As was said above, number of steps must be enough to reconstruct the problem. Not too long, not too short.
After this actions you must to type result.
If it is necessery type your expectations: what must happend in your opinion.
So, steps for reconstruction can look like this:
Steps for reconstruction :
1. recruit an army...
2. move an army from the citadel...
3. attack another army
4. press "retreat" button.
Result: general died in batle
Expected result: general must not die in battle.
If it is required: saves, logs, screenshots - attach them immidietly. Ofc, attachments must contain only necessery information, that can help to solve the problem.
Dont forget about "severity" - this therm tells how bug is critical in testers opinion. It is hard to say, how critical error is, but try not to tag every bug as critical.
PS please, after this post, all who want to participate in test, write your email and nothing else.