This post has been edited by a moderator. Please do not create alternate accounts to bypass forum bans. Alternate accounts will be permanently banned, and offending users will be subject to both temporary and permanent bans.
*Original post. Click at your own discretion.
They said they had teams test it but why is it still broken 
Well what do you expect from arrogent game developers.
Do you think 343 will learn from their mistake and make a Halo 5 beta?
If they don’t, well they’re screwed.
Actually, yes
Remember how on the first day, Halo 4 was super buggy? A beta would fix that.
Because even thought they havn’t the first clue what they are doing, there motto is “Trust us”
Yeah they should have listened and look what has happened.
It’s a common problem I am seeing with may developers lately. They opt out of a large public beta for an earlier release, then fix the problems that arise as the game progresses. Another noted example of this is Blizzard’s Diablo 3. The game was CRAP when it was released, again because of only in-house beta testing. Now, the game is very fun/playable and the console version looks even better than the PC version.
Halo5 NEEDS a public, or at least large invite, beta for multiplayer.
Go watch the GDC video and you’ll see why they never had a public beta.
> Halo5 NEEDS a public, or at least large invite, beta for multiplayer.
If by “large invite” meaning inviting large amounts of people into their studio to playtest their game, then that’s exactly what they did, and it wasn’t enough.
Though, part of the reason why 343 didn’t have a public beta was because they “didn’t have the time and resources to manage a beta”, they didn’t want to split up their current resources which were dedicated to working on the game.
Hopefully, they will make time for a Halo 5 public beta, because I’m sure no one wants a repeat of Halo 4’s beginnings.
> Go watch the GDC video and you’ll see why they never had a public beta.
Mind explaining anyway? I hope they didn’t change the reasons as to why because that would mean that they either lied back then or lied at GDC. (see above the quote for the “back then”)
They didn’t want it to interfere with halo 4’s development process. Still not a good excuse.
They had 4 years and couldn’t even get file browser to launch. If they had a problem getting a legit team together for halo 4, then maybe they should have waited.
Betas give people a good taste of what to expect. Plz, no closed selected betas next game 343.
Halo 4’s development cycle did not have time for them to create a seperate beta and get the feedback.
Is it 343’s fault, or -Yoink!-'s? We don’t know. Either way, I’d like to have a beta next time.
They thought their internal testing could somehow do as good as millions of people in a public beta. Even if the public beta would be months old, it doesn’t matter. Reach’s and 3’s public betas were months old and Bungie learned of plenty of bugs that could only be found by the masses and this made the games much more polished.
>
Maybe you should return your copy of Halo 4 if you say it is broken? Mine isn’t broken, it works just fine.
Also a Beta won’t be a magical save to fix all problems. Reach had a Beta and it still launched with a lot of problems and everyone hated it and everyone said Halo 3 was better, etc etc.
Inb4 “Halo: Reach’s beta fixed so many problems!”. The community rushed to the forums to whine, complain and moan up until Halo 4’s release date (and probably beyond) anyways.