329
edits
Changes
ADVERTISEMENT
From Diablo Wiki
m
bunch of minor stuff
==Will there be a Diablo III beta test?==
It's has not been confirmed, but Blizzard has run large scale public beta tests for every one of their games thus far. It's hard to imagine that Diablo III won't follow that successful path.
All computer game beta tests are chiefly used to fix technical problems. Public beta testers have an enormously wide variety of computer systems, and ironing out all of the hardware and software issues keeps Blizzard's technical crew very busy. Numerous game bugs are fixed as well, as the influx of new players invariably find ways to break the game that the company's QA department didn't discover.
Beta tests are very useful to companies as they work to streamline the early player experience as well. Beta tests seldom include the entire game, but they always have the early portions of the game, including character creation and other opening content, since it's essential (especially for Blizzard games) that their games are immediately involving and enjoyable. This is one reason companies like to pull in a wide variety of testers; noobs and dedicated fans alike. Experienced players will skip past minor glitches or confusing .
How much actual game testing goes on in a beta test varies from title to title. RTS games like Starcraft 2 generally feature the entire game, but only the multiplayer portion. They can run for many months, as countless tweaks and changes are made to the unit stats as players find new ways to exploit units, and one race or another seems too powerful, or grows too weak as new techniques are developed.
RPGs sometimes include the entire game client, but are usually more limited. Diablo II's beta only included Act One, and only the character skills up to level 18. The D2 team knew they'd need to make changes and tweaks and balances to items and character skills and monsters post-release, but they knew players would need longer than they wanted the beta test to run to get deeply enough into the game to offer valuable input on overall game/item/spell balance. The D2 beta was chiefly used to test out the new Battle.net features, and to test the early aspects of D2 itself. They wanted to perfect the fun factor and , leveling speed and , early items and , skills and , monsters and quests. Larger game balance changes were made in post-release patches and were based on the input and play choices of hundreds of thousands of players, rather than just a few hundred beta testers.
Beta tests with valid beta keys required to play are referred to as closed or private betas. (Most games run truly private betas before they get to the closed public beta, in which only company employees and some of their family members participate.)
Open betas are often referred to as "stress tests," since the goal is not to test the game, but to test the game hosting software and hardware. The game client is usually about the size of a demo, but it can only be played online. Open betas are usually almost always freely available to anyone who wants to download them. Beta keys may or may not be required, but if they are they're made very widely available, in numbers that scale up as the test continues.
Diablo II ran such a stress test for several weeks after the closed beta test, since they needed to see how the Battle.net servers would hold up with tens of thousands of simultaneous connections. There's no telling if Diablo III will run such a test. World of Warcraft had both a stress test and an open beta to test its servers. Diablo III's Battle.net set up is going to be similar to Diablo II's, with just a few realms worldwide, and millions of players on each. Blizzard may therefore feel it 's necessary to run such a stress test for D3, though they've said nothing about that publicly. They might also run an open beta because it's good publicity for their title.
Possibly, but nothing is definite until Blizzard announces it. All previous Blizzard beta tests had public signups, but that changed with the World of Warcraft expansion, Wrath of the Lich King. There was no public beta signup for that game; a beta code was given to all of the 6000+ attendees at the 2008 Paris WWI show, and the hundreds more added through fansites and Blizzard's friends list.
It's expected that the 15,000 fans attending the 2008 BlizzCon convention will get a beta code for an upcoming Blizzard beta, but that's not for sure. (Those codes could be for Starcraft 2 rather than Diablo III.) If they do, that might be all Blizzard thinks they need to test Diablo III, once they add in friends and family and hundreds more gathered from fansite contests.
It's likely that Diablo III will have a public signup, but it's not for sure.
Many would-be testers like to stress (in hotly-debated forum posts) that they would be great testers since they play a ton, are very experienced gamers, etc. That may be true, but the mistake such players make is thinking beta tests are primarily about game balance. That's an aspect of such tests, but far from the only one. Blizzard wants a wide variety of testers: varied computer systems, varied locations, varied play experience, and varied game interest. They know rabid D3 fans will play endless hours, and probably find some bugs. They also know that such players will learn how to control the game very quickly, and will not be slowed by unclear help guides, cumbersome controls, and other such minor difficulties that can stymie new players.
Beta tests, especially those (like D2's) that do not include the entire game (like D2's) are largely about optimizing the early game experience. Seeing what players find helpful or confusing about character creation, early game quests, NPC interactions, using the interface, etc. And for that, total noobs are as or more useful than experienced players. In fact, since Blizzard usually distributes hundreds of beta slots to their fansites, and they know those slots will be distributed predominately to rabid fans, they might actually favor more newbie testers amongst those who sign up from their public website form.
==Are Previous Blizzard Testers Invited invited to Diablo III Beta Test?==
Only if you are already on the Blizzard's friends list. They do keep a list of good testers from past games, and add people to it when they reliably report numerous bugs, but the names on this list are kept private.
Aside from marrying a Blizzard employee or becoming one yourself, you could try attending BlizzCon or other such conventions, since they've been giving out cards good for future beta test slots at such events. Admins of popular fansites and employees of major gaming info sites usually get beta slots as well; sometimes they even have extras to give out to site regulars. There's no way to increase your odds of being chosen from the public sign up period though, since the criteria Blizzard uses to pick such people varies, and is largely random.
==When Will will Selected be Notified?==
This varies greatly. There's usually at least a month or two between sign up and the start of the test, and selected testers only find out when they get their beta key emails. Since these notifications are sent out in waves, some testers will necessarily find out long before others.
