How to give feedback that helps

Give a reproducible note

Try the actual build when possible. Say which version and device you used. Describe the exact moment, what you expected, and what happened. Separate a bug from personal taste.

Browser demo v0.3, keyboard on Windows. At the second door I pressed E, but nothing happened. I expected it to open because the same prompt worked at the first door.

One useful observation is better than a vague score. Mention something that worked as well as the main problem. Do not claim to have played when you only watched a video.

Keep it in the game thread

Use the game’s existing Discord thread. The website’s feedback links return there. Do not include personal contact details, private messages, API keys or other people’s information in a public report. Ask permission before sharing a recording of someone else.

For creators

Ask one or two specific questions and give an approximate play time. Respond when you can with what changed or why you kept a design. React with the server’s helpful emoji when a comment genuinely helped; points depend on the configured rules, not praise alone.

You can select your own development posts for the public Project timeline. This does not copy another member’s feedback. Manage your game explains it.

Recognition and votes

The public weekly thank-you roll lists names without scores. Private bot commands can show feedback standings; other bot notices may mention milestones. Jam voting is a separate event process using the announced reaction emoji. See Byte commands and Jam handbook.

Members who want to review regularly can join the optional Playtest Crew. Its weekly ranking lists only members who chose to appear in it. Playtest Crew explains the commands, the ranking and the monthly awards.