So About That Time I Gave Hellblade A 1/10…



Sometimes you don’t quite consider every facet of something until the thing is done. Unfortunately this was the case with a previously published review for Hellblade.

The review will be back, but given the personally unprecedented situation, I need to think about it more than I initially did.

20 Comments:

  1. It’s ok Jim. I still love ya.

  2. Zelda Breath of the wild should be a 1/10 for the fanboy meltdown it had from Jim sterlings 7/10 score

  3. Didn’t you once attack IGN or something for doing this exact thing?

  4. You didn’t care much for Prey as a game, but you’ve seen how people reacted to IGN’s 4/10 review where the game was rated down for a specific bug. You don’t want to be compared to IGN, ever 😀 .

  5. Oh thank god Jim, no new shit intro on this video. I would give your new intro 1/10…

  6. This is just anothet reason why I respect Jim so much. Admiting that he did not handle it perfecty (and be honest, everyone does mistakes) and actually doing something to improve the situation (metacritic). THIS is what a true critic does, not thinking his opinion is “true”, but actually providing consumers the right information. Thank you Jim!

  7. rating a game down that much for a single bug, especially when it is predicated upon a very specific set of actions, is beyond extreme.
    even if it is something you cant get past, plenty of games have had them and plenty of good games probably still do.

    perspective sterling, perspective…
    you even hint at how you want this product to succeed after it is fixed, thing is a lot of people probably played through it with 0 issues, at least any issues as bad as you portray here, perhaps the better thing to do would have been to retry and specifically avoid the bug, see where it goes, yet take the bug into account when scoring.

    the worst thing to do is to give a knee jerk reaction and give it the lowest score possible, that way ythe developer wont get your point, and a lot of the audience probably wont either.

  8. Don’t you think this is a prime example why attaching number to game reviews is bad idea? I fell like your original review would be perfectly fine as it is without that number. People would think more about whether the game is worth buying primarily based on what you said (which was mainly praising the game) and they should consider whether the possible game breaking bug would stop them from buying it. 1/10 at the end just feels like “ignore what I said, this game is shit”.

  9. I feel like you should come up with a score you feel is completely fair if the bug had never happened. *_Then deduct two points from that._* I agree with both sides, the game needs a fair review, but including a negative repercussion for the sheer seriousness of this bug is not only justified, but the most helpful, informative decision for potential buyers of the game.

  10. Why aren’t there multiple saves? Auto overwrite of a single is appalling design. It almost seems like the reasoning is “because fuck you!” XD

  11. I would be extremely mad too and lash out if it happened to me, who knew you were human too?

  12. In summary, reviewer has bad experience with game and review reflects this. Community decides reviewer’s opinion is wrong because whatever bullshit reason. Reviewer needs to change opinion because people are ragey babies and want the score higher… Jim literally couldn’t play the game anymore. A 1 is justified.

  13. This wouldn’t be a problem if game devs would bother to program MULTIPLE MANUAL SAVES. How it used to be. Who the fuck came up with the idea of ONE save slot? ??

    Deal with the 1/10. It deserves it. Untested, game breaking bug slipped through, ONE save file because fuck you…

  14. Going purely by what I’ve seen in this video… yeah, “I ran into a bug, therefore 1/10” is not a reasonable score. Your score is supposed to be a user guide, a general hint as to how good a product is, and one rare bug most players are likely not to even encounter shouldn’t be that big of an effect on that. If the game was riddled with bugs like these, I think it’d be a more reasonable thing to do, but judging by what you’ve said, that’s not the case.

    I also do wanna point out, how does this fit in with the “review only games you’ve finished” policy? Far as I see it, this is an invalid review, and the correct thing to do here would have been to restart the game, and make mention of the fact there’s a bug like this and an autosave feature that might cause some issues.

  15. A game-breaking bug is a game-breaking bug. Anyone can argue “Well, it was caused by the player’s actions,” but the game should not have a condition where the player’s actions can permanently prevent all forward progress like that. (This is not the same as a game-over screen on a perma-death game etc., those are acceptable.) What’s surprising to me is that you claim this is the first time it happened to you, Jim. Given the quality of games you tend to play, that’s kinda amazing. I’ve had it happen several times in titles from major publishers even. I always consider the game an auto-fail at that point, if there’s a condition that completely breaks the game. Not sure i’d give a 1/10, not sure I’d give it a score at all. More of a warning. “If you do this, the game breaks. DON’T DO THIS. Bad game, no biscuit for you.”

  16. Dr.Sir Bruce Armstrong Mother Fucker The Third

    Giving the game a 1/10 simply for a game breaking bug is asinine. Yes, that game breaking glitch is terrible, and should have lowered it to a 6/10, but to slap a rating on the game on par with the worst games of the year is purely unprofessional, and that’s kind of a big turn off cause it will make people who take your word to heart and look at your rating for the game and don’t even consider touching a game that you actually enjoyed playing. I acknowledge you admit your mistake, but that doesn’t change it was a fuckin’ dumb mistake. If you’re just gonna throw scores like that in the wind because of one glitch, you might as well stop having a rating system.

  17. Fuck that, don’t release a game unless it’s ready. If it’s a broken mess of a game than the devs are to blame. Deal with your shit score.

  18. If you were reviewing a meal and you loved it up till the point where you encountered a foreign object that made you not want to finish it; how would you rate that experience? I believe you would be justified in rating it the same as a rotten big mac. even if you enjoyed it till the point you noticed said object. I believe the same can be said about game reviews.

  19. If you can’t guarantee your game is free of gambreaking “bugs” (or rather oversights) then make more than 1 save file or a failsafe. I personally feel 0/10 is justified on a broken product. If I bought a washing machine that couldn’t get through a single load of laundry I would consider that a worthless product regardless of how the machine, sounds, looks or worked for the first few minutes before it started smoking and never turned back on.

    Jim is a critic not a game tester, it is not his job to wait for devs to fix their games and if it was he could never criticize any broken ass steam release with no exe again due to the double standards of “well how can he give a full impression if he has not played it”

  20. fuck incomplete products and anyone selling them
    1/10 is deserved

Leave a Reply

Your email address will not be published. Required fields are marked *