Halo: MCC Multiplayer "1th" patch "fix" live!

A terrible game. Opinion.
A working game. Fact

Watch Dogs works too. Not gonna play that either just because it works. And in Destiny's case it's hard to fuck up matchmaking support when you dont even offer it for most of the modes in end-game.

Xbox Support person refused to give me a refund right away.

Keep saying "wait for 24 hour and if the issue persist, will process the refund".

sigh...
Same. The guy I talked to wanted to go through trouble-shooting steps for an hour. I told him to let me talk to a manager. He wouldn't. Eventually he just gave me the refund. And this was all after I gave him links to MS admitting there were issues.
 
Thats exactly whats happening to me now.
This night after patch I was able to find matches (played 6 to 7 matches, in different playlists). Now it just let me waiting in the queue till get that error message.

yeah its bullshit. i usually dont get mad about issues with video games, but im very busy wih work, school, and relationships, so i finally get minute to sit down and play some Halo this morning (east coast time) and the matchmaking is still broken. its a bit ridiculous that matchmaking is the major issue plaguing this game.
 
Networking and concurrency are an incredibly difficult beast.

It must be pretty difficult for them to make the first online, competitive multiplayer video game. If only they were employed by the same company that runs the Xbox Live team, the standardized online network of the one platform they developed for, I bet this game could work if they had access to talk to them.

Oh wait.
 
A terrible game. Opinion.
A working game. Fact

Still rather take a broken Halo game (that will be fixed eventually) than a functional Destiny.

Don't even get me started on the two "Expansions" that are $20 USD a piece (that sound like they were gutted from the base game to begin with)
 
Patch?

NegativeQuarterlyErmine.gif
 
shame-1.gif~c200


I bought a console for this.

I spent four hundred goddamn dollars.

I am seriously butthurt about this. Any and all hope I had for anything 343 does in the future is dead and buried.

Same boat here. I bought an Xbox for Halo CE, and Halo 2 and Xbox Live converted me over to consoles from being a PC online gamer. I logged hundreds upon hundreds of hours on Halo 2, I traveled for tournaments, I made real friends through that game. Friends I still talk to everyday, friends I've visited on the other side of the country, friends who I spent a weekend partying in Vegas with. Say what you will, but Halo has actually had a real impact on my life.

So when I saw an opportunity to relive some of that and play Halo 2 online again with a real community, I went out and bought an Xbox One solely for that reason. I didn't want an Xbox One, I had no plans on purchasing it, but there was no way in hell I was going to miss out on what was supposed to be the rebirth of my favorite franchise. What was supposed to be an opportunity to reignite the spark of Halo for a new generation, inspire the old fans, and bring in new ones.

And instead we got this... mess. Even if 343i manages to somehow fix all the game's bugs and issues within a month (which most certainly will not happen), the damage is already done. A game's community and population will never fully recover from such a horribly botched high-profile launch.

Call me melodramatic, but the whole thing actually makes me sad. It's really disappointing to see this happen to something I was so passionate about.
 
This is all I care about. Pissing me off it's not fixed yet. I better not have to replay those sections to unlock them either.

Yup, hardly any of my progress from last weekend's marathon actually saved to my console. It says I've played 1/15 missions in Halo 2 even though I completed the Heroic playlist -________-
 
shame-1.gif~c200


I bought a console for this.

I spent four hundred goddamn dollars.

I am seriously butthurt about this. Any and all hope I had for anything 343 does in the future is dead and buried.

I bought it for FH2, SO, and mainly this game. I spent 349 for the console. I don't particularly even like the console or it's UI. Since I bought it after November 1st, I'm allowed to return it for a full refund before January 15th (Christmas extends return periods at most stores in the US). I think I'm going to do that now and get a Wii U on Black Friday. I'll miss FH2, but I figure next year MS will have a new iteration of the console that isn't so huge, and will probably be even cheaper and I can play FH2 again then.
 
I feel like I need to say something about this...

A lot of people here ragging on 343i, saying that they are ruining halo, that they purposefully knew about the MP problem and just released the game anyways because they don't care, and so on...

Now ultimately the final responsibility does fall on their shoulders, BUT, I don't think you understand the problem here. They would not have released like they did if they knew the MP had issues like it does. I am sure they knew the game still had a bit of bugs in it that they didn't have time to Iron out, but as I believe they have already said, the MP issue is one that didn't show until the game was out in the wild.

This is very much the same situation as DriveClub where the developer was confident that the game would work, and then something just skrewed up at the launch.

Now i would agree that something like this is unacceptable to just brush off, and that people should be given some form of compensation. But spewing out hate post towards 343i is not the answer. The people that work there love Halo, and are probably some the the biggest fans of the series itself. They aren't perfect, but I assure you that they are trying their best to make fans happy, and deliver some of the best halo games to date.

Just because they skrewed up does not make them evil, and dos not mean that they are purposefully trying to mistreat us.

Sorry for going off on a rant, but I just felt like this needed be be said. It saddens me how people try to rag on the developers so much who are working their butt off to give their fans the best game possible.

Yeah, it's really on MS as the publisher more than 343i. The reason we have so many broken games this fall is because the publishers don't want to budge on their release windows. The games need more time to cook. Hopefully, they will begin to loosen up on that and get more creative with their release dates. It's OK to release a game between April and September.
 
Man oh man, I'd hate to be working at 343 right now. They have a surge of new players coming in about a week with Black Friday and there's no way they'll have things sorted by then.

Jeez :(
 
It's OK to release a game between April and September.

Woah woah woah... You want me to buy a Halo game outside of November? November and Halo... They go together...

Like red beans and rice.
Peanut butter and jelly.
Cigarettes and CVS pharmacies...

Oh wait...
 
Well, I don't have to restart my searches nearly as often. Unfortunately that's leading to a different kind of frustration. The uneven teams are making things absolutely miserable. In thirteen years of Halo I could probably count on two hands the number of games I've quit out of. Even when I was getting destroyed at blue on bg by the host on XBC I was happy to just be playing Halo online. I'm probably well beyond that mark now.

I know most people apparently can't even find a game, but has anyone complained about the playlist being absolutely terrible? In TS, every game of Halo 3 is either Narrows (who are these people voting for Narrows??) or High Ground, Halo 2 is Ivory Tower or Lockout, and no one really votes for CE but it seems to be Hang'em or Prisoner when they do. So many wonderful maps and I've only seen a handful even show up for a vote. You go into the playlist for Halo 2 and 3 and everyone just votes for slayer. I'm never going to get to play an objective game unless add separate objective and team slayer playlists for each game, which I doubt they'll ever do. It's a bummer.

CE feels much nicer after the patch though, so thanks for that, I guess. Too bad there's not a playlist to enjoy it in.
 
Yeah, it's really on MS as the publisher more than 343i. The reason we have so many broken games this fall is because the publishers don't want to budge on their release windows. The games need more time to cook. Hopefully, they will begin to loosen up on that and get more creative with their release dates. It's OK to release a game between April and September.
I agree, but I do understand in this case they didn't really have much wiggle room. Nov 11th was the 10 year anniversary of halo 2.
I think they should have outsourced more help to bug test it & fix problems.

I have no idea how big their actual team is, but the number of people who actually do the coding/bug fixing (that is, staff that aren't directors or artists or some such) is only going to be so big. And I assume some fixes are going to have to come from some of the teams that a lot of the game's code was outsourced to? I'm not sure how all that works. But I'm sure there's quite a bit of code and nowhere near the qualified staff on hand to fix everything quickly. Game development is a long process. The cake wasn't ready.

This is why open betas are a thing.

It's not like their only option was to send the game out there and pray it worked like it did in front of their 10 beta testers at the office. Simply not knowing your code was fundamentally broken in several major ways before stamping it GOLD and sending it out into stores for full MSRP is not a good excuse.

They're big boys and girls at 343. You don't need to apologize or make excuses for them. They know they fucked up and they're aware that a fuckup of this scale is going to have consequences. That's the hard reality of business.
Not every game needs to do a beta, but yeah, that probably would have been a good Idea here...
I'm not trying to make excuses for them. They messed up, and I feel like we should be compensated for it, but I think it makes no sense to continually bash 343 like this was all intentional. They are doing the best they can.
If anything, blame Microsoft's certification team which should have recognized that this game was a buggy as it was and gotten a lot of this fixed before launch, or just decided to push the date back a couple weeks.
 
Had a game in most playlists last night and it felt better. Then I was hit with a cannot connect to session error which has continued into today.

Shame. Real shame.
 
I bought it for FH2, SO, and mainly this game. I spent 349 for the console. I don't particularly even like the console or it's UI. Since I bought it after November 1st, I'm allowed to return it for a full refund before January 15th (Christmas extends return periods at most stores in the US). I think I'm going to do that now and get a Wii U on Black Friday. I'll miss FH2, but I figure next year MS will have a new iteration of the console that isn't so huge, and will probably be even cheaper and I can play FH2 again then.

2 games That are rumoured to come to pc, you should have had more patience.
 
Game's still broken. Gg 343. I was patient at first but it's messed up a few gaming nights just trying to get into a game with a friend to the point where we're both just tired and want to play something else.
 
I wonder if part of the issues last night was a combination of people trying to download the patch, people with the patch trying to get into games, and people who were still online pre-patch trying to get in games. Maybe the mix of people on different versions screwed something up? Regardless, it was really stupid of them to release the patch so late in the day after people were already online. Release that shit at noon eastern when most people are at school or are at work.

Anyways... All work on Halo 5, and the Halo 5 Beta, should be indefinitely delayed until Master Chief Collection is working properly. This in all likelihood isn't going to happen, but it is what should happen because splitting 343 up between bug fixing MCC and producing Halo 5 is only going to hurt both products.
 
Had a game in most playlists last night and it felt better. Then I was hit with a cannot connect to session error which has continued into today.

Shame. Real shame.

matchmaking sucks. i started playing last night and only found 4 matches, and now im trying today and keep getting a "connection failed" message.


For those who, just like me and these two here, are having the same problem, let me ask something.

Yesterday night / tonight, when playing the game after patch, did you have a "downloading latest data" issue that in fact never downloaded?
 
Well I'd like to know what testing they actually did on matchmaking. Because it flat-out doesn't work - it's not just a little broken.

I'm really curious how different their test environment is from the live environment. Because it seems like their shit goes through testing with flying colors and then hits the live servers and immediately crumbles. Makes me think their test environment isn't a proper reflection of the live XBL environment.
 
I'm really curious how different their test environment is from the live environment. Because it seems like their shit goes through testing with flying colors and then hits the live servers and immediately crumbles. Makes me think their test environment isn't a proper reflection of the live XBL environment.

+1

Any word from Frankie? 343? Microsoft?

I wouldn't expect them to have anything to say until they can offer a plan of action and a target date.
 
I'm really curious how different their test environment is from the live environment. Because it seems like their shit goes through testing with flying colors and then hits the live servers and immediately crumbles. Makes me think their test environment isn't a proper reflection of the live XBL environment.

That is a really good point.
 
I'm really curious how different their test environment is from the live environment. Because it seems like their shit goes through testing with flying colors and then hits the live servers and immediately crumbles. Makes me think their test environment isn't a proper reflection of the live XBL environment.

Yeah. Well either way, it's shocking from MS, especially for their flagship franchise and their servers. I would assume, this must be a massive fuck up with the coding or something to do with the sheer size of the content? All the maps and engines being utilized across all the games?

That's the only thing different here. That the game is just massive in size, and all the variance between each game.
 
troy-barnes.gif



So its still not working? My Halo 2 community is practically going to be at Halo 4 levels when this is done. Offer it with games with gold if thats what it takes, I don't even care that I payed for it, just bring back as much as the community as possible.
 
I had no idea an /r/Halo exists on Reddit till today.

I thought people were upset here... Nope. They're absolutely losing their minds in that subreddit.

I'm just glad I have other things to play in the mean time. I'd be really upset if I just bought the Xbox One and Halo MCC was the only game I had on it.
 
I'm really curious how different their test environment is from the live environment. Because it seems like their shit goes through testing with flying colors and then hits the live servers and immediately crumbles. Makes me think their test environment isn't a proper reflection of the live XBL environment.

Is it unreasonable to think that MS has access to some of the best testing & dev tools available in the world? It's hard for me to imagine they didn't have a means to test this game properly. I could believe they didn't have time, but not the means.

I just can't make sense of the process and steps that happened and led to the release of the game and it's current state.

EDIT: Maybe I am wrong... I don't know :(
 
I had no probs trying the matchmaking a couple of times just now but man the games itself seemed broken. Pretty laggy and the ground kept swallowing grenades? A dude drove a ghost and suddenly it was like he was getting sucked into the ground. It just exploded. Then it ended a round early.
 
Is it unreasonable to think that MS has access to some of the best testing & dev tools available in the world? It's hard for me to imagine they didn't have a means to test this game properly. I could believe they didn't have time, but not the means.

I just can't make sense of the process and steps that happened that and led to the release of the game and it's current state.

EDIT: Maybe I am wrong... I don't know :(

It's not unreasonable to think so. I'm just applying what little of my programming knowledge that is transferable to this situation. Piecing together what Frankie and 343 have said, it seems like the big issues didn't pop up until everything went live. From all of my programming experience when a similar situation happens its almost certainly a discrepancy between testing environments and production environments.
 
Top Bottom