This is a massive problem with the industry as a whole. The push it now, patch it later approach is terrible for the end user experience.
I bought MCC on launch and by the time it was fixed id more or less lost any interest in it.
This wouldnt be acceptable in any other industry and im not sure why its becoming the norm in this one to be honest.
I’m going to be completly honest, this is a bit embarrasing.
This game has barely any content overall and your most important gamemode is broken for almost one and a half month.
I really hope that a working hotfix happens within the next few days. This hurts the reputation of Halo as a Franchise each day more and more.
Big oof. That is a tricky one then. It was years ago when i worked QA, waiting around all day for a new build then having it fail was especially frustrating. Not something i miss to be honest. Getting Pizza for working late was great though!
NO ONE THAT WORKS AT 343 NOW ACTUALLY BUILT THE FRAMEWORK OF INFINITE.
They were all contractors that worked there for a few months over the course of hte last 6 years.
So now, the current staff is trying to figure out how to fix a broken game engine that they don’t even understand how it works because none of them actually worked on it.
I still suspect something else happening behind the scenes…
Maybe the build that was given to QA isn’t the same that we got
I just find it hard to believe at this point. Your point about the issues not being present on LAN makes sense on paper but again this all started December 8th… How did the December 8th update (that really just added Campaign) result in this? Bizarre.
Some of the 343i devs are acting sus is all I’m saying.
Let’s not make up false narratives or fake news or whatever the kids say these days.
QA has been using the same build, they’ve been using older builds to try process of elimination, and so much more than you can think of.
It absolutely is bizarre that the full release is what caused this and it’s something that QA is actively exploring and digging into. Have some faith that our teams and devs are trying. But this is exceptionally tricky and hard to pinpoint.
The build is passed off to cert (Microsofts xbox live) for final pass. This is just to ensure it doesn’t brick the console or open the console to vulnerability’s, it functions correctly with official accessories etc etc.
They wouldnt have the source to recompile a different executable afaik. I cant see any assets being behind this.
Code is hard, there will likely be thousands if not hundreds of thousands of lines that go into both the client and the server side of the software. A simple typo can fetch the whole thing crashing down like a house of cards.
I have no knowledge on how the clients interact with the server in infinites case, it could be a DNS resolver issue, it could even be something that is more prevalent on some ISP’s and not on others. It could be a typo.
Im not saying it doesnt suck… it does. We all want to play BTB. But its not a conspiracy, its not done out of maliciousness.
Well all I wanna say here is that if I’m proven right later on (343i firing a bad actor) I just want an apology
You guys make the process sound super complicated… Which means it would be more difficult to find out who was responsible for what and the specific cause of an issue.
I think everybody (especially people you work with) wants things to be more innocent, it is a hard pill to swallow that someone you may have known for years is doing wrong, but some things become suspicious over a long period of time.
Nah, sadly this is how 343i normally is. The MCC on release, and Halo 5, and now Infinite, have all released in subpar states.
The PC porting of MCC, and where most of the fixes came from that were transferred over to the broken console version, were primarily handled by the developer Splash Damage.
Actually that would be super easy. Files are normally tracked using software. Think of it like a giant library. One developer checks out a file (think of it like a book) and the library keeps a record of who has that file checked out, how long it was checked out for and usually a backup (just in case) and when it was checked back in.
Leaving your workstation unlocked while unattended is a MASSIVE NO NO. Your login is your library card.
Any deliberate malicious contributions would be tracked to the login that submitted them.
Hey snickerdoodle is there any way you could DM me? I’m not sure how to do that with my permissions and I have something I would like to talk to someone from the team about related to the game.
If you need help, you’ll want to submit a Halo Support ticket and if you have a game-specific question/issue that’s not support related, you can totally make a new topic!