You Have Not Entered the World Yet
For failure before entering the world, first check platform, version, address, and the Bedrock port. Then look for reports of simultaneous disconnections or maintenance information. Several people failing and only you failing are worth recording separately, but neither alone establishes the cause. Retain complete error text; a screenshot showing only 'Failed' is usually insufficient.
An Explicit Version-Mismatch Message
For an explicit version-incompatibility message, check the current announcement instead of repeatedly reconnecting with identical settings. Java and Bedrock have separate version numbers; name the edition in full. ViaVersion and Geyser being listed does not mean every old and new version can join. If the recommended version still fails, add the entrance and the stage at which the message appears so maintainers can check compatibility.
You Have Joined but Cannot Act
Inability to move or interact, or a verification prompt, may concern login, area settings, or other restrictions. Read the full prompt before choosing a step, rather than conclude the entire server is frozen because you cannot move. Handle a login prompt through login procedures; for an area denial, describe location and action. Separate symptoms from guesses in your report.
You Can Act but a Command Fails
Record the full command, actual feedback, and location. Unknown commands, insufficient arguments, and insufficient permissions are different responses: check spelling and source for an unknown command, actual usage for missing arguments, and availability to you for permission failures. Do not demand full administrative access or try alternate aliases repeatedly to bypass restrictions.
The Game Works but the Website or Synchronization Does Not
If the game works but the website does not open or QQ messages do not synchronize, describe a component issue. State which end sent, which failed to receive, when, and whether the game was working. Do not declare total server failure or send numerous test messages. One clear example usually explains more than dozens of tests and leaves others room to chat.
A Fault Description You Can Copy
Use this format: edition and full version; connection entrance and port; time; status beforehand; action taken; screen feedback; one step already tried; whether others had the same failure. Write 'Unknown' where information is missing rather than guess. Passwords, private verification codes, and unrelated personal information are not necessary for a fault report.