Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

That’s fair. I was probably treating casual itch.io comments too much like reports from a structured playtest.

Asking someone who voluntarily left a short comment to fill in another form would likely create more friction than useful context. Your point about the build is fair as well. For a public itch.io page with one current build, the comment timestamp should normally be enough.

I was partly thinking about closed tests where different builds are sent to different testers, but that is a different workflow from normal itch.io comments.

The tutorial example is useful. It sounds like the developer should first try to reproduce the player’s experience with no prior knowledge, then ask one focused follow-up question only if necessary.

When you receive a vague but potentially useful comment, do you normally ask for clarification in the same thread, or just investigate it yourself?

(+1)

I've replied to a comment to ask for clarification - but received none.  Most of my games / assets have zero comments.

That’s useful context. It sounds like the bigger problem on itch.io is getting any feedback at all, rather than organizing it once it arrives. A more detailed reporting form wouldn’t help if players aren’t commenting in the first place. Thanks for clarifying.