Traditional, pre-2006, beta tests were bug hunts in feature complete software. Then public beta tests became a thing that rapidly evolved into marketing for a finished game. Most public betas don’t see any bugs fixed on launch.
Generally, devs have felt very pressured when given multiple release date goals. By that I mean getting out a playable E3 demo, a “beta”, a demo, an early access for preorders…
It means if, say, the character has always had a clipping issue with their holster but it’s not a priority, the team can focus on important work/bugs first and their QA just kind of acknowledges the weird holster. But anytime they’re releasing, every detail like that has to be trimmed up for however many levels are coming out.
So yeah, I’m in favor of them avoiding any marketing betas if it helps them.
Is that not the purpose of a beta? That doesn’t seem like a good sign.
Traditional, pre-2006, beta tests were bug hunts in feature complete software. Then public beta tests became a thing that rapidly evolved into marketing for a finished game. Most public betas don’t see any bugs fixed on launch.
Not just marketing, they’re often also a load test for the networking infrastructure. Not much change to actual gameplay though.
Generally, devs have felt very pressured when given multiple release date goals. By that I mean getting out a playable E3 demo, a “beta”, a demo, an early access for preorders…
It means if, say, the character has always had a clipping issue with their holster but it’s not a priority, the team can focus on important work/bugs first and their QA just kind of acknowledges the weird holster. But anytime they’re releasing, every detail like that has to be trimmed up for however many levels are coming out.
So yeah, I’m in favor of them avoiding any marketing betas if it helps them.