[Closed] Good Bug Report Practices
Good Bug Report Practices
When reporting bugs, there are a few good practices to follow so that you can provide the development team the most information possible. This will therefore make it easier for the developers to fix issues.
Include the specific mode
Some minigames have a variety of different modes.
Including this in your bug report is highly beneficial. There may be an issue in one mode that doesn’t appear in another and including the mode will allow the developers to know exactly where the issue happened so they can replicate it.
Get ‘proof’ of the bug
One of the most challenging parts of fixing bugs is trying to replicate or reproduce the issue. If the bug report includes proof of some kind of the issue, it is extremely helpful and makes it a lot easier for us to recreate the bug.
We understand that not everyone can record or knows how to screenshot, which is why it is not required when making a bug report. However, we highly recommend you do include some sort of ‘proof’ when you make a bug report.
For those who do not know how to screenshot, pressing F2 on your keyboard (or Fn+F2 on Mac) will take a screenshot. You can then navigate to your “.minecraft” folder to find the screenshot file.
For larger issues it’s better for us to have a video, that way we can see exactly what you’re doing and how you’re doing it.
However, for smaller issues screenshots are also helpful. For example, if you find a missing block in a map, simply screenshotting it while having F3 mode turned on (so we can see the coordinates) will give us all the information needed.
When reporting bugs, we welcome you to provide us with as much information as possible. The more information you give us, the easier it is to fix it. Most of the tips above are the same idea, more information! However, you are free to add anything else you feel may be important.