Lol@Spencer saying that the game was fully tested and ready at launch and that problems were unexpected and related to the new Xbox Live.
Even throwing 343 a bone and saying that every one of the matchmaking problems were unexpected, the game menus themselves broke or didnt work every time you touched the game. I remember how fun it was having three menus overlay each other. And how about all those campaign issues? Me and seemingly a shitload of other people all got crashes on the first level of Halo 4. And apparently Halo 3's audio is often swapped backwards. That's just a couple from a long list across the games. Hell, dont even mess around with multiplayer, just put your factory disk into a disconnected Xbone and see how "ready" the game was.
Saying that the game was ready is just blatantly false and I dont see why they are so intent on lying about it. Even generic PR crap is better than lies. Or just tell me a leprechaun did it.
They lie about it because the alternative would leave them open to a lawsuit more than they already are. They expurgate the truth because they are not pressurised on the details in open, highly visible public spaces such as IGN or Edge or Game Informer; the interview published today is the
first and only time I've seen a journalist press an MS employee associated with the game. They've been very smart in playing this sleight of hand that one big network issue has caused all of the other 'smaller' issues with the game. That the new Xbox Live was the root of the games' online multiplayer and party compatibility woes and they didn't know this until it was being played in people's homes is questionable but plausible. That this made campaign levels crash or Halo 3's audio mixing to be scrambled or Halo 2's hit detection to cease functioning over a certain distance or CE's reticle to be pushed away from an enemy is not plausible.
Every game studio hires game testers and a testers work is commonly known to be gruelling in its tediousness and demand of repetition; be under no illusion that they weren't aware of practically every issue that the community has since uncovered. All one has to do is turn their Xbox One to offline mode and play the game from there to realise that it's a fundamentally faulty, poorly put together, bug ridden mess.
Here's something to ruminate on. 9th of October IGN publish the provisional playlist setup. Team Hardcore is listed as
"A collection of tournament-approved game types from Halo 2 and Halo 3. The Battle Rifle is your primary weapon. 4v4."
On the 8th of November, three days before the games' launch, Bravo blogs on Waypoint that
"The Team Hardcore playlist will launch only with Halo 2 Classic tournament-approved game types. Behind the scenes, were working to integrate Halo 3s custom map variant files into the playlist, and they arent quite ready just yet. As custom map layouts are extremely important to this playlist and community, well be adding the Halo 3 game types into the list when they can be fully integrated, tested, and brought in."
So they've known since
at least the 8th of November that Forge in Halo 3 does not work in The Master Chief Collection. On the 11th of March 2015, Team Ball is launched as a playlist. Halo 3's portion of the list features AR starts, as does the objective gametypes in the Halo 3 playlist, as does its portion in the Rumble Pit playlist. This is inexplicable because the other games all feature BR starts and so logic points to H3's forge being broken (reluctantly admitted to as non-functional by 343 in explaining H3's absence from the Snipers playlist) as the primary reason that Halo 3, the biggest selling Halo game of all time, has been, and remains, a very seriously compromised gameplay experience in the Master Chief Collection. Halo 3's team Hardcore variants still aren't quite ready
just yet. A third of a year since that statement was made, one wonders when 'just yet' will come.