DiabloFans

No word on the RMAH gold min cap fiasco?

I don't see any notifications in-game, and can't find the right thread on the forums... When does EU maintenance start?

Quote from Hextor

Can someone enlighten me what's this black weapon 'bug' they're all rambling about? Damage calculations are broken or what?

In short: yes.
A bit of the math behind it: http://www.teamliquid.net/forum/viewmessage.php?topic_id=394340 (click "show spoilers" to see the original thread).

Why doesn't Wyatt Cheng take over? Why do they need to bring in a new guy?

Well apart from their desperate need of new ideas...

Quote from Uldyssian

I don't like that people call Jay Wilson and the dev team names, that's just being a shitty person to another human being and produces no results, but they lost all their transparency after release and the mood between fans and developer feels fractured.

I like how you complain about people calling Jay Wilson Jay Wilson in this thread.

Quote from bruteMax

Jay Wilson got Jay Wilson'd?

They delayed PVP... and doubled it!

Quote from overneathe

Just the blog actually. Well.. none of the two have set dates, but they might already have an aim for PvP. When the blog comes out is irrelevant.

Just sad it's not going up earlier.

I don't see PVP coming out this year, so we might as well consider it delayed since JW was quite confident about releasing PVP this year back in May.

Quote from stromchin

Quote from Azriel

I don't know how people buying a large volume of a notably repetitive and unoriginal game is supposed to help the industry. Setting a shitty industry standard doesn't help anybody.

Hey, diablo isn't that bad.

I came here to bash Bobby Kotick, but then you two showed up <3

Quote from Valaran

I just wasn't aware that the news posts were actually performing such a level of calculations.

Such a level? It's just a simple division.

Quote from Valaran

the math that should be in the game, but isn't...

The math in game takes into account all stats except +damage to elites (demons, undead, etc) and +damage to skills. That gives us pretty good idea where our damage output is (except some known bugs with it). It could be better of course, for example, skill tooltips could easily show dps instead of the dps multiplicator, and tooptips could be more clear on skill mechanics. Game devs are funny people though, sometimes they want you to experiment, so in-game guides will never be totally clear.

But that's all the game can do for you. Tooltips can't predict how will you use skills with aoe or multiple hits. Azmodan has a big hitbox, so all bombs and granades will hit it. A small elite, like a skeleton will get only 1-2 hits from the same skills, thus dps on that elite will be around three times less. It makes no sense to take into account all uses of a skill... Many times devs can't even predict all uses of a skill. Discovering poverful mechanics like this is the fun part!

Quote from Valaran

(ie. specific-ability DPS ala D2)

I'm not aware of any in-game dps calculator in Diablo 2. Perhaps you mistake the damage range display for dps? It's nowhere near as convenient as the dps calculation Diablo 3 does.

Purgatory Device is Infernal Machine in English. New map? Maybe. Endless dungeon? Don't get your hopes high.

Quote from aljung

Quote from m4st0d0n

Of course, the clever choice is to swap skills as soon as you realize you can't beat the boss with you currents skills. You'll find an efficient, universal build quicker if you forgo the unnecessary wipes and skips. NV reset currently punishes being clever by removing the loot and MF bonus when you start to experiment and fine-tune your build, and it kills a major incentive of defeating a new boss.

True, but: Without NV-reset, people would just switch their brains off until their character dies to a monster-group and then respecc.

Switching skills while farming is not effective, it'd be a very bad and slow way of farming. NV reset simply prohibits that kind of gameplay, but even without that, most people would realize very soon that they need a constant build to farm effectively.

Quote from aljung

It isn't hard to know which skills are better against specific monster-types or amounts (single target vs. group, melee vs. ranged, burst vs. sustain dmg, ...), but it is hard to come up with a build that doesn't suck in any of these situations (now, apart from doing the completely brainless build-copying).

And that kind of experimenting is punished by the current NV reset system. People want to start with a copied cookie cutter build, instead of developing one for themselves, because with the current system they barely get any loot while experimenting. Of course not all people copy, and some people will always copy. But we're talking about what kind of gameplay is encouraged or discouraged by the game rules, and currently, experimenting is discouraged with the vastly inferior rewards.

It looks like the hardcore gamer who's willing to give thought to his gameplay is a dying breed indeed.

But regarding NV stack reset, let's ask the proper question: does it matter? Sure, NV stack reset locks you in a build for a session. But then again, if you want to farm efficiently, you're locked in a build, because you don't want to make breaks to mess with your talents (assuming the 1 min cd after skill swap stays). And if you died because you couldn't handle an elite using your current skillset, you don't farm efficiently. So NV stack reset doesn't matter when the game is on farm. You want to stick to a build anyways.

Where it actually matters is progress, and with the new and hard bosses/modes we'll be wiping a lot again. And what happens when you get to a boss/elite you can't kill it with your current skillset? You either skip it before you loose your stacks, or you wipe until you've lost your stacks, and only start changing skills after that because you don't want to loose your rewards (or if you can't skip it you just quit because of the loose-loose situation). Of course, the clever choice is to swap skills as soon as you realize you can't beat the boss with you currents skills. You'll find an efficient, universal build quicker if you forgo the unnecessary wipes and skips. NV reset currently punishes being clever by removing the loot and MF bonus when you start to experiment and fine-tune your build, and it kills a major incentive of defeating a new boss.

Now, just to be clear, I want NV reset to stay. It makes getting fast loot a bit harder (during progress period), and I'm fine with that, because I'm pro, and it's a big advantage to have the endgame inaccessible(or unfeasible) for most of the players. That makes my loot more expensive and I can make more money on RMAH (my only incentive to play this game). But the arguments above are very strong against NV reset on skill swap. I think it's clear that Blizzard has to remove it one day.

Feel free to discuss, but please read carefully what I just wrote and think before you post.

Quote from phatosen

Seriously man, if you want to quit the game because of a class/skill nerf, you're playing for the wrong reasons.

Oh no, I'm playing for the right reasons. Those reasons might not be the same as yours though. But I don't see the reason in your post. Think it over what you just said.

-----

I see this warning to fansites as another PR fail of Blizzard around Diablo 3. Most things are fine, 1.04 did good, people are playing, and then wham, Blizzard comes out of it's silence and breaks the calm with a "DON'T PANIC" warning. I see people panic just because of this warning, including myself, because historically, fixing the game resulted in nerfs to my class, builds, gear, etc.

I call bs. As a DH my class, my build, my playstyle or my performance was nerfed several times since May 15th. Blizzard may call it a bug fix, or sometimes outright lie and say it's a buff, what I get is a net nerf.

I don't expect it'll bee different this time either, whatever they say. I'll have to grind for different gear, find a different build, plan different farming routes. I'll have to climb the ladder of effectiveness again, with no apparent reason.

Sigh. No, actually I don't have to, but let me see the patch before I quit.