Comment on "The New Path for Bungie", 220 people, 17% of Bungie, laid off
Defaced@lemmy.world 4 months agoYep, OP clearly didn’t read the article and is banking on fake Internet points to fuel their comment. I’m glad management is getting the axe, they clearly have no fucking idea what they’re doing in Bungie.
irish_link@lemmy.world 4 months ago
I would generally agree with this statement but I think in this particular case it may be a bad thing. From what I understood of the article they are taking a portion of the Bungie dev team and spinning off to be a part of the Sony game devs. I have a feeling the manage team being taken out had been a big pushback on that.
Bungie wanted to leave Microsoft because they wanted to do new things and not just Halo. Unfortunately it turned out activation screwed them in terms of their development and mad then cut 70% of the D1 story with less than a year to release.
After all that they are eventually bought by Sony that now does almost the same thing MS was doing to them.
Don’t get me wrong, I am glad it’s more managers and corporate office than devs but I have a bad feeling that this is just the start of a bad turn of events for them.
MotoAsh@lemmy.world 4 months ago
I mean… regardless of how this goes, I think we can all agree this isn’t the start of a bad turn for them.
RightHandOfIkaros@lemmy.world 4 months ago
Not really. Microsoft did not absorb Bungie the way Sony is doing it. Bungie more or less remained untouched, like an independent studio under Microsoft. Microsoft didn’t mandate too much on them and that was part of their agreement with Microsoft. They had to do a certain amount of Halo games (I think it was 5) and in return Microsoft would more or less leave them alone. And then when the deal ended after Halo Reach, Bungie chose to not renew or sign a new deal with Microsoft. That’s pretty different from whatever is going on with Sony.
irish_link@lemmy.world 4 months ago
Good point. Sorry I wasn’t clear. I only meant that they couldn’t branch out and develop other games like they wanted to. Essentially I was making the same point that you are in terms of what they HAD to develop. MS it was Halo, Sony it’s destiny but in either place they did not have the option to make new IP. At least maybe not till now but that looks more like a forced dev.
I agree with your sentiment, though that Sony is pushing them more in house.
RightHandOfIkaros@lemmy.world 4 months ago
Microsoft did not restrict them such that they could not make a new IP or games other than Halo. Basically Microsoft didn’t really care what Bungie did as long as they released 5 Halo games and met their deadlines. Bungie chose not to make other games at that time because A) in the beginning, they loved Halo and wanted to keep making Halo, only tiring of it when they finished Halo 3 ODST, and B) they felt that their studio was big but not big enough at that point to handle making Halo games as good as they were while also making new IP at the same time. For example, Bungie were in the planning stages for Destiny while they were developing Halo 3 ODST, and began some prototyping for Destiny 1 while they were finishing up work on Halo Reach, as Destiny and Reach use the same game engine. But the team they formed to do that for all that time IIRC was around 50 people. For reference, Halo 1 had between 50-150 people working on it.
With Sony, its still too early to know the terms as former employees are likely still under NDA or such, but I would say it is highly likely that Sony did restrict their ability to work on other IP. The reasoning for this is that Bungie’s announcement says they’re losing a chunk of their employees so they can form a different internal Sony development studio (not a Bungie internal studio) to work on new IP. If Bungie was not restricted in a way that prevented them from working on new IP (like Microsoft which did not say no to new or other IP) then Bungie would have formed an internal studio to do this, not splitting off one to go under Sony.
Either way, Sony’s approach is very clearly more aggressive.