EmCeeGramr
Member
I'm somewhat conflicted about the situation, because on paper, yes, you review your own experience, you don't assume that the game will be better in a hypothetical future, and it'd be nice if Bethesda got a wakeup call about bugs.
That said, there's two things about the situation that bug me greatly:
1) As others have said, it highlights how useless numbers are as summarizing thoughts. It was difficult enough as it is, but 4 feels like an arbitrary thing. Stapleton said he wanted it to be a red flag, but how do you decide which number to use as a red flag? Why not a 0? Why not also an article titled "Don't Buy Prey, It's Broken?" (that would surely reach a lot of eyes fast) I get the idea: that Prey has worth but it falls below recommendation, but trying to sum up "this is a great game, except for this one thing that might be fixed which may or may not effect you at all" with a single integer is a futile task.
2) The more annoying aspect is that Stapleton knew that Arkane was working on a patch to be out in days' time. The day before the review and beta patch both went live, IGN themselves published an article saying that Arkane had told them they were aiming within the week, with more details promised for the next day. The next day, Arkane did as promised with the beta patch. I've seen conflicting reports on the exact time frames involved (I've seen "within minutes of each other," that the patch came out slightly after, that the patch came out a short while before, which would certainly change the situation a lot, etc.). Arkane put out the news themselves on Twitter, and their president Raphael Colantonio has personally been spending the last few days tweeting to people affected by bugs to tell them about patches or reassure them that fixes are coming for their problems. IGN had to seemingly be informed that the beta patch was live some time afterward it had already come out, and Stapleton's response was basically (and this is the core thing I find somewhat off) that he's heard companies say patches are going to come soon that don't, so essentially... he assumed that Arkane was lying. The next day I saw him telling someone on Twitter that the patch still wasn't live for everyone several hours after it had come out (and Arkane had once again publicly announced that on their Twitter feed) at which point the other person informed him.
I don't doubt that Dan was coming from a position of utmost sincerity of taking bugs to task, but seemingly not paying attention to whether the fixes are out or not while essentially saying that you outright disregarded the developer's word on fixes is obviously an ironic way for it to play out. It has to be extremely awkward to make a gamble that the developer and publisher are being dishonest with the timeframe, only to discover that they were actually ahead of schedule and your grand stand for consumers now looks like tilting at windmills.
There's also a bit of irony that if someone had disregarded Dan's warning and bought the game on PC at the exact moment the review hit, it would have been nearly impossible for them to have reached the bug in question anyway before the patch hit unless they were speedrunning it.
That said, there's two things about the situation that bug me greatly:
1) As others have said, it highlights how useless numbers are as summarizing thoughts. It was difficult enough as it is, but 4 feels like an arbitrary thing. Stapleton said he wanted it to be a red flag, but how do you decide which number to use as a red flag? Why not a 0? Why not also an article titled "Don't Buy Prey, It's Broken?" (that would surely reach a lot of eyes fast) I get the idea: that Prey has worth but it falls below recommendation, but trying to sum up "this is a great game, except for this one thing that might be fixed which may or may not effect you at all" with a single integer is a futile task.
2) The more annoying aspect is that Stapleton knew that Arkane was working on a patch to be out in days' time. The day before the review and beta patch both went live, IGN themselves published an article saying that Arkane had told them they were aiming within the week, with more details promised for the next day. The next day, Arkane did as promised with the beta patch. I've seen conflicting reports on the exact time frames involved (I've seen "within minutes of each other," that the patch came out slightly after, that the patch came out a short while before, which would certainly change the situation a lot, etc.). Arkane put out the news themselves on Twitter, and their president Raphael Colantonio has personally been spending the last few days tweeting to people affected by bugs to tell them about patches or reassure them that fixes are coming for their problems. IGN had to seemingly be informed that the beta patch was live some time afterward it had already come out, and Stapleton's response was basically (and this is the core thing I find somewhat off) that he's heard companies say patches are going to come soon that don't, so essentially... he assumed that Arkane was lying. The next day I saw him telling someone on Twitter that the patch still wasn't live for everyone several hours after it had come out (and Arkane had once again publicly announced that on their Twitter feed) at which point the other person informed him.
I don't doubt that Dan was coming from a position of utmost sincerity of taking bugs to task, but seemingly not paying attention to whether the fixes are out or not while essentially saying that you outright disregarded the developer's word on fixes is obviously an ironic way for it to play out. It has to be extremely awkward to make a gamble that the developer and publisher are being dishonest with the timeframe, only to discover that they were actually ahead of schedule and your grand stand for consumers now looks like tilting at windmills.
There's also a bit of irony that if someone had disregarded Dan's warning and bought the game on PC at the exact moment the review hit, it would have been nearly impossible for them to have reached the bug in question anyway before the patch hit unless they were speedrunning it.