DiabloFans

There was a study done in 2005 that shows the regular GRE is one of the worst predictors for grad-school success. MCAT, DAT, topic specific GRE and GPA are much better predictors for success.

Although, some schools just want you to take it and don't really care about the score.

F5 keys may rest. With the announcement along with the rapid-fire bug reporting from the beta, I wouldn't expect many beta invites anytime soon or Soon^tm.

I could be wrong but look at what we've seen:

• Beta not announced at conference call
• Small beta test group, NOT expanding
• Many more gameplay bugs than expected from a small beta pool and short content
• Revamping major gameplay elements after Beta "starts"
• Announcement of early 2012 release

IMO this game isn't ready for beta yet. I'm guessing Battle.net and server issues are to blame, but I can't rule out gameplay because of the overhauls on the DH and Wizard yesterday.

Here's hoping I'm wrong.

Quote from Eldius

Quote from Branmuffin

In the words of the great "Weird Al" Yankovic: "Everything you know is wrong."

While changing the DH's skills around, it seems they've changed much, much more.

Most WD and Wiz skills now use weapon damage instead of flat damage that increases with level.

Ladies and gentlemen, it's time to rebuild

That is just...lame. They should reverse that change. Casters shouldn't have to rely on weapon damage.

I agree, but at the same time I don't know what else it would scale with that would make sense.

So when it is based on weapon damage, does it count modifiers from other items? For example, if a belt increases attack damage, does that also mean the spell damage will increase?

Quote from Molsterr

Most of these bugs are under already known, and most likely were fixed for release. Nothing seems to be a problem other than a few things they are already fixing.

It's a small list for the small amount of content the beta covers, but there are 3 1/2 more acts, 2 more artisans, dozens of quests, monsters, skills and runes. The only reason we have the list we have is because of feedback from the beta. How many more bugs would there be if all gameplay was available?

I was under the impression that the beta was supposed to be a near finished product and that server stress was to be the focus of the beta.

After lurking around the official b.net forums, there are a lot more gameplay bugs/glitches than I would have expected. For gameplay only part of the way through act I there seems to be a lot of bugs. There are many mechanics, monsters, abilities, etc. that will never get the beta treatment before release.

Are they still internal testing the gameplay mechanics or are they focusing entirely on the beta?

Quote from "DieHardDiabloFan" »

Why the hell would someone wear a cape to battle?

Superman and Batman would but I don't think we'll be seeing them in Diablo 3.

I think there should be aesthetic customization. Capes are generally bad because the animation is difficult and never looks right. But I think that's something lacking from D2. If you wore a bone helm as a sorceress you looked funny, but there was nothing you could do to customize it so you invariably looked like an idiot. Some really good armors were purple, but I hate purple. Giving color variations or changing textures (tattoo's on skin, medals on armor) do not affect the 3d modeling or the animation.

Nothing is scarier than a tatted up Barbarian chick wearing pink.

I hope with the release of b.net 2.0 to the masses Diablo 2 will also get a major update. A lot of the limitations with content and such come from the old battle.net. I'm no computer programmer but I think that a major update in the online services could mean a major update for Diablo 2, without the limitations of the current battle.net.

Don't flame me for ignorance, maybe they have announced that the old battle.net will remain for legacy titles and they won't all go to b.net 2.0.

Actually I checked my battle.net account and the beta was up before I got the email. I got the email this morning but I downloaded the client last night.

SO CHECK YOUR BATTLE.NET

System specs just for fun (and I don't have a core i7)

OPERATING SYSTEM: WINDOWS 2.6.1.7600
CPU TYPE: INTEL(R) CORE(TM)2 QUAD CPU Q6600 @ 2.40GHZ
CPU SPEED (GHZ): 2.42
SYSTEM MEMORY (GB): 3.999
GRAPHICS CARD MODEL: NVIDIA GEFORCE 9800 GTX/9800 GTX
GRAPHICS CARD DRIVER: NVD3DUM.DLL
DESKTOP RESOLUTION: 1920X1080
HARD DISK SIZE (GB): 241.148
HARD DISK FREE SPACE (GB): 140.301

I'm in. And it's AWESOME!!! I've been playing too much diablo and not enough SC cause I'm getting wasted. Oh well, practice makes perfect. I will post pics but its 1:00 AM and me sleepy...

I thought the weapon swap was lame. I only used it end game when I could afford weapons that would buff. Otherwise I would use it to hold the weapons needed for quests, or a weapon or shield that I couldn't fit into the stash

Quote from "Nektu" »

What do you mean?

What do you mean??? A bunch of these have runes that don't exist (ie far or thur) Some of the names sound like they have made up by 4 year olds.

Plus where is the link to the source?

EDIT: I just looked up the source and these were posted last May by someone on battle.net. NOT LEGIT.

People are complaining??? Seriously?

Any other company would have stopped patching and balancing 3-5 years ago. Most companies do not put legacy teams on games that are 10 years old. Not only that but Blizzard has a sequel in the works and they are still improving D2.

Plus being disappointed about a patch that is still in public testing is lame. Its not even final yet.

Blizzard makes no money (maybe from that ad banner) from battle.net play and a new patch isn't attracting a whole lot of people to purchase the game. And those who do are only paying $20.

I guess what I'm saying is, if you want more content, wait for D3.

Realy?!? Is it wourth it?

Where is Halo? Isn't that the game that revolutionized console FPS games? Not one Halo game is represented.

"Sorry Master Chief, Wario kicked your ass."