Did you know that MoJira is our public bug tracker for Minecraft? And by bug tracker we don’t mean a tool for monitoring pesky insects – It’s where players can look up known issues, follow along as reports are updated, and (when needed) submit new reports to bother our devs help the team investigate and fix problems. And that reporter could be YOU. Everyone loves a problem-solver!

Reminder: MoJira is a public place for everyone to browse and report bugs, so please don’t include any personal or contact information (or your gamer tag) in reports, attachments, or comments.

Bonus: Want the quick tour before you go bug-hunting? Watch our bug tracker video on YouTube — floating villagers, flying squids, and all. Consider it your little “how-to” book before you head into the Overworld to gently scoop up a bug report (and carry it outside).

Start here: browsing and reporting

• bugs.mojang.com (browse): a public, read-only view where anyone can search and browse reported issues.
• report.bugs.mojang.com (report): the bug reporting portal where you sign in to submit a new report (and interact with existing reports when available).

Browsing bugs on bugs.mojang.com

If you want to see whether an issue is already known (or you’re just curious what the community is reporting), start on bugs.mojang.com. You can browse issues without signing in, open an issue page, and read the details that have been shared so far.

Search (and narrow results with filters)

The fastest way to find an issue is to search first (using as few keywords as possible), then use the filters to narrow things down. This is especially helpful because many reports use similar keywords (for example, “crash”, “freeze”, or a mob name).

Before reporting a bug, it’s always worth searching for an existing report – there’s a chance the issue has already been reported and tracked.

• Use as few keywords as possible. Search only finds reports that contain all the words in your query. For example, try “squid suffocate” instead of a full sentence.
• Double-check spelling. A single typo can hide the results you’re looking for.
• Try a few separate searches using synonyms. For example: “workstation”, “job site”, and “profession block”.
• If you find your issue already reported, check the report’s Resolution to see what to do next.
• Project / game: choose the area you’re playing (for example, Java Edition vs Bedrock).
• Status: focus on open issues, fixed issues, or other states depending on what you’re trying to confirm.
• Affected version: narrow results to the version you’re currently playing.
• Platform: filter to a specific device/OS when the issue only occurs on a certain platform.
• Sort options: switch between “most recent”, “most relevant”, or other orderings to find the newest activity.

Tip: include a couple of specific details in your search (an error code, a feature name, or the name of the block/mob involved). Searching for short phrases like “world won’t load” or “split screen” can also be more effective than a single word.

Reporting a bug on report.bugs.mojang.com

If you can’t find an existing report that matches what you’re seeing, head to report.bugs.mojang.com. This is the reporting portal where you’ll sign in and submit a new bug report.

Please use the issue browser on this page to check whether your issue has already been reported. If you haven’t already, make sure you’ve read the Bug Tracker Guidelines – reports that don’t follow the guidelines may be invalidated.

Important: All reports must be submitted in English, as it’s the common language used on this bug tracker.

Recommended description format

• Submit one issue per report. If you’ve found multiple problems, create separate reports so each one can be tracked clearly.
• Use a clear title. A short summary like “Game crashes when opening the world list” helps more than “Help!!!”.
• Include steps to reproduce. Tell us what you did, what you expected to happen, and what actually happened.
• Add environment details. Include your platform/device, game version, and any relevant settings (resource packs, add-ons, multiplayer/Realms, etc.).
• Attach helpful evidence when you can. Screenshots, short clips, or logs can make an issue much easier to diagnose.

After you submit

To show that an issue affects you, you can add a vote to an existing report. You can also watch a report to get updates when it changes.

Comments are most helpful when they add new, relevant information (for example: clearer reproduction steps, additional details, or logs). Please avoid “me too” comments – use votes instead.

Once your report is submitted, you can use the public site to keep an eye on updates. If someone asks for more information (or you discover new reproduction steps), adding that detail to the existing report is usually more helpful than creating a duplicate.

Quick checklist

• Browse first on bugs.mojang.com and search with filters to avoid duplicates.
• If you don’t find a match, submit a new report on report.bugs.mojang.com.
• Include clear reproduction steps and your platform/version so the issue can be investigated faster.

Feeling enlightened? Excited? Educated? Then you're more than ready for becoming a great bug catcher! Good hunting, and let's hope your encounters will be few!