Login | Signup

So there won't be a Halo MCC patch beta after all

JonLester |  Feb. 10, 2015 at 15:06

Apparently a massive patch is headed to Halo: The Master Chief Collection, with the intention of fixing the still-inconsistent matchmaking once and for all.

"Progress on the CU continues, and we’ll work to provide an ETA once the final date is locked. As stated last week, our current focus and priority remains delivering the upcoming improvements to the matchmaking and party systems, but the team is also working on and prioritizing additional items beyond this, and I look forward to discussing these – a lot more – as we get closer to those updates."

343 originally suggested that they were going to hold a beta for this new content update in order to stress test it thoroughly, but apparently they no longer plan to do so.



"After further evaluation, the team has determined that that final testing for the content update will be completed internally, and we will not be conducting a beta test for the next CU. Also, it was determined that the additional time and work devoted to the beta would’ve actually postponed the public availability of the content update. Lastly, there were some added challenges surrounding the CU beta – including an extra series of required updates and rollbacks – that made us take a step back and reexamine the CU beta. 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."

Well there was no beta for Halo: The Master Chief Collection and that turned out so well, didn't it?

I'm not being entirely facetious there. I love the MCC's campaigns and multiplayer... but the latter only works some of the time.

With luck the new update will sort things out... but don't make a girl a promise, 343.

Latest Halo: The Master Chief Collection deal: http://www.dealspwn.com/xbox-bundle-alert-xbox-evolve-halo-master-chief-collection-29999-195062

Add a comment 1 comment
Late  Feb. 10, 2015 at 15:30

No complaints here. (And not just because I've not actually played the game since the week it came out, purely because I've been distracted by newer shinier things - I will get back to it soon.)

I love an open Beta. It allows us to play games we might not have, and form opinions for ourselves before a game comes out - rather than having to rely on third parties. (I sound like I'm trying to put games reviewers out of a job!)
If it's good then we might buy a game we originally weren't going to. If it's bad then we might avoid buying a game we were going to waste money on. And either way, we're having fun playing a triple-A title before it's actually out. It's great for gamers.
And it's clearly got a lot of value for publishers, too. They get to stress test their new game before its release. They get to identify and patch any glitches and bugs that turn up. And they get to generate hype and enthusiasm if their game is any good.
It's win-win with open Betas.

But for a game that's been out for months, I can't see any benefit. You'll end up with everyone who has the game (and hasn't given up on it) giving it a try. So where's the difference between calling it a patch and calling it a beta for a patch? You're doing yourself no favours and you're doing the punters no favours.

Just get it patched, get it released, and let people play it.

Beta or not, be sure to get it right this time, though. Patience is running thin (or completely dried up) for a lot of people, and the constant problems are surely damaging the brand.


Leave a Trackback from your own site

Email Address:

You don't need an account to comment. Just enter your email address. We'll keep it private.