The Master Chief Collection is definitely a black eye for us (Destiny)

by Korny , Dalton, Ga. US. Earth, Sol System, Thursday, May 14, 2015, 10:52 (3321 days ago) @ CruelLEGACEY

Yeah, I read that recently, which is why I said they're barely acknowledging it. At this point, calling the MCC a "black eye" nearly half a year after release is kind of putting it lightly with regards to goodwill with customers and community, and the rest of his post is more of the blatant lying that we're familiar with. They imply that in their test environment the game was good to go, when that's clearly not the case given the near-universal issues that plagued the customers (many which persist to this day).

I don't have specific details, and I couldn't share them even if I did, but everything I've heard backs up the notion that 343 genuinely believed they were shipping a working game when MCC launched. The fact that it was broken really did take them by complete surprise.

Which would have been one thing, but what they should have done is immediately acknowledge it, and issue a statement advising people not to buy the game, or at least keep them updated with a list of reported issues that they were going to address.
What they did was try their best to sweep it under the rug by changing the subject at every chance and by pantomiming concern (and trying to play it safe money-wise by delaying an already-finished game, Spartan Strike).... And the second the Halo 5 Beta got near, they shoved that down everyone's throats (sure didn't delay that, did they?).

Crap happens, especially when you cobble three different games together in a short time-frame. But when it happens, the decent thing to do is own up to it and do everything you can to fix it, not take months and months while trying to shift the focus away.

Which is concerning for a whole other reason. How is it possible in this day and age to get all the way up to release, thinking your game works perfectly, only to be hit by such a surprise?

It's impossible that they could look at a project worked on by a ton of different studios and think to themselves "nothing could go wrong!", and if anyone thought that, they need to get fired, because they clearly have competence issues. The game simply wasn't finished. "Working product" is NOT "finished product", and I find it extremely hard to believe that they didn't forsee something going wrong (heck, I wouldn't be surprised if they were working on excuses and damage control once the game hit the deadline.)

But again, the issue is communication and honesty, above all else.