In-game Bug Report Guide This thread will go over each step of the bug report form so you can efficiently and of course correctly report any bugs/issues found. Following this guide will make it easier for our QA team to recreate each bug so it can be forwarded and then fixed as soon as possible. Choosing a Platform In this section, there will be a drop-down menu where you can choose which platform the bug occurs on. Java/PC: This is the Minecraft version on Windows, macOS, and Linux MCO/Bedrock: This is the mobile/Windows 10 version of Minecraft that be played on a numerous amount of device + consoles Be sure you select the correct platform when reporting a bug. It is VERY important when it comes to correctly recreate the bug/issue reported. Java and Bedrock are completely different when it comes to its makeup so an issue on java most likely will not be an issue on Bedrock as well. However, with bedrock and java having similar games it can be difficult with vague information what server the issue is on. What Type of Bug? This section is also a drop-down menu with a few options giving a little more information about what kind of issue/bug you will be reporting. Game Bug: This is a general bug that has to do with the server/games itself. Whether a kit deals doesn't work as described all the way to achievements not working or even holograms staying after you open a chest in the lobby. This is the option a majority of reports will be. Be careful you don't get Game Bugs confused with Map Exploits. Map Exploit: This is an issue with the map NOT the game. Map exploits can range from the border being too high or a spawn point being incorrect all the way to being able to get out of the map. If you are filing a map issue/ map exploit please do not forget to include the map name. Clans Related: Any issue/bugs that happen in clans fall into this category. It will be viewed by Clans Management and they will respond accordingly. Chat Filter: This is pretty self-explanatory this regards any issues with the filter. This can be a set of words that get censored that shouldn't be or even a bypass that you think should be filtered. Versions If you are reporting a bug for Java/PC be sure to include the proper game version you are using. (E.g. 1.8.9, 1.9.0, etc.) As for MCO/Bedrock, it's the same. you must include the proper game version/update. You will also need to include what device you are using. (E.g. 1.8.0, etc. Windows 10, Xbox, Nintendo Switch, etc.) Where Does the Bug Occur Be extremely specific when it comes to this. Specify if it occurred in the Hub or Game lobbies as well as the exact game lobby. (E.g. HG-1) Including this information will allow us to tell if it is an issue with the overall game or just a single lobby. As much information regarding where it happened is best. *If you are filling out a map issue, please include the map the issue is located on as well as the coordinates to the location of the issue. As for bedrock don't forget to fill out which device was used when finding the bug/issue Steps To Reproduce This is one of the most important sections. You have to be extremely detailed and clear when explaining how the bug is done. Examples: WHAT TO DO: Description: Cosmetic doesn't work in game lobbies when the countdown starts. Step 1: Go to the game lobby Step 2: Open cosmetics menu Step 3: Choose cosmetic Step 4: Wait for the game to countdown Step 5: Try to use cosmetics WHAT NOT TO DO: Description: Cosmetics don't work in game lobbies. Mods By this, it is asking for any modifications you may have installed that you use along with Minecraft. This can include but is not limited to, Optifine, Laby mod, Laby mod 3, Podcrash, Forge, etc. When listing all modification you use be sure to add the version of the mod. (E.g. Optifine 1.13.2 HD U E5) Evidence With every bug report, the evidence is a necessary step. This is how we get proof of any bugs or issues and evidence assists when it comes to recreating. Evidence can be submitted in a form of a video or in some cases a screenshot. *Keep in mind, uploading screenshots with a link directly from your PC will NOT allow us to view the evidence. You will need to upload screenshots to a third party website and give us the link to it from there A few great websites for uploading screenshots include: -unapproved link- https://prnt.sc/ https://imgur.com/ As for video evidence, it is best if the video is recorded from a recording software such as Bandicam, Fraps, QuickTime Player, etc. for Java/PC. As for recording Bedrock, this can be a little tricky. Not all devices + consoles you can use for Bedrock have an easy way to record. If you're using an iOS device such as an iPhone or an iPad with the firmware of 11.0+ (If you're unsure of what firmware you have, you can check by going to Settings -> About -> Version) you'll have access to the screen recording feature located in the control center of your device. To enable this feature go to Settings -> Control Center -> Customize Controls -> Click the `+` button next to the Screen Recording option to include it in your control center. To access the screen recording button, simply access the control center and press the circle to start recording. To stop recording, access the control center again and click the red circle to end the recording. The video will then be saved to your camera roll in which you can upload the video to an app such as Youtube to share the video online. With all recorded evidence it will need to be uploaded to a website such as Youtube so you can get a link to put in the box that requests evidence. When uploading to youtube be sure you upload as public or unlisted if a video is set on private the link will not work. *Please double check all links to make sure they work properly. It is important that we can see all evidence, so all issues/bugs can be tested and dealt with properly. It is very important to give as much detail as possible as well as leaving the proper evidence when it comes to making bug reports. If the bug is unable to be recreated by our QA team you will be asked to make another report with more information.