Problem is he already delayed it due to not getting the game until after release.What is the standard policy for a reviewer who encounters a "game breaking" bug?
I would have thought that they'd be obliged to check around and see how many other people encountered it and then used that info to decide how much to dock the game's score.
A four out of ten might be okay if said bug is happening to a lot of people but if it's 1 in a thousand wouldn't the reviewer be better off delaying the review?
Problem is he already delayed it due to not getting the game until after release.
They're a company who has to make money, and you do that with clicks. And no one is going to care about their review in another couple of days.
It is what it is.
Yeah, problem is most people will just look at the score.I guess you just cross your fingers that people will be smart enough to see the situation for what it is and treat the review accordingly.
To be honest reviews have little or no influence on my decision to buy a game or not.
Sorry, only 5 hours lost. I don't even play zombie modes cause I don't like the feeling of losing progress after an hour of running around, so I still see where he's coming from. I'd pick the game up a year later and try again.
Yeah, problem is most people will just look at the score.
Do Quick looks and podcast discussions got as reviews? Because those influence my decisions.
Yeah, problem is most people will just look at the score.
Do Quick looks and podcast discussions got as reviews? Because those influence my decisions.
Exactly. That's the thing with reviews that quick looks or even just watching 30 minutes/an hour of a stream or Let's Play can't do. Reviews are retrospective, providing a perspective of a game as a whole, rather than just the snippet you get from the other means. The latter might show you how a game plays, but it can't tell you if the game stays as good throughout, if it sticks the landing, if issues appear later or compound over time, and so onIf they can cover the game mechanics and how they adjust throughout the entire game and so forth sure. But frontloading is a real thing, and will continue to be for some titles so quicklooks can be a bit weak in that regard. For instance a number of recent quicklooks I have watched have absolutely no idea whats occurring in the game and what was reported many times didn't reflect anything about the gameplay later on.
That's not how it works. The game he got in release broke. Is he supposed to write an open letter on video game forums and poll those affected before dropping his review? No. And the fact that he's a part of a bigger publication is good as it will bring light to the issue. Imagine if no one complained and then the bug hit a bunch of users. Then the thread would be full of people mad the score was so high. If it was a small site, folks would call it click bait to get attention. There's no winning.
For the reviewer it did. It sucks, but that's what happens. Unlike the joycon thread which took place a week before release, this is happening after release, so imagine if the game had an actual review schedule, the problem could've been ironed out and the author might not have thrown up their hands. Saying this is lashing out at Bethesda (not you) is looking at it from a very petty and sad point of view.
You should read what you posted. A game with unfinished modes before release versus game breaking bugs after release.
Review threads bring the worst out in people.
Review scores are largely arbitrary.
But a 4/10 is a joke.
seems fair if you run across a game breaking bug tbh.
i mean, if i came across the same sort of thing in any game or was forced to start over, no matter how good it was up to that point, it's just thrown itself into the shit pile. the bug shouldn't be there for anyone...end of. it doesn't matter if it's 10 or 10 thousand people experiencing it. there is a risk of it happening there that shouldn't be in something that costs $60.
i personally don't have a habit of recommending games that offer a Russian roulette chance of bugging the fuck out. why would IGN?
Who's worse, the reviewer grinding the axe or the editor letting them bury it?
The bug stopped them from proceeding but it was also fixed on the day it went up and the save worked again so no progress was lost?seems fair if you run across a game breaking bug tbh.
i mean, if i came across the same sort of thing in any game or was forced to start over, no matter how good it was up to that point, it's just thrown itself into the shit pile. the bug shouldn't be there for anyone...end of. it doesn't matter if it's 10 or 10 thousand people experiencing it. there is a risk of it happening there that shouldn't be in something that costs $60.
i personally don't have a habit of recommending games that offer a Russian roulette chance of bugging the fuck out. why would IGN?
seems fair if you run across a game breaking bug tbh.
i mean, if i came across the same sort of thing in any game or was forced to start over, no matter how good it was up to that point, it's just thrown itself into the shit pile. the bug shouldn't be there for anyone...end of. it doesn't matter if it's 10 or 10 thousand people experiencing it. there is a risk of it happening there that shouldn't be in something that costs $60.
i personally don't have a habit of recommending games that offer a Russian roulette chance of bugging the fuck out. why would IGN?
The bug stopped them from proceeding but it was also fixed on the day it went up and the save worked again so no progress was lost?
Seems like just, you know, boot the game and verify "hey it works now" would be great.
The bug stopped them from proceeding but it was also fixed on the day it went up and the save worked again so no progress was lost?
Seems like just, you know, boot the game and verify "hey it works now" would be great.
Seems like a logical next step in such a situation, however I can't say I don't empathize with the reviewer a bit, he ran across something that nulled his entire progress and since reviews are subjective, he was well within his rights to score it as low as he did based on his personal experience.
And even though it WAS fixed pretty quickly, it doesn't change the fact that for a while he felt as if he just wasted 40 hours of work, negative feelings like that tend to leave a bad mark. Besides, after fixing the issue - according to the review, wasn't the game crashing constantly later on? I bet that also affected the score on top of the save glitch.
The whole situation is a bit tricky overall, since many here seem to be approaching this from their own standpoint on what a reviewer should be, objective, subjective, held to a higher standard etc. that's why it's hard to find a common ground here.
Personally, I don't hold reviewers to a higher standard, that's why I don't think due diligence was neccessary here. One guy had a shitty experience? No problem, there's countless other reviews to compare it to and see for myself if it's the norm or an outlier.
The entire 'official' reason for Bethesda's review policy was so gamers and reviewers can experience the same game at the same time, so I hope they still think it was a good idea. Because before, the guy would probably still be under embargo and they'd have some time to resolve this issue hush hush. Would it affect the score? I bet, but the reviewer would have some time to settle down and finish the game without pressure.
He only lost 5 hours of progress though, not all 30.
He only lost 5 hours of progress though, not all 30.
Why not? Other writers do opinion pieces and reactions to other writer's articles all the time. Like all the reactions to the "Video Games Are Better Without Stories" article last month
So would people prefer he gave it a 9 with a 'btw, the game straight up broke while I was playing it an I lost 5 hours of progress'.
That'd be a lot worse, in my opinion.
I don't care about the score but why would you give a broken game a 4 when he thinks it's very game breaking?So would people prefer he gave it a 9 with a 'btw, the game straight up broke while I was playing it an I lost 5 hours of progress'.
That'd be a lot worse, in my opinion.
Except he didn't lose any progress. They had a fix out by the time he published his review.So would people prefer he gave it a 9 with a 'btw, the game straight up broke while I was playing it an I lost 5 hours of progress'.
That'd be a lot worse, in my opinion.
Except he didn't lose any progress. They had a fix out by the time he published his review.
The saves were not corrupted, only refusing to load due to a bug.
That bug obviously should not have been there, and perhaps if Bethesda had handed out review copies a week or two prior to launch it could have been resolved before the review was published, but this just seems like Dan is trying to strong-arm Bethesda into changing their policy on review copies rather than "informing consumers".
He was already in contact with the developers about this, but felt that his need to publish a review as soon as possible was more important than due diligence.
Since this bug was corrected in a matter of days - and is no longer a "beta patch" - all his review does is misinform readers of IGN, and hurt Arkane Austin.
I cannot understand how he arrived at giving the game a 4/10 though.
I agree that reviews scored on a 100-point scale - or perhaps any point-based scale - are largely meaningless, but if you are going to give the game a negative review based on a "game-breaking" bug that you encountered, it should be an instant 0/10.
A 4/10 score is Dan's attempt at lashing out. It says "this is a very bad game" not "this game is broken and thus we could not complete a review".
Again, if you just read the score you think it's a bad game. But if you actually read even just the first and last paragraphs he literally says "This is a good game that I can't recommend due to the potential of a game breaking bug."Except he didn't lose any progress. They had a fix out by the time he published his review.
The saves were not corrupted, only refusing to load due to a bug.
That bug obviously should not have been there, and perhaps if Bethesda had handed out review copies a week or two prior to launch it could have been resolved before the review was published, but this just seems like Dan is trying to strong-arm Bethesda into changing their policy on review copies rather than "informing consumers".
He was already in contact with the developers about this, but felt that his need to publish a review as soon as possible was more important than due diligence.
Since this bug was corrected in a matter of days - and is no longer a "beta patch" - all his review does is misinform readers of IGN, and hurt Arkane Austin.
I cannot understand how he arrived at giving the game a 4/10 though.
I agree that reviews scored on a 100-point scale - or perhaps any point-based scale - are largely meaningless, but if you are going to give the game a negative review based on a "game-breaking" bug that you encountered, it should be an instant 0/10.
A 4/10 score is Dan's attempt at lashing out. It says "this is a very bad game" not "this game is broken and thus we could not complete a review".
A 0 would at least make people read it as they would go "wtf"Ok, then let's do this from now on. Game breaking bug = 0/10. And let's start with Prey because why not, make it the scapegoat, noone seems to give a fuck about Arkane, one of the last studios that tries to make AAA niche games.
Prey and Arkane do not deserve this. Bethesda maybe, but not the devs.
I am not saying that I think the game deserves a 0/10 score.Ok, then let's do this from now on. Game breaking bug = 0/10. And let's start with Prey because why not, make it the scapegoat, noone seems to give a fuck about Arkane, one of the last studios that tries to make AAA niche games.
Prey and Arkane do not deserve this. Bethesda maybe, but not the devs.
This really isn't a difficult situation. All Dan had to do was sit on the review for a bit until the patch came out to see if it fixed anything. He didn't, he chose to run the review because he's a petty asshole with an axe to grind. If he'd waited A SINGLE DAY he wouldn't have had the justification to run that review. IGN's not gonna fail because a single review ran a day later. He knew what he was doing. He published the review just before the patch came out (which he knew was coming) precisely because he would lose justification to run the review as-is after the patch.
All the navel-gazing about scores is beside the point. The situation the review describes literally doesn't exist anymore. It existed for less than a week in grand total, and even then, it was a very rare occurrence. Yet that review will now stand, probably forever. Fuck Dan Stapleton.
(...)
if you gave us early review copies, things like this wouldn't happen' - at Arkane's expense.
This really isn't a difficult situation. All Dan had to do was sit on the review for a bit until the patch came out to see if it fixed anything. He didn't, he chose to run the review because he's a petty asshole with an axe to grind. If he'd waited A SINGLE DAY he wouldn't have had the justification to run that review. IGN's not gonna fail because a single review ran a day later. He knew what he was doing. He published the review just before the patch came out (which he knew was coming) precisely because he would lose justification to run the review as-is after the patch.
All the navel-gazing about scores is beside the point. The situation the review describes literally doesn't exist anymore. It existed for less than a week in grand total, and even then, it was a very rare occurrence. Yet that review will now stand, probably forever. Fuck Dan Stapleton.
"IGN's Executive Editor of Reviews" - Dan
Prey reviewer - Dan
![]()
The next time a telltale game gets reviewed at ign and scores above a 4 then we know Dan had a bone to pick with Bethesda.Aha.
So does he ask his reviewers to knock points off for every bug they encounter?
This really isn't a difficult situation. All Dan had to do was sit on the review for a bit until the patch came out to see if it fixed anything. He didn't, he chose to run the review because he's a petty asshole with an axe to grind. If he'd waited A SINGLE DAY he wouldn't have had the justification to run that review. IGN's not gonna fail because a single review ran a day later. He knew what he was doing. He published the review just before the patch came out (which he knew was coming) precisely because he would lose justification to run the review as-is after the patch.
All the navel-gazing about scores is beside the point. The situation the review describes literally doesn't exist anymore. It existed for less than a week in grand total, and even then, it was a very rare occurrence. Yet that review will now stand, probably forever. Fuck Dan Stapleton.
The worst version of Prey is the game its ending thinks it is, an action-y game with stealth elements about humanity and moral choices. The best version of Prey is the game that happens in between, one where you ignore its plot completely, take your time to explore every cranny, and hide in a tree to look at the stars. It fails itself when it tells you what to do, but you have plenty of opportunities not to listen to it and have a great time in the process.
I concur with this post. This whole situation was handled poorly and unprofessionally. Although I struggle to use the word 'professional' with "games journalism" these days. Situations like this don't help.
IGN's Dan Stapleton just updated his review after bug was fixed.
http://www.ign.com/articles/2017/05/13/prey-review-2
8.0
IGN's Dan Stapleton just updated his review after bug was fixed.
http://www.ign.com/articles/2017/05/13/prey-review-2
8.0
IGN's Dan Stapleton just updated his review after bug was fixed.
http://www.ign.com/articles/2017/05/13/prey-review-2
8.0
Does Metacritic update in situations like this? If not, that's a SUPER dick move from IGN.