Agree with the thread: itch comments aren’t a QA lab. What has worked for short browser puzzles:
1) One public build → treat comment time as the build id.
2) When someone says “stuck / tutorial confusing,” reproduce cold yourself first; ask *one* follow-up max (“which screen / which control?”) in-thread.
3) Don’t send casual commenters to a form. Save forms for people who already volunteered for a closed test.
4) Best prompt on your own page: “Where did you first get confused?” beats “any feedback?”
Useful boundary: structured reports are for recruited testers; public itch is for rare gifts. Design so a vague comment is still actionable from timestamp + current build.