2. Type your password into a text file, highlight it, and press CTRL+C to copy your password. (Note: If you try to copy your password directly from the password field, you'll only be copying asterisks! *****)
3. Start up D3 and switch it from Fullscreen Mode to Window Mode.
4. Type in your e-mail as if you're logging in. (assuming it's not already there)
5. Use "Do It Again" to begin recording a macro.
6. Click on the password field, press CTRL-V to paste in your password. Press ENTER. Wait for the Error 37 Dialogue to come up and press ENTER again.
7. Press SCROLL LOCK. This will end the macro recording. Give it a [Name].
8. In "Do It Again", go to Options>Repeat Task Settings for [Name]. Change the repetition times to 99999. You may have to add a wait timer in the field depending on what error we're getting right now (some errors take longer to pop up)
There's nobody running around. You guys are thinking that these errors are a problem that Blizzard is desperately trying to fix. They're not, they are planned errors.
"Stress Test" means just that. You have to stress the system before you can test how it responds under stress.
It's not that there are too many beta players and Blizzard doesn't have enough servers so they're getting hammered. On the contrary, Blizzard probably has 10 times as many servers as are needed for this beta, because they'll need that many when the game goes online in 3 weeks.
What's happening is that Blizzard is deliberately shutting down servers, letting fewer and fewer servers handle the load until queues slow down, errors appear, or something crashes. This is what "stress testing" is all about. It's not about "oh, let's see if our servers can handle the influx of beta testers". It's about "let's break our servers in a planned manner, then dig through logs to understand the different modes of failure".
Of course, this means a !@#$ty experience for the beta testers, but that's how stress tests work.
This test is helping to remind people how much Online Only sucks. I would rather a less secure game that I can play whenever (obviously didn't hurt D2 from being massively popular).
Update: (11:50 pm EDT) We're in the process of bringing down the beta service for a brief time and will be bringing it back up with gradually increasing concurrency caps. When attempting to log in you may see a variety of errors, and we recommend you keep trying. Thank you for your patience and continued help during this stress test.(Source)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
PANIC TIME!!
https://twitter.com/#!/Bashiok/statuses/193804596966207488
at least diablo 3 is offering some kind of challenge
There's nobody running around. You guys are thinking that these errors are a problem that Blizzard is desperately trying to fix. They're not, they are planned errors.
"Stress Test" means just that. You have to stress the system before you can test how it responds under stress.
It's not that there are too many beta players and Blizzard doesn't have enough servers so they're getting hammered. On the contrary, Blizzard probably has 10 times as many servers as are needed for this beta, because they'll need that many when the game goes online in 3 weeks.
What's happening is that Blizzard is deliberately shutting down servers, letting fewer and fewer servers handle the load until queues slow down, errors appear, or something crashes. This is what "stress testing" is all about. It's not about "oh, let's see if our servers can handle the influx of beta testers". It's about "let's break our servers in a planned manner, then dig through logs to understand the different modes of failure".
Of course, this means a !@#$ty experience for the beta testers, but that's how stress tests work.
I bet I know your choice.