Basically, the reason I'm typing this is because ID@Xbox isn't "all bad" and I just felt it'd be fair to at least offer that perspective for a moment.
As for those tweets earlier tonight, I posted that because I genuinely had a good talk with Chris Charla. It wasn't awkward or upset, just congratulations with the announcements and some talk about the whole thing that went down. After that, we switched back to talking future plans and Nuclear Throne. It was super pleasant, especially considering we had just broken NDA and told them how that deal came to be.
If Microsoft had thrown any threats around, you'd be reading about those in the press right now. We really don't take lightly to legal nonsense like that. If we gave at all about Microsoft getting upset we would not have mentioned that story at all, but we don't, really. We care about letting the indie developer scene know what string are attached to which deal. If Sony ever turns sour, we'll let you know. If OUYA is being a pain, we'll let you know. We like transparency. Our whole involvement at ID@Xbox is trying to go through the gauntlet to let developers know what's what. So far, with the exception of the parity clause, our experiences have been quite positive.
Sony needs to be more aggressive. Simple as that.In retrospective, I think now I understand why Shahid was venting on Twitter shortly after the ID@XBox announcement. A good chunk of those indie games making an "exclusive console debut" on the PS4 are now getting delayed because of Microsoft's "indie friendly" program.
This is not friendly to indies, it is anti-competitive, and it is certainly not friendly to consumers either.
Why is Rami ok with this? This basically makes life harder on smaller indies that want to tier their releases on platforms if they want to release on Xbox as well. They have to hold off and develop for more platforms when they might want to focus on one.
EDIT: Please update the OP!
Why is Rami ok with this? This basically makes life harder on smaller indies that want to tier their releases on platforms if they want to release on Xbox as well. They have to hold off and develop for more platforms when they might want to focus on one.
Pardon me, but get off your fucking high horse. This is my career and my employees' careers. I'm not going to automatically say no to an extremely important section of my demographic because a company wants me to not give a timed exclusive to another company. It's the business. Not everything is going to be roses.I've read so much of this thread and now I'm just mad. Mad at stupid fucking Microsoft, mad at all the people who repeatedly misinterpret the OP and try to downplay it, mad at the indies that would actually stand for this and don't just say "NOPE." (Although it shouldn't be their responsibility.)
I need to abort this thread for my health.
As for those tweets earlier tonight, I posted that because I genuinely had a good talk with Chris Charla. It wasn't awkward or upset, just congratulations with the announcements and some talk about the whole thing that went down. After that, we switched back to talking future plans and Nuclear Throne. It was super pleasant, especially considering we had just semi-broken NDA (apparently Microsoft had already mentioned launch parity before, so I guess legally we're fine anyway) and told them how that deal came to be.
If Microsoft had thrown any threats around, you'd be reading about those in the press right now. We really don't take lightly to legal nonsense like that. If we gave at all about Microsoft getting upset we would not have mentioned that story at all, but we don't, really. We care about letting the indie developer scene know what string are attached to which deal. If Sony ever turns sour, we'll let you know. If OUYA is being a pain, we'll let you know. We like transparency. Our whole involvement at ID@Xbox is trying to go through the gauntlet to let developers know what's what. So far, with the exception of the parity clause, our experiences have been quite positive.
You got to hand Chris that compared to the situation a year ago it's sort of amazing that at this point we're talking specific points of improvement over 'well, Microsoft is anti-indie'. The thing is that Chris Charla genuinely cares about indie games. We've been quite happy with how things at ID@Xbox are going so far, we received our dev-kits last week and the team has been super responsive and pro-active. We obviously don't have the level of trust with them that we have with Sony (and it might be that we never will, because we really love Shuhei, Adam, Shahid, Nick and their teams at Sony) - but we do trust that the folks at the ID@Xbox program are trying to do the right thing here. We don't know what caused this particular clause in the contract, but we do believe (and this is based on nothing) that if they could get rid of it, they would.
We'll continue to argue with Microsoft to try and convince them to drop launch parity, because it'd be a shame if we could only release future titles through ID@Xbox through a contractual exception to be negotiated on a case-per-case basis. It would be stupid if games have to be delayed on one platform because of another. It is wrong for a platform to think that they have the position to affect, by default, how someone does business with another platform. If somehow, they can be convinced to drop that, that'd remove one of the really problematic aspects of the program.
In the meanwhile, we're also just really happy that Nuclear Throne is doing so well on Steam Early Access and working with the amazing team at Sony to get LUFTRAUSERS to Vita and PS3 and Nuclear Throne to PS4 and Vita. For Nuclear Throne, it's nice that we now have the time to develop the game properly for all platforms, including Xbox One.
In the end, it does seem that openness is always the best option, but instead of simply slamming ID@Xbox as a bad program for this one clause, we like to see if we can improve those sort of flaws from the inside. As you noticed we do feel we have the moral obligation to be open about our experiences if those affect others in any way. In the end, we do want to see ID@Xbox succeed. We want games on there to be successful. But we don't want them to be successful because of Microsoft, we want them to be successful for the indie scene. The more available development platforms that treat indie developers as a serious part of their business, the better. While there are some flaws left, ID@Xbox is a really, really big step in that direction.
Basically, the reason I'm typing this is because ID@Xbox isn't "all bad" and I just felt it'd be fair to at least offer that perspective for a moment.
That's all for fireside talking with grandpa Rami about indie games today, I guess. I'd love to spend some more time on GAF, but making games as a two-man team sort of confines me to one social medium (and that ended up being my Twitter) and my metric ton of e-mail. If anybody has any questions or so, feel free to throw them that way. We love this place and super-thank you for all the support over the years <3
what is that ps4 indie game thats cell shaded? i think on ue4? by tequila works? any chance that could be coming to x1?
what is that ps4 indie game thats cell shaded? i think on ue4? by tequila works? any chance that could be coming to x1?
Why should I, as a paying xbox owner, care?
what is that ps4 indie game thats cell shaded? i think on ue4? by tequila works? any chance that could be coming to x1?
It’s just not in Microsoft’s corporate DNA to be friendly and cooperative with smaller players. They always have to put in clauses to try to keep the upper hand and create problems and hassles for smaller developers.
Every level of executive management in the company is absolutely rotten.
Why should I, as a paying xbox owner, care?
Pretty sure Rime is actually a pitch funded by Sony from the get-go, so no.
Rime? It's a Sony published/owned game so no.
Funded and the IP is owned by Sony.
according to that last paragraph, he isn't.
Why should I, as a paying xbox owner, care?
Well to be fair to him if all of you collectively said no then they would have to change it. Just because you need to do it for your business does not make it the right path. Though i understand that you have to take care of yourself and with the way business is if you said no someone else would just take your slot but you don't need to be so defensive about your choice except you know that it is damaging to some people.Pardon me, but get off your fucking high horse. This is my career and my employees' careers. I'm not going to automatically say no to an extremely important section of my demographic because a company wants me to not give a timed exclusive to another company. It's the business. Not everything is going to be roses.
I'm not defending this action, but you implying I'm an asshole because I can't financially take a flag-waving personal stand is pissing me off.
Is Microsoft really gonna say "you can't come to Xbox One because you released on PS4 first."? This is really stupid.
Well to be fair to him if all of you collectively said no then they would have to change it. Just because you need to do it for your business does not make it the right path. Though i understand that you have to take care of yourself and with the way business is if you said no someone else would just take your slot but you don't need to be so defensive about your choice except you know that it is damaging to some people.
But it's also the company who recently killed off their always-online DRM plans (despite them being central to the console) and created the mostly great sounding ID@Xbox program, so maybe they can be reasoned with? If anything this clause seems like a weird, stubborn last vestige of the microsoft approach from back at the beginning of this year.
Not really. As people in this thread have pointed out, most indie developers only have the resources to develop for one or the other. If this policy forces people to pick Sony, so be it. The indies pick Sony. Whatever.Well to be fair to him if all of you collectively said no then they would have to change it. Just because you need to do it for your business does not make it the right path. Though i understand that you have to take care of yourself and with the way business is if you said no someone else would just take your slot but you don't need to be so defensive about your choice except you know that it is damaging to some people.
So what are they going to do when an indie dev can't wait and needs to release already and does so on PS4? Refuse to let them release out of spite? I'm sure they don't do this to published games. What happened to "games are games are games?"Yes, the idea is to make smaller indie developers halt the release of their games on the PS4, out of fear that they will miss out on potential Xbone sales.
Not really. As people in this thread have pointed out, most indie developers only have the resources to develop for one or the other. If this policy forces people to pick Sony, so be it. The indies pick Sony. Whatever.
I assume they can still publish their game under other pretenses, just not under the "ID@Xbox" initiative.So what are they going to do when an indie dev can't wait and needs to release already and does so on PS4? Refuse to let them release out of spite? I'm sure they don't do this to published games. What happened to "games are games are games?"
Not really. As people in this thread have pointed out, most indie developers only have the resources to develop for one or the other. If this policy forces people to pick Sony, so be it. The indies pick Sony. Whatever.
Is Microsoft really gonna say "you can't come to Xbox One because you released on PS4 first."? This is really stupid.
True, though a relatively rare case. Still, does the order of Xbox -> Sony as opposed to Sony -> Xbox actually hurt the developer in terms of sales?Or some indies who want to release on both consoles will instead release on the XBone first, because Sony will wait if they have to, whereas Microsoft won't.
So what are they going to do when an indie dev can't wait and needs to release already and does so on PS4? Refuse to let them release out of spite? I'm sure they don't do this to published games. What happened to "games are games are games?"
Well to be fair to him if all of you collectively said no then they would have to change it. Just because you need to do it for your business does not make it the right path. Though i understand that you have to take care of yourself and with the way business is if you said no someone else would just take your slot but you don't need to be so defensive about your choice except you know that it is damaging to some people.
That's not what i said most indies will not choose only Sony what they will do is be forced to prioritize the xbo version or go longer without income while they work on additional platforms. All this does is make life harder for smaller developers.Not really. As people in this thread have pointed out, most indie developers only have the resources to develop for one or the other. If this policy forces people to pick Sony, so be it. The indies pick Sony. Whatever.
Because it's a policy that does absolutely nothing to guarantee you get any games sooner or better than they would have been if devs were left to their own devices. In fact, it could result in the opposite.Why should I, as a paying xbox owner, care?
How many multi-console platform indie games have come out in the last few years?That's not what i said most indies will not choose only Sony what they will do is be forced to prioritize the xbo version or go longer without income while they work on additional platforms. All this does is make life harder for smaller developers.
I'm sorry, that's really not fair to put the burden on developers and expect some kind of microsoft boycott. This is not a business breaking clause, it's just shitty compared to what other platforms in the game industry are pretty much universally offering. Expecting one person/company to convince hundreds or thousands of other people to all go in on some kind of boycott during which some people who are barely making it (most devs) can't even pay themselves/their employees and some people lose their jobs is absurd.
Expecting every small developer to boycott as a group every time there's a policy they don't like is silly. For players and press who can see how this might negatively affect the industry, now is the time to speak out and let microsoft know that this kind of sucks. Devs have already spoken out despite the NDAs that usually keep stuff like this muffled. What else do you really want?
You shouldn't at all if you are selfish and closed minded....otherwise you should think it's a pretty shady clause, one that manages to affect the development or release of a product on a competitors platform....
True, though a relatively rare case. Still, does the order of Xbox -> Sony as opposed to Sony -> Xbox actually hurt the developer in terms of sales?
I think it DOES matter if you're only planning on releasing on one console (or perhaps doing a later port if sales are good). And in that case, I completely understand picking Sony.
Refusing to do business with a company will have more impact then just complaining about it but as you said small developers are plentiful and cutthroat so they will just lose their slot. I don't expect them to do anything like that because they have too much to lose however he should recognize that this is a shitty policy for some people and should not get upset when people suggest they don't care about other developers.I'm sorry, that's really not fair to put the burden on developers and expect some kind of microsoft boycott. This is not a business breaking clause, it's just shitty compared to what other platforms in the game industry are pretty much universally offering. Expecting one person/company to convince hundreds or thousands of other people to all go in on some kind of boycott during which some people who are barely making it (most devs) can't even pay themselves/their employees and some people lose their jobs is absurd.
Expecting every small developer to boycott as a group every time there's a policy they don't like is silly. For players and press who can see how this might negatively affect the industry, now is the time to speak out and let microsoft know that this kind of sucks. Devs have already spoken out despite the NDAs that usually keep stuff like this muffled. What else do you really want?
As with the system itself, I think this is a product of suits stepping in and trying to make a "better" product in their eyes. I highly doubt Chris Charla is happy about the clause but has to find a way to make it work.
I wonder if enough people made enough noise about a few really promising indie games that are getting left off the Xbox One because of this if they would ever consider changing it. I was under the impression that the parity at launch, which we heard about a while ago, only applied to content regardless if it had come out earlier on another console first. It is so dumb that it would apply to release date as well. I understand Microsoft wanting the Xbox One version of games to match content of all other versions when it's released, but forcing launch day parity is really dumb.
True, though a relatively rare case. Still, does the order of Xbox -> Sony as opposed to Sony -> Xbox actually hurt the developer in terms of sales?
I think it DOES matter if you're only planning on releasing on one console (or perhaps doing a later port if sales are good). And in that case, I completely understand picking Sony.
Once again, I just took umbrage over the fact that I was essentially being called an asshole for theoretically wanting to release on both systems and "obeying" this policy.
Eh...I wouldnt go that far. They are basically trying to ensure that they get something out of the deal for giving away dev tools + Unity. You could argue that getting games out of it is that something but we know there arent any gurantees there at all.Screw MS for trying to bully developers.
They are no better than Nintendo was back during the NES and SNES days.