Diablo 3 Community Manager Vaeflare hat sich in einem Beitrag im offiziellen Diablo 3 Forum zu den kommenden Änderungen am Zauberer, im speziellen am Skill Meteor, geäußert.

While the proc coefficient on Meteor and its runes is indeed being nerfed, this change really should be viewed within the full context of the patch. Patch 1.0.5 not only introduces changes to defensive bonuses and monster damage, but also the Monster Power system, and numerous crowd control improvements.

Combined with the Meteor’s lowered AP cost and decreased delay between cast and impact, these changes made it so Meteor was more appealing to everyone, which is fine. But they also made the skill extremely efficient (in fact: too efficient) to get Critical Mass procs and 100% CC uptime. Efficiency is good, but there needs to a balance. The skill is still very strong, so the tuning on its proc coefficients will hardly trivialize Meteor builds, and we anticipate that it will be brought back to roughly where it is currently in patch 1.0.4.

That said, skill synergy isn’t where we want it to be for wizards at the moment, and we’re looking at ways to improve that for the future. The sort of changes we’d like to do are more involved than simple numbers-tuning, though, and they weren’t able to make it in with this patch. But are we absolutely working on them.

Des Weiteren sind die Diablo 3 Entwickler mit dem Mönch wohl zufrieden, wie er aktuell ist. Es wird vielleicht Besserungen am Skill Fegender Tritt und Rasender Angriff geben

We feel that monks are in a decent place at the moment, and are a solid class in terms of power, but there are some things that we would like to address with the class. Namely: we would like to delve deeper into fulfilling the fantasy of what it means to be a monk.

Currently, monks spend a lot of their time applying an assortment of DPS buffs through the use of utility and survivability buttons. The bulk of monk damage comes from very passive gameplay, like healing yourself to get a damage buff, or applying Sweeping Winds and not looking at it again. We want to give players who enjoy the fantasy of being a blur of fists and feet a more active playstyle, and we’d love to play up some other fun mechanics as well.

For example, one possibility we’re considering is changing one of Dashing Strike’s runes to allow players to travel further with the skill so that it can serve as a mobility tool, but at the cost of imposing a cooldown. Another possibility we’re exploring is making Lashing Tail Kick feel more compelling by moving the knockback component to a rune, or changing a rune to remove the knockback and instead increase the damage more meaningfully. These types of changes are not minor tweaks, however. We want to make sure we take some time to make meaningful changes that improve the overall play experience for these sacred warriors.

Zu guter Letzt wird am Donnerstag US-amerikanischer Zeit ein neuer Patch auf den Testserver eingespielt, der Bugs wie den bekannten Fehler 12 beseitigen soll.

Quick update for everyone:

We believe we have a possible fix for players experiencing issues with the Retrieving Hero List step or getting an Error 12 while logging into the PTR. The problem itself is on the account’s side, so we’ll need to implement the fix with the next PTR build, which is currently scheduled to deploy this Thursday. Should we make any changes to our schedule for the PTR that would push the deploy past Thursday, I’ll be sure to provide an update in this thread.

In the meantime, we don’t need any further D3Debug.txt files. Thank you to everyone who did share your files, though; they were extremely helpful in troubleshooting this issue. 🙂