Halo Director Explains What Went Wrong With The Master Chief Collection

4.3
Halo Master Chief Collection has experienced some difficulties, to say the least, but a recent update of the collection from Halo’s franchise director Frank O’Connor attempted to explain what went wrong with the product and how they hoped to fix it.

For those who remember trying to take part in The Master Chief Collection in its previously unplayable state, you might be wondering what didn’t go wrong as opposed to what did. O’Connor acknowledged those concerns and more in the blog post while prefacing it by saying that he wasn’t here to make excuses, just to provide explanations.

“From a personal perspective, the MCC launch was one of my lowest ebbs, professionally,” O’Connor began. “Every angry mail I received, I took to heart. I felt like I had personally let our fans down. I have not spent a single day since the night the game fell down in matchmaking where I didn’t think about it.”


As for the matchmaking component of Halo – certainly the core part of the series – O’Connor explained that the matchmaking environment that was extremely unstable hadn’t been tested properly in a real-world environment. That factor combined with not getting to run tests at scales they hoped to reach created a turbulent matchmaking experience.

“So we genuinely didn’t know until the day it released, how bad the matchmaking in particular was going to get,” O’Connor said. “I’m not going to ignore the other bugs, they were real, and important, but the way the UI and matchmaking protocols interacted with each other exacerbated many of the smaller items and amplified a couple of them in unpredictable ways.”


Changes were made to the original games’ matchmaking, but that ended up messing with the multiplayer parts of each of the games. 343 Industries was able to fix it eventually, but by that point, many players had moved on.

To close out his post, O’Connor summed up his thoughts while bringing up the Xbox One X and the possibilities that are contained within the console.

“It may sound simplistic, but MCC was essentially six pretty different game engines strapped together and interlinked with highly complex and highly delicate new systems,” he said. “With Xbox One X on the horizon, it was obvious that we could simultaneously update the game to take advantage of the new hardware for folks that have it and use that as an opportunity to finally rearchitect and update some of the foundational issues and networking/matchmaking methods.”


Posted:
Last Updated:
Related Forum: Xbox Forum

Source: http://comicbook.com/gaming/2017/10/21/halo-the-master-chief-collection-what-went-wrong/

Comments

"Halo Director Explains What Went Wrong With The Master Chief Collection" :: Login/Create an Account :: 6 comments

If you would like to post a comment please signin to your account or register for an account.

xGSxCoachPosted:

Brandon Frank O'Connor has got to be the thickest **** on the face of the planet. First off:

Thick **** @ 343 "I have not spent a single day since the night the game fell down in matchmaking where I didnt think about it.


And that's why the game is still broken right? And that's why ever since Halo 5 came out there haven't been any type of support whether patches or devs on waypoint, right?

Thick **** @ 343 "So we genuinely didnt know until the day it released, how bad the matchmaking in particular was going to get"


That's why all the pre release tourneys were ALSO having these SAME issues on LAN, SHOWING that the game was broken fresh out of the box. You couldn't even invite anyone to a lobby on LAN, and when you could; the second the game started it would crash and throw everyone to dashboard. Please refer to T2's comment: http://i.imgur.com/h6aMHz9.jpg

And finally, somehow, 343 managed to **** up 6 Halo games that in which, only made 2 of them. I mean, they ported fresh out of the box H2V KNOWING all the issues that had at release.

This is just a PR stunt. Halo is dead. **** 343 and **** micro$oft


Nail on the head... Halo died back during 3. It should have never been f*ed with

MythPosted:

Frank O'Connor has got to be the thickest **** on the face of the planet. First off:

Thick **** @ 343 "I have not spent a single day since the night the game fell down in matchmaking where I didnt think about it.


And that's why the game is still broken right? And that's why ever since Halo 5 came out there haven't been any type of support whether patches or devs on waypoint, right?

Thick **** @ 343 "So we genuinely didnt know until the day it released, how bad the matchmaking in particular was going to get"


That's why all the pre release tourneys were ALSO having these SAME issues on LAN, SHOWING that the game was broken fresh out of the box. You couldn't even invite anyone to a lobby on LAN, and when you could; the second the game started it would crash and throw everyone to dashboard. Please refer to T2's comment: http://i.imgur.com/h6aMHz9.jpg

And finally, somehow, 343 managed to **** up 6 Halo games that in which, only made 2 of them. I mean, they ported fresh out of the box H2V KNOWING all the issues that had at release.

This is just a PR stunt. Halo is dead. **** 343 and **** micro$oft

SR20DETPosted:

I liked the MCC, not so much for the multiplayer but for the singleplayer. I never really had a chance to play the older Halos, back in the day because I didn't own the game or even knew about it until Halo 3 which I was probably my favorite, spent so much time in forge mode with a bunch of my friends building bases and other stuff.

MissPosted:

Still a great game I enjoy playing to this day.

RyokoPosted:

Why did it take so long, this couldve easily been one of the best things on Xbone

SagePosted:

Im glad that they know that the game was a shit show on release. Also they shouldnt be worrying about xbox x release and just fix what they already have out.