Did not know this. Thanks.The bandwidth used for PSN patches is not charged either. Which is why a lot of devs go for the "400mb mandatory patch, 100kb install key DLC" route.
Did not know this. Thanks.The bandwidth used for PSN patches is not charged either. Which is why a lot of devs go for the "400mb mandatory patch, 100kb install key DLC" route.
Imagine how bad it would be without the patch certification. They'd probably upload the wrong build!trollol
The bandwidth used for PSN patches is not charged either. Which is why a lot of devs go for the "400mb mandatory patch, 100kb install key DLC" route.
Which is basically charging for patches?
It didn't occur to any of you that if the games stayed on PC, huge budgets wouldn't be needed? You know, as PC development is cheaper than console development?
Thanks for well written explanation.I think the point is that its not a flat $40,000 fee all the time as some think. It depends on what you are actually patching (patching bugs, or patching in significant content).
On XBLA you can patch and fix as many bugs as you want for free in the first patch. On PSN, if your bug fix patch is a few MB, you may end up paying a few dollars, not tens of thousands.
Both those approaches though encourage you to charge for DLC rather than giving it for free, as you need to recover those costs, as on XBLA you would have to pay, and on PSN you pay for the bandwidth and DLC is not small like a bug fix patch.
If you aren't 100% sure that your game is bullet-proof and won't be needing a patch, then DON'T RELEASE IT. Simple, no? Just keep polishing and fixing until it's 100% done and solid. Like Nintendo does.
If you're making your game while keeping in mind that it can be patched later on, YOU'RE DOING IT WRONG. Patches should not be the norm. They should be the ultimate last resort.
im more amazed nintendo's services are rated better.
Yes, because retail AAA games are spotless. Every game has bugs, game-breaking or otherwise. Can't escape that. Good to know you don't care about improving game experience and getting additional content.See Tim, there's one tiny big huge massive enormous point you seem to be missing:
For all intents and purposes, the game you're releasing should be 100% FINAL. You're not supposed to release an incomplete, buggy mess just to patch it later. I guess that would be too much work for you? You don't like working hard? Do you enjoy playing incomplete games? I don't.
You should take a clue from games on Nintendo consoles. Games on there don't need a gazillion patches. When they're released, they're final. Sure there's the occasionnal oddball with a game-breaking bug that doesn't get patched, and that's a shame, but even then that should require ONE patch to fix. ONE. And AFAIK the first patch is free. So don't go complaining.
I don't want consoles turning into a free-for-all wild west like it's the case on iOS for example. Games on there are almost purposely broken or incomplete on release because they know they can just patch away at will.
If you aren't 100% sure that your game is bullet-proof and won't be needing a patch, then DON'T RELEASE IT. Simple, no? Just keep polishing and fixing until it's 100% done and solid. Like Nintendo does.
If you're making your game while keeping in mind that it can be patched later on, YOU'RE DOING IT WRONG. Patches should not be the norm. They should be the ultimate last resort.
See Tim, there's one tiny big huge massive enormous point you seem to be missing:
For all intents and purposes, the game you're releasing should be 100% FINAL. You're not supposed to release an incomplete, buggy mess just to patch it later. I guess that would be too much work for you? You don't like working hard? Do you enjoy playing incomplete games? I don't.
You should take a clue from games on Nintendo consoles. Games on there don't need a gazillion patches. When they're released, they're final. Sure there's the occasionnal oddball with a game-breaking bug that doesn't get patched, and that's a shame, but even then that should require ONE patch to fix. ONE. And AFAIK the first patch is free. So don't go complaining.
I don't want consoles turning into a free-for-all wild west like it's the case on iOS for example. Games on there are almost purposely broken or incomplete on release because they know they can just patch away at will.
If you aren't 100% sure that your game is bullet-proof and won't be needing a patch, then DON'T RELEASE IT. Simple, no? Just keep polishing and fixing until it's 100% done and solid. Like Nintendo does.
If you're making your game with the assumption that it can be patched later on, YOU'RE DOING IT WRONG. Patches should not be the norm. They should be the ultimate last resort.
See Tim, there's one tiny big huge massive enormous point you seem to be missing:
For all intents and purposes, the game you're releasing should be 100% FINAL. You're not supposed to release an incomplete, buggy mess just to patch it later.
Just keep polishing and fixing until it's 100% done and solid. Like Nintendo does.
The biggest issues for Nintendo were the insane royalty structure (devs get paid only after certain sales threshholds) and the broken store interface. Nintendo themselves are usually pretty painless to work with by most accounts, though certification can be a bitch since they run it final product and not in progress for digital.It's not the service in itself, but the experience in dealing with them. So far most of the comments on working with Nintendo have been positive-ish, now when it comes to the actual DD service itself... yeah that chart would look different for sure.
See Tim, there's one tiny big huge massive enormous point you seem to be missing:
For all intents and purposes, the game you're releasing should be 100% FINAL. You're not supposed to release an incomplete, buggy mess just to patch it later. I guess that would be too much work for you? You don't like working hard? Do you enjoy playing incomplete games? I don't.
You should take a clue from games on Nintendo consoles. Games on there don't need a gazillion patches. When they're released, they're final. Sure there's the occasionnal oddball with a game-breaking bug that doesn't get patched, and that's a shame, but even then that should require ONE patch to fix. ONE. And AFAIK the first patch is free. So don't go complaining.
I don't want consoles turning into a free-for-all wild west like it's the case on iOS for example. Games on there are almost purposely broken or incomplete on release because they know they can just patch away at will.
If you aren't 100% sure that your game is bullet-proof and won't be needing a patch, then DON'T RELEASE IT. Simple, no? Just keep polishing and fixing until it's 100% done and solid. Like Nintendo does.
If you're making your game with the assumption that it can be patched later on, YOU'RE DOING IT WRONG. Patches should not be the norm. They should be the ultimate last resort.
See Tim, there's one tiny big huge massive enormous point you seem to be missing:
For all intents and purposes, the game you're releasing should be 100% FINAL. You're not supposed to release an incomplete, buggy mess just to patch it later. I guess that would be too much work for you? You don't like working hard? Do you enjoy playing incomplete games? I don't.
You should take a clue from games on Nintendo consoles. Games on there don't need a gazillion patches. When they're released, they're final. Sure there's the occasionnal oddball with a game-breaking bug that doesn't get patched, and that's a shame, but even then that should require ONE patch to fix. ONE. And AFAIK the first patch is free. So don't go complaining.
I don't want consoles turning into a free-for-all wild west like it's the case on iOS for example. Games on there are almost purposely broken or incomplete on release because they know they can just patch away at will.
If you aren't 100% sure that your game is bullet-proof and won't be needing a patch, then DON'T RELEASE IT. Simple, no? Just keep polishing and fixing until it's 100% done and solid. Like Nintendo does.
If you're making your game with the assumption that it can be patched later on, YOU'RE DOING IT WRONG. Patches should not be the norm. They should be the ultimate last resort.
Fun semi-related fact; Steam was originally built to an auto-patching service for Valve games. The store was only added after Valve realised they could use the same infrastructure to push whole games.
Yes, because retail AAA games are spotless. Every game has bugs, game-breaking or otherwise. Can't escape that. Good to know you don't care about improving game experience and getting additional content.
See Tim, there's one tiny big huge massive enormous point you seem to be missing:
For all intents and purposes, the game you're releasing should be 100% FINAL. You're not supposed to release an incomplete, buggy mess just to patch it later. I guess that would be too much work for you? You don't like working hard? Do you enjoy playing incomplete games? I don't.
You should take a clue from games on Nintendo consoles. Games on there don't need a gazillion patches. When they're released, they're final. Sure there's the occasionnal oddball with a game-breaking bug that doesn't get patched, and that's a shame, but even then that should require ONE patch to fix. ONE. And AFAIK the first patch is free. So don't go complaining.
I don't want consoles turning into a free-for-all wild west like it's the case on iOS for example. Games on there are almost purposely broken or incomplete on release because they know they can just patch away at will.
If you aren't 100% sure that your game is bullet-proof and won't be needing a patch, then DON'T RELEASE IT. Simple, no? Just keep polishing and fixing until it's 100% done and solid. Like Nintendo does.
If you're making your game with the assumption that it can be patched later on, YOU'RE DOING IT WRONG. Patches should not be the norm. They should be the ultimate last resort.
Nintendo games typically don't have any obvious bugs or defects (occassional oddball notwidthstanding (aka Skyward Sword)) and don't need patches.
See Tim, there's one tiny big huge massive enormous point you seem to be missing:
For all intents and purposes, the game you're releasing should be 100% FINAL. You're not supposed to release an incomplete, buggy mess just to patch it later. I guess that would be too much work for you? You don't like working hard? Do you enjoy playing incomplete games? I don't.
You should take a clue from games on Nintendo consoles. Games on there don't need a gazillion patches. When they're released, they're final. Sure there's the occasionnal oddball with a game-breaking bug that doesn't get patched, and that's a shame, but even then that should require ONE patch fix. ONE. And AFAIK the first patch is free. So don't go complaining.
I don't want consoles turning into a free-for-all wild west like it's the case on iOS for example. Games on there are almost purposely broken or incomplete on release because they know they can just patch away at will.
If you aren't 100% sure that your game is bullet-proof and won't be needing a patch, then DON'T RELEASE IT. Simple, no? Just keep polishing and fixing until it's 100% done and solid. Like Nintendo does.
Can't tell if this post is serious.
You think developers intentionally release broken games? Even the '100% polished Nintendo games' you mention have game-breaking bugs - see Skyward Sword as a very recent example. Twilight Princess and Metroid: Other M also had game-breaking bugs. Shit happens. It's better for everyone involved that if developers were able to release quick patches to prevent that stuff.
NOT having the ability to patch or charging a huge fee for patching a game is ridiculous.
name a company, in history, that meets your standards.
BZZT, wrong. Do I need to name 10 first party games in the current generation that required recalls, replacements, or had magic game-breaking bugs or bugs that exposed massive security holes in the consoles?
See, you're missing the point. I'm not talking about fixing bugs that unfortunately slipped through QA. I'm talking about companies that don't even try to polish their titles or that release willingly incomplete games because they know they can just patch it later on.
Those 10 first party games... How much do you bet that ONE single patch would've been required to fix those issues?
BZZT, wrong. Do I need to name 10 first party games in the current generation that required recalls, replacements, or had magic game-breaking bugs or bugs that exposed massive security holes in the consoles?
Only two I can think of this gen are Other M and Skyward Sword. Twilight Princess had one too, but it was pretty obscure and easy to avoid.i'd like to know which first party nintendo games had game breaking bugs, etc. i'm not sure if exposing security holes should enter the discussion as that wasn't really part of his point.
i'd like to know which first party nintendo games had game breaking bugs, etc. i'm not sure if exposing security holes should enter the discussion as that wasn't really part of his point.
As as a small aside, patches aren't just for fixing games; they can also be used to add features.See Tim, there's one tiny big huge massive enormous point you seem to be missing:
For all intents and purposes, the game you're releasing should be 100% FINAL. You're not supposed to release an incomplete, buggy mess just to patch it later. I guess that would be too much work for you? You don't like working hard? Do you enjoy playing incomplete games? I don't.
You should take a clue from games on Nintendo consoles. Games on there don't need a gazillion patches. When they're released, they're final. Sure there's the occasionnal oddball with a game-breaking bug that doesn't get patched, and that's a shame, but even then that should require ONE patch to fix. ONE. And AFAIK the first patch is free. So don't go complaining.
I don't want consoles turning into a free-for-all wild west like it's the case on iOS for example. Games on there are almost purposely broken or incomplete on release because they know they can just patch away at will.
If you aren't 100% sure that your game is bullet-proof and won't be needing a patch, then DON'T RELEASE IT. Simple, no? Just keep polishing and fixing until it's 100% done and solid. Like Nintendo does.
If you're making your game with the assumption that it can be patched later on, YOU'RE DOING IT WRONG. Patches should not be the norm. They should be the ultimate last resort.
Nintendo games typically don't have any obvious bugs or defects (occassional oddball notwidthstanding (aka Skyward Sword)) and don't need patches.
You have the exact same mentality as Tim: that games when they are released should not be the a completely whole, final and fully polished product.
I'm sorry but I've been a console gamer my whole life and I've come to expect that games I purchase are 100% definitive and complete. Mario Galaxy didn't need a patch to make it better: It was perfect on release.
And additionnal content? I hate that shit. Any game that gets DLC subsequently makes me feel like I'm playing an incomplete product, and that I'm forced to pay even more to get the complete package. Back in the day, everybody had the same complete experience. If they wanted to release "additionnal content", they made a fully-fledged sequel. I never felt like I was missing out on anything, because I was getting a whole, 100% final product.
Only two I can think of this gen are Other M and Skyward Sword. Twilight Princess had one too, but it was pretty obscure and easy to avoid.
Skyward Sword had such a bug if I remember correctly.
have they patched skyward sword?
Yes. You have to add a channel to patch it.have they patched skyward sword?
See, you're missing the point. I'm not talking about fixing bugs that unfortunately slipped through QA. I'm talking about companies that don't even try to polish their titles or that release willingly incomplete games because they know they can just patch it later on.
Those 10 first party games... How much do you bet that ONE single patch would've been required to fix those issues?
i'd like to know which first party nintendo games had game breaking bugs, etc. i'm not sure if exposing security holes should enter the discussion as that wasn't really part of his point.
And additionnal content? I hate that shit. Any game that gets DLC subsequently makes me feel like I'm playing an incomplete product, and that I'm forced to pay even more to get the complete package. Back in the day, everybody had the same complete experience. If they wanted to release "additionnal content", they made a fully-fledged sequel. I never felt like I was missing out on anything, because I was getting a whole, 100% final product.
Single player aspects in games don't usually have obvious bugs. It seems you are applying the issues more prevalent in multiplayer where a majority of activity is dynamic causing bugs to sprout more commonly, spontaneously, and unusually. Once you fix something, problems can arise.
Oh I don't mind patches that fix totally unforeseen defects that were unfortunately missed. But when you look at game releases these days, that's not what they're doing. Instead, they use patches to put in the stuff they didn't have time to fix before they hit their self-imposed release date. A game should need ONE patch to fix game-breakers. These days games that get upwards of 5 patches are common.
I see why they charge so much for patches. Every time you booted up you'd be greeted with a patch, if not. Plus greedy corps making profit, obviously.
But fuck that's a lot of money.
See Tim, there's one tiny big huge massive enormous point you seem to be missing:
For all intents and purposes, the game you're releasing should be 100% FINAL. You're not supposed to release an incomplete, buggy mess just to patch it later. I guess that would be too much work for you? You don't like working hard? Do you enjoy playing incomplete games? I don't.
You should take a clue from games on Nintendo consoles. Games on there don't need a gazillion patches. When they're released, they're final. Sure there's the occasionnal oddball with a game-breaking bug that doesn't get patched, and that's a shame, but even then that should require ONE patch to fix. ONE. And AFAIK the first patch is free. So don't go complaining.
I don't want consoles turning into a free-for-all wild west like it's the case on iOS for example. Games on there are almost purposely broken or incomplete on release because they know they can just patch away at will.
If you aren't 100% sure that your game is bullet-proof and won't be needing a patch, then DON'T RELEASE IT. Simple, no? Just keep polishing and fixing until it's 100% done and solid. Like Nintendo does.
If you're making your game with the assumption that it can be patched later on, YOU'RE DOING IT WRONG. Patches should not be the norm. They should be the ultimate last resort.
In a perfect world every game would be released on Steam, and Gabe would be the richest man on earth and own the most extensive collection of knives, swords, and cutlery the world has ever seen.
I wonder if AtomicShroom had any idea how much hate he would get for his opinion. I mean, his heart's in the right place as a consumer but seriously... What an uninformed mess of words that post was.
It's not too late, though! Thanks to the wonders of the "Edit" function, he can go back and patch his post into something more agreeable to the consumers of his text!
The iOS patching you're complaining about makes it so that many games get 20+ content updates for free. Team Fortress 2 has had, what, 400 patches so far? How many has WoW had?
Unplayable online due to endemic cheating which could have been patched out:
8. Tetris DS
9. Mario Kart Wii
(there are others but I named one per system to show that it affected both systems