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.
Judging from their previous behaviour it's a horrendously sloppy "company".
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.
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...
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_...
2: http://www.gamasutra.com/view/news/174307/Xbox_Live_Arcade_s...
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...."
I even understand the reason for the fee. It's to make sure developers give their maximum before submitting a game so they can avoid the need to patch and the fee in the first time. It creates an incentive for the developers, too... Hell, maybe it even costs more than $40000 for Microsoft to review the patches so they're being benevolent here and the whole thing is moot. I don't know, I don't work there.
My post was merely to point that, when one creates an incentive, there might be many sides to it, therefore one must be careful when creating incentives.
I'm an XBox owner who buys a lot of games (even arcade ones). I think it's the best Microsoft product I ever use (their awesome keyboards of circa 2001 being a close second). That XBox games on demand thing is just awesome.
Will try to be less succinct when commenting in the future.
MS has no incentive to review any patch at all beyond "it won't break stuff other than this developer's stuff". Unless I'm misunderstanding the review process code quality is the developers problem and if they release a bad patch that MS let out because it looked OK form their PoV (it applied cleanly to their test systems, and doesn't make the resulting app break any of the walled garden's rules) then that is not MS's fault.
Yes, it is a bad system. But they can't sign up for a bad system, give exclusivity to that bad system, then moan that they are stuck in a bad system and expect me to have sympathy for them. The way to try change the system as a developer is to refuse to take part until it is fixed - if the system loses users due to lack of content then MS may listen. The users are not going to fall for the reverse ransom that they are trying to pull - the average player is going to think "I paid you for the game, you need to fix it for me, I don't care what the costs are to you, that is a business problem for your accountants to sort out".
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.
From an interview with the developer, Phil Fish: http://www.nowgamer.com/features/950149/fez_interview_polytr...
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.
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.