343 seems to have pretty much finished up, excluding the last one or two campaign levels and one or two maps. Bungie was behind at this stage with Halo: Reach, and still managed a beta (which was super if you ask me, fixed a lot of annoying stuff, excluding the focus rifle which it broke). Now, 343 is trying to tell us they are working every second, but they should have our input. (Notice the absence of NEED in that sentence.) So I propose an idea:
REQUIREMENTS FOR HALO 4 BETA:
-Have at least 30 minutes of gameplay with any 343I related game (H3, HR, HCEA).
-Have a Halo Waypoint account in good standing, with at least 10 posts
-Post once per every day you play the HALO 4 Beta, in the Halo 4 forum, discussing gameplay mechanics.
-???
-Profit!
They’re not doing one. Sorry, mate.
There is definitely no time for a beta.
Why can’t people just accept that there will be NO beta.
> Why can’t people just accept that there will be NO beta.
Because people can’t get the idea of public betas through their skulls.
OP, why do you want a public beta? For community input? E3’s, RTX’s, and SDCC’s hands on demos did just that.
Other than that, there is NO REASON for a public beta, most people use it as a DEMO, and don’t pull the “But I want to help 343i find bugs in their game” because guess what, Halo 3’s beta, and Halo Reach’s beta are all old builds, they’re a month or two old builds from what Bungie was actually testing in house. And on top of that, 99% of what they can do in public betas, they can do in house, with less development time lose, less resources, and 100% better feed back, than hosting a public beta.
The only time a public beta is useful, is for MMOs, not FPS games like Halo.
A Beta would reference the game being far from complete.
The game is close to going gold and being produced. The best thing we can hope for is a demo to be produced when 343i is done.
now, if they had a Public Beta, then their servers would be saved, and everyone wouldn’t have to play Campaign.
but if there is no Public Beta, the servers will crash, very hard, thus forcing everyone to play Campaign until 343i gets their servers fixed the next day.
Well played, 343i. Well played.
No, no online Public Beta for you… it’s a waste of time.
Give it up already!
Battlefield 3 did a “beta” like 2 weeks before launch, lol
> now, if they had a Public Beta, then their servers would be saved, and everyone wouldn’t have to play Campaign.
>
> but if there is no Public Beta, the servers will crash, very hard, thus forcing everyone to play Campaign until 343i gets their servers fixed the next day.
>
> Well played, 343i. Well played.
Servers play very little part in Halo matchmaking. All gameplay is Host and Client based. Servers will only match us up and choose host. Nothing will crash.
> Battlefield 3 did a “beta” like 2 weeks before launch, lol
And that game actually NEEDED the beta, or need I remind you of the “Long necked, prone, floating weapon, soldier” glitch? So far, Halo 4, doesn’t need a public beta test.
> They’re not doing one. Sorry, mate.
> Battlefield 3 did a “beta” like 2 weeks before launch, lol
Battlefield 3’s Beta was to test the servers, not the actual gameplay. The build we played in the Beta was 4-5 months old by the time we played it.
> 343 seems to have pretty much finished up, excluding the last one or two campaign levels and one or two maps. <mark>Bungie was behind at this stage with Halo: Reach, and still managed a beta</mark> (which was super if you ask me, fixed a lot of annoying stuff, excluding the focus rifle which it broke). Now, 343 is trying to tell us they are working every second, but they should have our input. (Notice the absence of NEED in that sentence.) So I propose an idea:
>
> REQUIREMENTS FOR HALO 4 BETA:
> -Have at least 30 minutes of gameplay with any 343I related game (H3, HR, HCEA).
> -Have a Halo Waypoint account in good standing, with at least 10 posts
> -Post once per every day you play the HALO 4 Beta, in the Halo 4 forum, discussing gameplay mechanics.
> -???
> -Profit!
Did you consider that maybe Bungie was behind because they did a Beta.
The problem with betas is that 99% of all players view it simply as bragging rights of playing it early.
> > 343 seems to have pretty much finished up, excluding the last one or two campaign levels and one or two maps. <mark>Bungie was behind at this stage with Halo: Reach, and still managed a beta</mark> (which was super if you ask me, fixed a lot of annoying stuff, excluding the focus rifle which it broke). Now, 343 is trying to tell us they are working every second, but they should have our input. (Notice the absence of NEED in that sentence.) So I propose an idea:
> >
> > REQUIREMENTS FOR HALO 4 BETA:
> > -Have at least 30 minutes of gameplay with any 343I related game (H3, HR, HCEA).
> > -Have a Halo Waypoint account in good standing, with at least 10 posts
> > -Post once per every day you play the HALO 4 Beta, in the Halo 4 forum, discussing gameplay mechanics.
> > -???
> > -Profit!
>
> Did you consider that maybe Bungie was behind because they did a Beta.
Not to mention, Halo 4 has had a longer development cycle.
> There is definitely no time for a beta.
EA/Dice had a Beta for BF3 when it was just 4 weeks untill releas, but then again look at how that turned out.
> > There is definitely no time for a beta.
>
> EA/Dice had a Beta for BF3 when it was just 4 weeks untill releas, but then again look at how that turned out.
BF3’s beta was a disaster and actually hurt their sales.
> > There is definitely no time for a beta.
>
> EA/Dice had a Beta for BF3 when it was just 4 weeks untill releas, but then again look at how that turned out.
That “Beta” was basically an open demo. It was essentially advertising.