X

THANK YOU!

Post has been reported succesfully.

Mojang Bug Tracker Guidelines

The Mojang Bug Tracker (also known by its nickname Mojira) is the place where all bugs in Minecraft and other games created by Mojang Studios are reported, documented, and tracked. Read the full guidelines carefully before you create a bug report or participate on the bug tracker. 

If you need additional help with reporting a bug or have questions about the bug tracker, feel free to ask other players in the community by visiting our official Minecraft social channels or visit one of the community sites. 

In this article

     What can be reported on the bug tracker and what cannot? 

     How to use the bug tracker’s search function efficiently 

     Contributing guidelines 

     General bug report guidelines 

     How to write helpful bug reports 

     Project-specific guidelines 

          Minecraft: Java Edition 

          Minecraft (Bedrock codebase) and Minecraft Dungeons 

          Minecraft Realms 

     Example template 

     Example bug reports 

 

What Can Be Reported on the Bug Tracker and What Cannot? 

We will only accept your bug report if it is about a bug. A bug is something in the game not behaving the way it should, due to a problem in the game's code. As such, it should be reproducible and not be caused by circumstances outside of the game. Keeping the bug tracker focused on true bugs helps to get them addressed faster by Mojang Studios. 

The following types of issues are not bugs and are not allowed on the bug tracker: 

  • Minecraft account or payment issues 
    If you have trouble accessing your Minecraft account, or if you have payment or purchase issues (including Realms and Marketplace), please contact  Minecraft Support. We cannot help with this on the bug tracker. 
  • Suggestions and feature requests 
    To suggest a new feature for Minecraft, or to post a suggestion, do so on the official Minecraft feedback site or visit one of the community links. 
  • Parity issues introduced prior to the Buzzy Bees update 
    To report a parity issue (a difference between the different editions of the game), review the official parity issue guidelines before doing so. If your report does not fulfill all of the criteria, it belongs on the official Minecraft feedback site. 
  • Translation issues for Minecraft: Java Edition and the Minecraft Launcher 
    These translation issues need to be raised in the Minecraft or Minecraft Launcher Crowdin projects since the translation of the game is done there by members of the Minecraft community. 
    Issues with the original “English (US)” language are allowed on the bug tracker since they are not included in the community translation process. 
  • General connection issues (Realms, Marketplace) and authentication issues 
    These issues are typically outside the control of the game’s code and are usually due to server maintenance, downtime, or local network configuration. If the issues persist, consider asking the community (see FAQs). 

How to Use the Bug Tracker’s Search Efficiently 

Before reporting a bug, always search for an existing report. Here are a few tips on searching for existing bug reports: 

  • Use as few keywords as possible. The search engine will only find bug reports containing all of the words in your query. For example, search for “squid suffocate” instead of “Squid will frequently suffocate for no reason when swimming around in a river”. 
  • Verify all words spelled correctly. 
  • Try multiple separate searches using synonyms. For example, “workstation”, “job site”, and “profession block”. 
  • Restrict your search to the project you want to report the bug too. A list of all current projects with their description is included below. 
  • Sort your search results by date created, with the newest bug reports on top. Review them to see if they describe your issue. 
  • If there are too many bug reports to review easily, you can change the sort criteria (e.g., sort by votes), further refine your search query, or exclude already resolved bug reports. Keep in mind though, that the issue you’re searching for may have already been addressed in a resolved report. 

If you find that your issue has already been reported, look at the Resolution of the report to determine what steps to take next. 

Resolution Statuses 

  • Unresolved – The bug has not been fixed yet. In this case, vote for the bug report. This helps us gauge how many players are affected by the bug. You can also add more information to the bug report if you think anything is missing (see below). 
  • Awaiting Response – View the “Comments” section to see what is missing from the bug report. You can provide this missing information in a comment to reopen the report (see below). 
  • Duplicate – Follow the link to its parent report in the “Issue Links” section. That parent report is where your issue is tracked. 
  • Fixed – Find the “Fix version”. This is the version in which the bug was fixed by Mojang Studios. If you’re using a newer version than the one specified, create a new bug report if you can’t find another, newer report about your issue. If the fix version is a “Future version”, the bug will be fixed in a version that has not yet been released to the public. 
  • Other Resolutions – Read the comments carefully, if there are any, to understand why it has been resolved. Also, see our FAQ for more information on what the different resolutions mean. 

Contributing Guidelines 

If you found an existing bug report about your issue, you can add more information by commenting or attaching a file (e.g., a screenshot or video).  Follow the following guidelines when contributing to the bug tracker in any way: 

General 

  • IMPORTANT The bug tracker is a public place. DO NOT share your password, email address, transaction ID, or other personal information under any circumstances. 
  • Do not impersonate others, for example via your username or display name. 

Comments 

  • Do not leave a comment on a bug report if you don't have anything new to add. 
  • Do not add comments like “me too” or similar that simply state that you experienced the bug without any further information. 
  • Keep all comments related to information about the bug itself. Complaints and criticism of Mojang Studios, its employees, or anyone else are not acceptable on the bug tracker. 
  • Any kind of profanity and NSFW content is not allowed on the bug tracker. 
  • If you want to initiate a discussion about a bug or need to report someone, take the discussion outside of the bug tracker (see FAQs), do not comment directly on the bug tracker. 
  • Do not imitate or use the preformatted responses used by helpers or moderators. 

Attachments 

  • Do not attach new screenshots unless they show something significantly different than the ones that are already part of the bug report. 
  • When attaching a file to an existing bug report, post a supporting comment for context. 
  • When embedding an image in a comment (or in the description of a bug report), make sure that the image size is not too large. If the image doesn't properly upload, try uploading a smaller one. 
    To embed an image, use the following markup in text editing mode: 
    !picture_name.png|thumbnail! 
  • IMPORTANT Remove any personal information (email address, gamer tag, realm links, etc.) from your attachments before posting them. 

General Bug Report Guidelines 

When creating a bug report, keep the following guidelines in mind: 

  • IMPORTANT If your bug report contains sensitive information which you don’t want to be publicly visible, set the “Security Level” of the report to “Private” and explicitly mention that you don’t want it to be public. 
  • In case you have discovered an exploit or security issue, set the bug report’s “Security Level” to “Private” so that only you, Mojang Studios employees and bug tracker moderators are able to view your bug report. 
  • Before creating a bug report, spend time checking whether someone else has already reported it. See the tips above on using the search effectively. 
  • We only accept bug reports in English, do not create bug reports in other languages. 
  • Only put one issue into each bug report. We will not accept your bug report if you include multiple bugs. 
  • If you are using any mods or third-party tools at all, see if the issue persists in a completely unmodified Minecraft environment before reporting it. If it doesn't, report the bug to the mod creator, not Mojang Studios. 
  • This includes third-party server software, such as Spigot or Paper. 
  • OptiFine is considered a mod in all circumstances. 
  • Worlds that have been opened with a third-party tool are not supported. 
  • If you have an issue on a large multiplayer server (like Hypixel or The Hive), contact the server staff first before creating a bug report. These kinds of servers often run modified server software that is not supported by Mojang Studios. 
  • Only report a bug if you are sure that it is still active in the latest version of the game. We do not accept bug reports for any versions except for the latest release and the latest development version. 
  • Report the issue to the correct project: 
  • MC: Minecraft: Java Edition – Windows, Mac and Linux 
  • MCPE: Minecraft (Bedrock codebase) – Amazon Fire TV, Android, iOS, Nintendo Switch, PlayStation®, Windows 10 (from the Microsoft store), and Xbox. 
  • MCD: Minecraft Dungeons 
  • MCL: Minecraft Launcher – Launcher for Minecraft: Java Edition and Minecraft Dungeons 
  • REALMS: Minecraft Realms – Issues with Realms management or that only occur on a Realm 
  • BDS: Bedrock Dedicated Server – Issues that only occur on Bedrock Dedicated Servers 
  • WEB: Mojang Web Services – Issues with one of Mojang Studios’ websites 
  • The “Labels” field is for use by helpers or moderators to help organize bug reports. Only use existing labels and don’t create new labels. For more information on how labels work, see our FAQ. 
  • After creating a bug report, watch for related emails or regularly check the bug report for updates or potential further inquiries. 
  • Keep the project-specific guidelines in mind as well. 

How to Write Helpful Bug Reports 

To help ensure that your bug report is effective, it is highly recommended that you follow these guidelines: 

  • Write a concise summary that clearly states the problem. Avoid generic statements like “Help!”, “It doesn't work”, “It’s broken”, or “There’s a bug”, and instead use a short phrase to accurately summarize your issue. You may find it helpful to think about what you would search on to find the issue. 
  • Include precise steps to reproduce the issue. Write down what exactly you did that caused the issue. If you are not sure, try to recreate the bug in a test world. Use a numbered list for the steps, so it is easy for someone else to follow. 
  • After listing the steps, clearly state what happens, and what you believe should happen. 
  • Include the exact text of any messages (e.g., error messages) that appeared at the time of your issue. 
  • Attach screenshots to the report to showcase the issue more clearly. If possible, you can attach a short video as well. In some cases, it might also make sense to provide a world save (as ZIP archive). 
  • If the attachment file size is too large, upload it somewhere else and link to it in the description of the bug report. For more information on this, see our FAQ. 
  • If your bug is linked to a specific world, such as a world generation, portal transport, biome, or structure issue, be sure to include the world seed and all relevant coordinates. 
  • Do not use excessive formatting (bold, all caps, large text, multiple blank lines, etc.). 
  • If you are aware of any situation in which the behavior you are reporting is used as a feature, mention it in the description of your bug report. This way the developers can decide if they want to keep the behavior or add a respective replacement for it. 
  • Take your time. Read over your bug report to make sure you didn’t leave out anything and that everything is clearly explained. 

Project-specific Guidelines 

Minecraft: Java Edition 

  • To report a crash, attach the crash report to the bug report. You can find crash reports in the “crash-reports” subfolder of the .minecraft data folder. If there is no related crash report, attach the launcher log. 
  • If you create a bug report about a server-side performance issue, include the debug profile and report to the bug report. You can create them by using the /debug. 
  • If you create a bug report about a client-side performance issue, provide detailed information about your system specifications and the circumstances in which the performance issue occurs. Bug reports about general performance issues (for example “Minecraft always has low FPS”) are usually not accepted. 

Minecraft (Bedrock) and Minecraft Dungeons 

  • Always specify exactly what device (platform) you are using. 
  • Crash logs are automatically collected and reported to Mojang Studios. Only report a crash if you can provide a list of steps to reproduce the crash. 

Minecraft Realms 

  • Make sure the Affected Version and Platform match. 
  • Specify the device you are using in the Environment field. 
  • Specify whether you are the realm owner. 
  • Search the corresponding main project (MC or MCPE) for existing bug reports also. 
  • If you are unable to connect to realms that were previously working, check the Official Mojang Status to see if there are any scheduled maintenances or other connection issues. 

Example Template 

Here’s an example of how you could format a new bug report; feel free to copy and paste this: 

[Briefly describe the bug here] 
 
Steps to Reproduce: 

  [Step 1] 
  [Step 2] 
  [Step 3] 

 
Observed Results: 
[Describe what happens] 
 
Expected Results: 
[Describe what should happen] 
 
Screenshots/Videos: 
[Optional: Attach an image or short video] 
 
Notes: 
[Any further information you can provide about the bug, such as explaining any attachments you’re including, when the bug started to occur, how you’ve tested the bug,  
messages displayed (e.g., error messages), and how the bug impacts gameplay.] 

 

Example Bug Reports 

Here are some well-written bug reports that you can use as examples: 

Last Updated - 2021-08-03 21:18:05 UTC

Was this article helpful?