Bug Reports & Feedback

Good reports ​

A good bug report explains what happened, what you expected, and how staff can reproduce it. Short reports are fine as long as they include the important details.

What to include ​

• your Minecraft username or gamertag
• Java or Bedrock platform
• the server or branch where it happened
• event name and approximate time
• screenshots, clips, or logs when useful
• exact steps that caused the problem

What not to share publicly ​

Do not post private tokens, IP addresses, personal information, or staff-only debug details in public channels. Use the correct private support route if a report contains sensitive information.

Feedback ​

Feedback is best when it includes the problem, why it matters, and a suggested improvement. This makes it easier to compare ideas and prioritize changes.