I’m not really interested in the motivations of the developer or the reviewer, the type of game, how long it was played or any of those extraneous details. When I saw the post, I thought about how I would handle this kind of situation, and what I can do to turn this kind of feedback into something useful, to myself, the reviewer, and the project as a whole.
Let’s take the review at face-value: the reviewer has purchased the game with the intent of enjoying it, and went into it with an open mind. Assuming anything else is going to negate anything useful that can be gleaned from the review. They put in a significant amount of time (4 hours is more than enough IMO) and came away unimpressed, to the point of a snarky hot taek on the game’s Steam page.
Were it me on the receiving end, I would clearly be upset at first, but I would then have to take a critical look at the game. What’s the point of the game? Is it appealing to the audience for whom I made it? Is it a cost/playability ratio that is off? Can I get in touch with this player to see if I can get more insight? Is there any clue from the rest of the reviews as for the underlying issue?
Looking at the rest of the reviews, there are some consistent threads that point to improvements that could be made. The ways to re-engage with the development cycle on the game from a players perspective sounds like marketing buzz-speak, but sometimes they can be valuable. Beta testing can only tell you so much, and it’s not a substitute for real-world experience.