I guess 343 quit working on MCC and is not going to update it ever again. Its been over a month and no update… Thanks.
But hoo nose.
“No update for month” does not translate into “stopped support FOREVER!”. I’m sure we’ll get at least a couple more tweeks before Halo 5 comes out but as that happens updates will become far less likely (or at least, far less frequent) since 343i will have to shift priority to supporting their new game (just as they should). So please calm down, sir.
Halo 5 needs all the love and attention it can get.
Plus MCC bombed with the community, I’m sure 343i just wants to (secretly) sweep it under the rug.
> 2533274870884222;3:
> " (just as they should).
Just as they should? No. The right thing to do is make up their continuous mistakes with this game by supporting it until it’s just as good as it was intended to be. Fans feel cheated and insulted at being given such a bad product.
343 just give us a broken game that for some people, still barely works, and now they are refusing to fix it. Seriously, they need to not release Halo 5 until the MCC is fixed for everyone.
It would seem that way. I mean, they say they’re going to fix it, but they also swore about dedicated servers.
343 stopped working on MCC a long time ago. Back in January they realized they were too incompetent to fix the game so starting with the March update, they’ve been hiring other studios to do the work for them. It’s not a surprise that the first update done by someone other than 343 was the first patch to actually improve the game.
> 2533274793734669;8:
> 343 stopped working on MCC a long time ago. Back in January they realized they were too incompetent to fix the game so starting with the March update, they’ve been hiring other studios to do the work for them. It’s not a surprise that the first update done by someone other than 343 was the first patch to actually improve the game.
How do you know this? Who was the company outside of 343 who patched the game?
> 2535441099340132;5:
> > 2533274870884222;3:
> > " (just as they should).
>
>
> Just as they should? No. The right thing to do is make up their continuous mistakes with this game by supporting it until it’s just as good as it was intended to be. Fans feel cheated and insulted at being given such a bad product.
343i have done a pretty decent job at improving net code stability and fixing most of the major issues the Collection had (it is still nowhere near perfect of course) but at this point the player population is so low that if they fixed everything they would have a perfectly working product nobody is playing. Focusing on Halo 5 and making sure it is the best Halo game it can be is far more important for the studio (as well as community) at this point.
> 2533274795233660;9:
> > 2533274793734669;8:
> > 343 stopped working on MCC a long time ago. Back in January they realized they were too incompetent to fix the game so starting with the March update, they’ve been hiring other studios to do the work for them. It’s not a surprise that the first update done by someone other than 343 was the first patch to actually improve the game.
>
>
> How do you know this? Who was the company outside of 343 who patched the game?
Splash damage did the march patch. I can’t remember who did the April patch. Not sure if it was splash damage or someone else but somewhere I saw with trustable evidence that it wasn’t 343. I’ll try to look for it later. I’ll admit I’m assuming they didn’t do the May update without any proof but if they already contacted out the work for the last two patches, why not continue to do so? And besides, the May update didn’t contain much fixes. It was mostly odst and remnant which 343 didn’t do.
> 2533274793734669;11:
> > 2533274795233660;9:
> > > 2533274793734669;8:
> > > 343 stopped working on MCC a long time ago. Back in January they realized they were too incompetent to fix the game so starting with the March update, they’ve been hiring other studios to do the work for them. It’s not a surprise that the first update done by someone other than 343 was the first patch to actually improve the game.
> >
> >
> > How do you know this? Who was the company outside of 343 who patched the game?
>
>
> Splash damage did the march patch. I can’t remember who did the April patch. Not sure if it was splash damage or someone else but somewhere I saw with trustable evidence that it wasn’t 343. I’ll try to look for it later. I’ll admit I’m assuming they didn’t do the May update without any proof but if they already contacted out the work for the last two patches, why not continue to do so? And besides, the May update didn’t contain much fixes. It was mostly odst and remnant which 343 didn’t do.
Why shouldn’t they contract the patch out to other companies when they contracted most of the game out to other companies in the first place? It would be a nightmare trying to patch the game by themselves. Having to pull all those resources back to the studio, understanding the code and policies/procedures of other companies. It’s easier just to get the guys who made the mess to clean up after themselves.
> 2533274870884222;10:
> > 2535441099340132;5:
> > > 2533274870884222;3:
> > > " (just as they should).
> >
> >
> > Just as they should? No. The right thing to do is make up their continuous mistakes with this game by supporting it until it’s just as good as it was intended to be. Fans feel cheated and insulted at being given such a bad product.
>
>
> 343i have done a pretty decent job at improving net code stability and fixing most of the major issues the Collection had (it is still nowhere near perfect of course) but at this point the player population is so low that if they fixed everything they would have a perfectly working product nobody is playing. Focusing on Halo 5 and making sure it is the best Halo game it can be is far more important for the studio (as well as community) at this point.
So because they took too long to fix their product they are now off the hook? That sounds like a serious lack of integrity.
> 2533274795233660;12:
> > 2533274793734669;11:
> > > 2533274795233660;9:
> > > > 2533274793734669;8:
> > > > 343 stopped working on MCC a long time ago. Back in January they realized they were too incompetent to fix the game so starting with the March update, they’ve been hiring other studios to do the work for them. It’s not a surprise that the first update done by someone other than 343 was the first patch to actually improve the game.
> > >
> > >
> > > How do you know this? Who was the company outside of 343 who patched the game?
> >
> >
> > Splash damage did the march patch. I can’t remember who did the April patch. Not sure if it was splash damage or someone else but somewhere I saw with trustable evidence that it wasn’t 343. I’ll try to look for it later. I’ll admit I’m assuming they didn’t do the May update without any proof but if they already contacted out the work for the last two patches, why not continue to do so? And besides, the May update didn’t contain much fixes. It was mostly odst and remnant which 343 didn’t do.
>
>
> Why shouldn’t they contract the patch out to other companies when they contracted most of the game out to other companies in the first place? It would be a nightmare trying to patch the game by themselves. Having to pull all those resources back to the studio, understanding the code and policies/procedures of other companies. It’s easier just to get the guys who made the mess to clean up after themselves.
You have a point with code ownership. Where I work that’s very important with us and the person who fixes the bug is always the person who created it. In an ideal world this would always happen as it increases productivity.
In this situation you’re wrong in three ways. First, the March patch dealt mostly with networking and matchmaking which was originally 343’s responsibility .Second, when you contact it work like this, it’s 343’s responsibility to maintain the code/product. You could say 343 is doing so by contacting out the work which is fine, but that brings us to the last point. The companies 343 is contacting the work out to had not previously worked on the game (I don’t remember the studio of the April update ATM but I do remember it was someone new like splash damage).
343 didn’t make mcc an outside company did, the only reason it says 343 and bungie on the cover is because they made halo 1234
It had an update today.
> 2533274890450463;15:
> 343 didn’t make mcc an outside company did, the only reason it says 343 and bungie on the cover is because they made halo 1234
Multiple companies did the porting, but 343 oversaw the whole thing, IIRC.
> 2535456533691021;16:
> It had an update today.
5 months later… And yet again it seems to have broken more than it fixed… I fear to think how long it will take them to fix the problems they created with this new “patch”.
The new update just came out. LOL! To be serious though, focus has been on Halo 5. Once that has successfully launched, they’ll start paying some attention to MCC again
The OP was made back in July, this is an old post folks. Take care to check the date of a thread before posting replies 