Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
In your example, for example, puzzle games may not require completion to know whether or not they're worth your yea or nay. I reviewed PAC-MAN 256 long before I completed it, as well as Jack Lumber, Bad Hotel, and others. In these cases, I knew before completing them whether or not they were good or bad. I despised Jack Lumber early, and Bad Hotel was... bad. Didn't take 30 hours to figure that out. PAC-MAN 256, however, felt polished, smart, and worthy of a thumbs up.
To answer your initial question, my own standard is to complete the game at least once, both to experience it and confirm that it's not broken. If it is an arcade style puzzle without goals, like Tetris, maybe a little time with, a break, and more time with again to come at it with a fresh mind more than once is helpful. If there are achievements, I try going for at least a minimum 30-50%, as they feel like a good gauge for understanding what the developers intended, and seeing what I may have overlooked when playing on my own terms.
Other than that I play games through to the end and then review it
For big open world games I'll need to make notes at the start of the game, then notes after finishing the story, and notes after I'm done playing. (or else i"ll end up like I did with Monster Hunter Rise or Baldur's Gate 3, where I was like "dear god where do I start with this review?")
But currently I'm working on a Grand Strategy game called STAR WARS Rebellion, and it's taking as long as most big budget games to beat. I'm deadlocked in a fight with the Empire and don't see myself winning any time soon. In these cases I think of my reviews as one part video game feedback/critique and two part "let me tell you a story about playing through this game".
But it really depends on the game, I played a game called 100 Hidden Cats, and beat it in less then an hour. What can I say about that? "Uhhh... Yep, I found them all."
So ultimately I think the review and format you choose will heavily depend on what you're trying to tell in your review? Are you purely providing critique of your experience? Are you contrasting the game to others similar in the genre? Are you super casual and just like "Hey! This is what I think about this game".
Part of me wants to wait until I complete the game so I can say in my review that it takes "x" amount of hours to complete. But it could take me a year to complete the game because there are a ton of levels plus bonus games to play if you want all the achievements, and I only play a few games a day, I don't grind. For instance, I still haven't completed last year's Christmas/Winter themed game and the dev just announced a new one will be released soon. Sigh. Oh, and I always buy upon release (if discounted which it always is) to support the devs.