A useful distinction
“The game broke” does not show how to reproduce the problem. A useful report describes the starting state, actions, expected result and observed result. It can also name the browser and version without exposing private account information.
Put it into practice
Write a short numbered sequence using only necessary details. Try it once again in an appropriate test context to check the description. Include a screenshot only when it clarifies the state, and redact identifiers. Keep a suspected cause separate from the observed behaviour.