Give the reader a recognisable situation
Give the reader enough context to recognise the moment: which title was open, which control you pressed and what happened on screen. A description of the boat moving before a missed cast is more useful than a vague verdict. Keep personal contact details and other people’s information out of public notes.
Explain whether it is a suggestion or a failure
Separate a suggestion from a malfunction. Wanting a quicker rover is a preference; a direction button ignoring every press is a possible fault. Describe the expected response, the observed result and the steps you repeated before writing the report.
Read the panel’s response before assuming success
The public discussion panel depends on the site’s community service, whereas the game runs in the browser. A server problem can therefore interrupt comments without stopping play. Read the panel’s response before assuming a contribution was accepted; the site does not fill outages with fabricated player posts.