So I installed the “19.01. Update” on my Series X and tried to play BTB, 3 times in a row I get “There was a problem with dedicated servers. Please try again”.
Fixing BTB → so that was a lie!
I mean 343i are you kidding me?
Fix your game asap, with your stupid communication and amateurish behavior you just make a joke out of yourselves!
You know they literally dropped an update letting people know it didn’t work right? Right at the top of the page.
And 343i said they wanted to double the size of BTB in MCC eventually to be in line with Infinite’s larger BTB. I don’t see how that’s ever gonna happen since they obviously don’t know how to make BTB. They forgot about it when H5 launched ffs.
Also, can we just stop saying how every time someone is wrong or incorrect it is a lie? It’s cringe.
Thank you.
Another thing that’s cringe is a massive buyout from Microsoft occurring yet 343 seems to be dying in the water.
I’ve been banned 5 times.
Seems to have absolutely no impact on Halo… Odd point.
I’m just thinking that if 343 is in need of resources to make a working patch, wouldn’t their publisher be the one to throw them those resources?
Lack of resources, or maybe incompetence, uhh… What else could be the issue here?
What? You think a patch having unintentional consequences/results has anything to do with resources?
The hotfix didn’t need 500 people lol.
Throwing money at problems doesn’t solve them (most of the time) unfortunately. 343i aren’t in need of more money. They are in need of rightsizing if anything.
Resources as in money, devs, etc. Like this patch ‘went thru QA’ and ‘passed’ so I’m just here on the sidelines wondering what the hold up here is with a company this size.
Yes, however talking about your inabilities doesn’t make them any better. Also shipping an unfinished product on which you try making money through selling added services while it is not working, should be pointed out.
And all this BS that 343i is telling like “we are all in this together” “we’ve all dealt with this issue” is pure PR-BS. They released an unfinished product and take forever to fix it, while simultaneously making money of it. Shame on them and shame on this community for putting up with this crappy behavior of 343i
Im starting to wonder if 343 even know what QA is to be honest.
I said this somewhere else but I’ll say it here… I suspect sabotage at this point lol.
Its been screwed up since December 8th I believe, which common sense wise doesn’t add up because that update had almost no impact on MP in any way, now we go to today and the patch isn’t working right? It could be QA screwing up but I think there’s someone intentionally ruining the process.
Yeah I’m super confused lmao
I wish they were more transparent with the process. I mean they were making bank the first two months of the shop, toned it down a bit (thanks), BTB busted since launch, then today, the long awaited patch that will fix BTB and then this-
But we have a working cyber event-
New purchasable items-
Sabotage sounds like a valid reason at this point because I have no idea what they need to get the job done. Their first acknowledgement of BTB being broken and they said they didn’t know what was causing it, I’ve never seen a dev say that.
Idk, I come to the forum when I’m slow at work, Idk what a videogame production office looks like but I can’t see a team working 8 hours a day 5 days a week producing no results for 2 months minus vacation-
Time may vary I guess but surely the execs aren’t happy? Or maybe they are because of their money printer in the shop? Who knows
Well what they meant is that the underlying cause is hard to find, so it wasn’t a simple thing like adding in Slayer, seems to be more nuanced maybe involving a small line of code or something idk.
I mean to be fair most of the team are likely not doing anything for BTB… Most of the stuff they actually do is content related and not just bugfixes. They have huge deadlines to hit like Forge or Campaign Co-op and so on that are diverting lots of attention away from other issues.
I don’t like blaming QA frankly because they are not the ones responsible for anything in the first place.
So yes. This patch did go through QA and yet here we are.
“Sam, what happened then?”
Bugs are weird. We’ve had people looking into this and working on it and looking into this some more. This is definitely a priority for us.
But for whatever reason, when doing their many, many, many test passes, QA simply aren’t hitting the same issue. This could be for a whole slew of reasons and I can promise you they are still actively working on it and looking into SO MANY THINGS. (I’m literally on a call for this right now and listening in!)
No one wants this fixed more than us, I promise.
Hang tight. This isn’t a one and done thing. As ske7ch said in the banner message, we’ll share more when we have more and we’re going to keep working on this.
I used to work QA and although you are right they are not responsible for the actual bug fixing they are absolutely responsible for testing fixes and reproducing bugs.
This went through QA and from what information we have the QA team gave it the thumbs up. The fix then failed. This indicates that they were either unable to reproduce or didn’t fully test the fix itself (doubtful). The only reason I can see for it passing QA and still failing is that its a networking/latency issue that only presents itself over a wide area network. if they were in house, working from the office on a LAN the issue may not have presented itself… in that case, they should have pushed a test build out to insiders to test over the wider network.
This fail to fix really makes you wonder if the desync issue will ever be resolved as i would imagine that being a lot harder to nail down than clients failing to connect to the server.
The point is that they communicated the failure. They didn’t just drop it and send people on their way, they didn’t act like it was fixed and call it day. Be frustrated all you want that it’s still not working, but stop with the whining about “lies” and all that childish nonsense.
I could go on a massive tangent about the sheer embarrassment it is that in 2022 people still act like fixing these issues is easy, or the expectation that such large scale networking issues should be identified BEFORE the software gets in the hands of hundreds of thousands of active users, but the real issue is that base griping drowns out legitimate criticism.
Share your criticism, air your grievances, but do it constructively and do it accurately.
Haha! I’m not used to seeing devs hop into a thread, thanks for the response~
It just sucks cause my friends were all aboard the halo hype train, then after a month they dropped it, and I’m really trying to keep up with my dailies and what not but without the squad not having any motivation to come back to it- Well it’s rough out here on these streets.
Yeah, that’d be my larger concern. Really just assuming at this point that all the outsourcing for development likely means they’re going to have to spend a lot more time than is typical identifying the root causes of these issues.
That being said, as long as they keep working on it and fixes do make their way out I’m less angry about it than others. It’s not like they’re charging us for the game or any gameplay updates (yet), and despite people’s insistence on how great MCC is they often forget that it took years to function well.