An experimental public beta test of a patch for Halo: The Master Chief Collection, which would have been the first of its kind on a console, has been cancelled.
Developers at 343 Industries initially believed that a controlled public test of a content update would give insight into what problems it would fix and what new potential errors it could bring up.
nice way to break the only worthwhile game in MS arsenal, 343i studio.
CANCELLED!... we cannot fix, months later and still have no clue
lower expectations for halo 5 lads, because 343i is a joke so far.
LiNk
icing on the cake
343 Industries concluded: "Ultimately, this plan will allow us to deliver the smoothest possible experience, and ensure that the next content update becomes available as soon as possible."
LOL what a mess, i guess they are saving this for e3
pre-order halo 5 NOW and get MCC update for free! meGAton
This is a no-no. This is THE franchise on xbox. This isn't just bad for fans of the game(myself being one), this is detrimental to the xbox branding. Microsoft should really bite the bullet on this one and fix it, or rerelease it and give it away for free to those who purchased it.
They've been working on the fix and it's huge so they decided it would just take longer if they did a public beta and instead opted to do it differently which gets the fix into our hands much faster.
They cancelled it because testing it like this would take far, far longer than making a regular patch (which they did not cancel mind you).
That said, it would appear they still don't have the issues of the game completely figured out so it's possible it'll still be awhile before it's fully fixed.
"But the team now says the beta would have further postponed the release of this long-awaited patch, and say that testing can be completed internally. It is hoped that this major content update, of which there is no release date yet, will remedy the game's major problems."
Update is still coming. It's just not going to be a beta.
Holy smokes, this is bullshi&. 343 & M$ should have NEVER announced they were doing this late beta then. They deserve a backlash from fans but probably will be just fine based on the amount of fanboy Damage Control to the max I see in threads like this. I get fanboyism, especially fanboys that don't even own a game or extreme brand fanboys, but as a consumer I don't like this one bit as I own this product and I've been adversely affected by the glitches in the Single Player and Multiplayer. Releasing this Halo MCC beta was going to cost more time and money...and they already got their money from selling the game. They have people posting how great it is even though it's glitchy. There must not be a big upside to spending anymore money on fixing this buggy game. That's why I gave them credit before, because I was surprised they were alloting resources to fix something they already made money on. Most pubs take the money and run. Let's be honest, it's February. If they ran into some bugs they can't tackle with this beta or other glitchy complications, the PR isn't going to tell the full story. What we do know is it's February. Let that sink in. The game released on November 11th, 2014 and now it's February 10th, 2015 and it's still broken. Honestly, how much money is M$ going to pour towards this broken release? How much? It can't go on forever.
I imagine M$ would prefer 343 drop Halo MCC on the back-burner as much as possible to allow 343 to work on Halo 5's issues. That's good for Halo 5, but that means Halo MCC customers are probably f***ed. The fanboys will tell us all to wait another year if possible, but let's be real.
Especially when these fixes end up breaking the Halo MCC game further and this happens:
Halo Master Chief Collection Update Inadvertently Adds More Bugs "We are aware that far too many are not seeing improvements."
Regarding the Halo MCC "Fix the game late" beta, I said before in other threads that I was glad 343 was fixing the game. I own the game and ran into some snags on the SP and MP front.
Even if it mean 343 were fixing the game with this nutty "3-4 months after launch release" beta instead of just abandoning the game altogether. Sure, 343 could have done a beta test BEFORE releasing the product. What a treat that would have been for the Halo brand and fans. However, 343 and M$ are sitting pretty judging from the amount of corporate apologists they have on message boards. I'm sure they are patting themselves on the back for releasing a known broken game early generating millions of $$$ and it's quite the site seeing people defend this incredibly pitiful move. 343 is a young studio and have tarnished their name and the Halo brand with this product. It's not like Halo is some new IP. Even worse is what I think greedy bastard sleaze bucket companies like EA, Activision, and Ubisoft will learn from this. They already suck and I can only imagine that the crappy, broken games we've seen before/last year are only the beginning.
With this move by 343 today to cancel the Halo MCC Beta, I take my previous opinion back that I am glad 343 were trying. I've lost a lot of faith in this developer and the brand. Halo 4 was disappointing, but this really has me questioning how badly I want Halo 5 this year. Maybe I should wait. At best, it will be as good as Halo 4, which didn't set the world on fire being the first AA main Halo (87/100 metascore) FPS game. On top of questionable choices in the Halo 4 SP, Halo 4's online community abandoned the game as well. All of Bungie's main Halo's were 90+ on meta. That was my first experience with a 343 Halo game. I wasn't thrilled, they clearly dropped the ball with their first major Halo....but they showed potential. Halo MCC was my second experience with 343. They simply aren't an impressive developer. This is not going well for fans or Halo. I do believe Halo 5 will be much like Halo 4 in that it won't be as broken, but I'm not sure I care as much about Halo as I did 5 years ago all thanks to 343 and Bungie's departure (Bungie themselves seem to suck now too imo, but I'll save that rant for a Destiny thread). Maybe Bungie was always just over praised and just a competent developer, but if that's true, 343 is below that Bungie standard, no if's about it. 343 are an imitating unknown comic opening act to Bungie's Richard Pryor.
For the uninitiated, my Halo MCC copy sits with my Halo 360 collection and I've been with Halo since it's was created/released on the first Xbox Nov 2001:
Hmm, I suppose the buck ultimately stops with 343 but MCC was outsourced so there's that. :P
"While 343 Industries designed the interfaces and online networking"
I mean, it seems they were in charge of the part that's been the least functional.
The collection was developed by 343 Industries in conjunction with Certain Affinity, Ruffian Games, Saber Interactive and Blur Studio. While 343 Industries designed the interfaces and online networking, Certain Affinity developed the multiplayer and Saber Interactive
Eh, they all were cogs in the wheel and I haven't a doubt had the whole thing been in house by 343 there wouldn't be these issues.
The collection was developed by 343 Industries in conjunction with Certain Affinity, Ruffian Games, Saber Interactive and Blur Studio. While 343 Industries designed the interfaces and online networking, Certain Affinity developed the multiplayer and Saber Interactive
Eh, they all were cogs in the wheel and I haven't a doubt had the whole thing been in house by 343 there wouldn't be these issues.
Exactly. The part that was up to 343i to design, is the one that is broken.
The collection was developed by 343 Industries in conjunction with Certain Affinity, Ruffian Games, Saber Interactive and Blur Studio. While 343 Industries designed the interfaces and online networking, Certain Affinity developed the multiplayer and Saber Interactive
Eh, they all were cogs in the wheel and I haven't a doubt had the whole thing been in house by 343 there wouldn't be these issues.
Exactly. The part that was up to 343i to design, is the one that is broken.
The collection was developed by 343 Industries in conjunction with Certain Affinity, Ruffian Games, Saber Interactive and Blur Studio. While 343 Industries designed the interfaces and online networking, Certain Affinity developed the multiplayer and Saber Interactive
Eh, they all were cogs in the wheel and I haven't a doubt had the whole thing been in house by 343 there wouldn't be these issues.
Exactly. The part that was up to 343i to design, is the one that is broken.
No, the saying too many cooks in the kitchen come to mind, the code and interface could have been fine and it's something the four other devs did that through the monkey wrench into the works. Suffice to say all the Halos including H4 didn't have these issues. Also, wika isn't really all that ya know. As I stated before, the buck stops with 343 and MCC shouldn't have made it out the door with such issues but I'll give 343 a little wiggle room because I'm just that kinda guy. :P
No, the saying too many cooks in the kitchen come to mind, the code and interface could have been fine and it's something the four other devs did that through the monkey wrench into the works. Suffice to say all the Halos including H4 didn't have these issues. Also, wika isn't really all that ya know. As I stated before, the buck stops with 343 and MCC shouldn't have made it out the door with such issues but I'll give 343 a little wiggle room because I'm just that kinda guy. :P
I'm not gonna argue over something that can't be proven, like other studios messing something up, but what we know is that 343i was in charge of the networking part of the MCC, and they messed up in the worst way possible.
And Wikipedia is the first one to pop up. Other websites have already reported on who did what on the MCC. It's not something that people are still speculating about.
No, the saying too many cooks in the kitchen come to mind, the code and interface could have been fine and it's something the four other devs did that through the monkey wrench into the works. Suffice to say all the Halos including H4 didn't have these issues. Also, wika isn't really all that ya know. As I stated before, the buck stops with 343 and MCC shouldn't have made it out the door with such issues but I'll give 343 a little wiggle room because I'm just that kinda guy. :P
I'm not gonna argue over something that can't be proven, like other studios messing something up, but what we know is that 343i was in charge of the networking part of the MCC, and they messed up in the worst way possible.
And Wikipedia is the first one to pop up. Other websites have already reported on who did what on the MCC. It's not something that people are still speculating about.
Precisely and all I've said it's feasible that having so many different parties involved sounds plausible to me as a contributing factor.
They have to do what is best and I respect them for that. I makes me feel like they love me personally sometimes. My green blood just got a littler greener today.
lower expectations for halo 5 lads, because 343i is a joke so far.
Funny how the game that they actually developed had a fully functional online. Also funny how the Halo 5 beta was fully functional minus a few hiccups to be expected from a beta.
Clearly theres a bigger issue with the MCC, could be something to do with so many different devs working on it that has caused complications. It certainly doesn't make 343 incompetent like you're trying to imply. Nice try.
Log in to comment