4 ms·
They knew what the policies were (one free patch, future ones are $$$) when they signed up with the platform. What it comes down to is the developers thinking:
by zdw 14y ago
They knew what the policies were (one free patch, future ones are $$$) when they signed up with the platform.
What it comes down to is the developers thinking:
"Who will gamers hate more? MS for the policy, or us for not releasing a patch?"
Especially if they say:
"We have fixed the problem… MS just wants their ransom for us to give it to you."
MS is then in the bind of making an exception, thus creating the expectation for future developers that the platform agreement is flexible and/or a joke.
There's no way to win this one. Both parties have somewhat dumb policies and because of the contract are deciding to play russian roulette with user's data.
- deleted 14y ago[deleted]
- Rhino55 14y agoThat's ridiculous. MSFT made some decisions without really A) thinking about or B) caring about the consequences. Their MO from day 1 is to screw everyone else and become fabulously wealthy in the process.
- klodolph 14y agoOkay, they knew what the policies were when they signed up. Big deal. It's not like the devs predicted that they'd botch a patch for some 1% or so of their users. The developer is just saying, "Look, the cost-benefit analysis just doesn't support making a new patch." That's honest. It doesn't sound like a policy to me (you'd have to so something more than once before I'd call it "policy"). The devs don't owe it to the affected users to pony up the cash to Microsoft. Devs don't have unlimited liability for lost save files. Microsoft's policy makes sense from a "Look, it costs money to make sure that your games don't crash on users' systems." So maybe Microsoft will change the policy so that a small enough patch goes through a less thorough review process. That's what happens when your policy has unintended consequences: you reevaluate it.
- 89a 14y agoMaybe test their patch properly before deploying it… Judging from their previous behaviour it's a horrendously sloppy "company".
- klodolph 14y agoIt sounds like a small percentage of users were affected by corrupted save data upon upgrading from the previous version. 100% test coverage is pure fantasy. You might as ask for a 100% complete specification of a product before you begin working on it. I'm actually just being devil's advocate here, but most bugs in games are not that important, and the companies that are a little sloppy can spend less money making mostly the same product.
- ekianjo 14y agoWhy exactly did the FEZ creators go for the Xbox Live instead of Steam or other alternatives, if they knew of these kind of issues in the first place? Plus, the developers are in the wrong here, as their software is malfunctional in the first place. Maybe they should have done more or better testing before releasing it for Microsoft certification. The Fez creators look like brats who do not want to accept responsibility for their mistakes, and blame Microsoft for not fixing their problems for free. Very poor PR skills.
- kineticflow 14y ago>“Fez is a console game, not a PC game,” he states, emphatically. “It’s made to be played with a controller, on a couch, on a Saturday morning. To me, that matters; that’s part of the medium.” I get so many comments shouting at me that I’m an idiot for not making a PC version. ‘You’d make so much more money! Can’t you see? Meatboy sold more on Steam!’ Good for them. But this matters more to me than sales or revenue. It’s a console game on a console. End of story.” From an interview with the developer, Phil Fish: http://www.nowgamer.com/features/950149/fez_interview_polytrons_phil_fish.html http://www.nowgamer.com/features/950149/fez_interview_polytr...
- drivebyacct2 14y agoIt's hard for me to question the guy that wrote the damn thing but I so incredibly profusely disagree with him. This is the casual game that I want to play on the plane, on my phone, etc. I sit down on my xbox to play a three-hour marathon of Halo once every 2 weeks. Other than that, the Xbox is a hassle.
- ekianjo 14y agoThis guy must live in a different planet or something. I play games on my PC just like on any console, with a controller (except for some FPS or RTS), and on a big monitor that has a better resolution than my TV anyway. And honestly, I can understand the idea of having the benefit of a couch and huge screen for some very spectacular games. Arcade games, Racing games, fighting games, etc. But Fez ? Come on. It could well be an iPad or a PC game it wouldn't really matter. Talk about shooting yourself in the foot.
- reginaldo 14y agoIMHO, that "policy" is kind of odd anyway. It creates an incentive for Microsoft to not do a very through review of the first patch, which is free, so they can get paid to do a review of the second one. When coining such things, one must be very aware of the incentives they create. Bad incentives will accumulate and potentialize and then come to haunt you...
- MichaelGG 14y agoAre you seriously suggesting that Microsoft intentionally wants to break games so they can hope to get patch review fees out of developers? Edit: According to [1], Fez had 76,000 downloads in the first half-month (April) alone. And in [2], Fez has 114,000 gamers on its leaderboards. So, where's the value in hurting conversions and pissing of a lot of folks, just for a chance to get a $40K fee? 1: http://www.gamasutra.com/view/news/171271/InDepth_Xbox_Live_Arcade_Sales_Analysis_April_2012.php http://www.gamasutra.com/view/news/171271/InDepth_Xbox_Live_... 2: http://www.gamasutra.com/view/news/174307/Xbox_Live_Arcade_sales_analysis_June_2012.php http://www.gamasutra.com/view/news/174307/Xbox_Live_Arcade_s...
- marshray 14y agoFirstly, I'll say that I've met and worked with several people from Microsoft and there's no doubt in my mind that they're putting 120% into their QA mission. I don't think any company in the world invests more into and does more heavy-duty patch release testing than Microsoft. That said, the general question "where's the value in hurting conversions and pissing of a lot of folks, just for a chance to get a $40K fee?" does have an answer. Consider a company where departments are fighting for budgets and managers are looking after their own neck far more than the common good of the organization (believe it or not, this happens sometimes). Organizations can easily devolve into a state of loving those business units that are perceived as "revenue centers" and hating those perceived as "cost centers". Microsoft used to be famous for derisively referring to teams (and even individuals) as "overhead". Obviously it's stupid and short-signted, but sometimes things like QA on patch releases for 3rd-party distributed software end up being several degrees removed from the revenue inflows, at least to the bean counters. In these situations, managers may be pressured into downsizing their quality efforts or trying to raise as much raw revenue as possible even if it really represents negative value on the whole. When the pressure comes down, the perverse incentives pop up. This "stack ranking" scheme sounds like a brilliant example. My guess is this policy comes from one or two^Hthree motivations: * Users don't like patching. * A desire to raise the cost of patching to hopefully encourage higher quality in the 1.0 releases. True or not, the perception among many in the industry is that Apple's app store requirements to jump through hoops to release versions has raised quality among those apps. * But the simplest explanation goes like this: "Why did you have to hire these extra staff at 40K each?" "Well, because we had more patch releases than last year." "Hmm...."
- jsz0 14y agoAnything that creates a bad user experience is ultimately bad for the platform so it's in everyone's best interest to get it fixed. In this case the update is probably 99.9% similar to the last paid update. That should really be a freebie. When you get into more significant changes that's a different discussion. If you get one free update when you publish the game the assumption seems to be that most games are going to need a patch so it's built in. It would probably be safe to assume that a patch is likely to introduce at least some small bugs and would also require a minor update later.