Include the exact version, platform, and relevant device or browser details. Then write the steps in order. Mention whether the issue happens every time or only occasionally. A short recording or screenshot can help when it shows the behavior without exposing private information.
Describe the smallest repeatable example
If the problem occurs after several levels, say which save or checkpoint was used. If it depends on a controller, orientation, or network interruption, include that condition. Avoid changing several settings before each attempt unless those changes are part of the issue.
Separate the observed result from an assumed cause. A frozen screen could come from several systems. The developer can investigate more effectively when the report preserves the evidence instead of presenting an unverified diagnosis as fact.
After a fix, test the original steps and nearby behavior that may have been affected. Keep the report linked to the corrected build and actual result. A passing automated test or editor run may be useful, but it does not replace retesting a device-specific failure on the relevant setup. Clear bug reports reduce repeated explanation and make it easier to distinguish a fixed issue from one that merely failed to appear during a quick check.