WoW Classic Update

[Stoy]

WoW Classic Update

Hello Classic enthusiasts! We’ve been following the discussions about Classic closely here on the forums (and elsewhere) throughout the winter, and wanted to give you an update on a few things that the Classic development team has worked through since BlizzCon and the Classic demo.

The feedback we got from the demo was fantastic. Thank you to everyone who gave us so much feedback to work with, especially the community members who compiled lists of issues that people found with the demo. We’ve looked at everything that was reported, and want to share a few anecdotes with you so you can see how we’re tackling these issues.

One thing many players noticed was the incorrect health regeneration and the spell critical hit multiplier. Good catch! Going into the demo, we thought we’d fixed that and were surprised to see the issue crop up. Before BlizzCon, we specifically checked health and mana regeneration, and fixed the critical hit cases. We also did combat and regeneration tests to make sure we had those accurate.

It turns out that there was a discrepancy between how Classic was configured on our environment at the office (correct!) and the environment serving the demo to you (not correct…). Tracking that down taught us how to best check our environment configuration as we prepare it for launch.

Another issue players reported was that Warlock demon summoning was broken – lots of players said that you shouldn’t lose your current demon until the new one appears. We double-checked and in the original 1.12 WoW, and there, as soon as you started summoning a new demon, your existing demon disappeared. So the demo actually matched how the game played originally. There were a few other reports – such as “rare mobs do way less damage” and “Kobolds at Jangolode Mine run faster than walking speed when running away” – where we were able to confirm that the gameplay was the same in the demo as in the original 1.12 WoW.

It’s important to point out that there are some bugs we’re going to fix before launch, and there are some bugs that we don’t intend to address. As we mentioned in our BlizzCon presentation, some differences aren’t worth fixing, like differences in how the mail works. Nonetheless, we’ve fixed some fairly high-priority issues:

• Critical Strike rating: Each item now “Improves your chance to get a critical strike by X%.”
• Rogue Energy didn’t work right: it was both benefiting from melee haste and re-calculating more often than it was supposed to. Both issues were fixed.
• Slow Fall no longer applies to your jumps.
• You again get pushback when hit by ranged attacks and wands.
• Dodge, Parry, and Miss were all not happening often enough.

That’s not all we’ve done, of course, but we want to give you an idea of what we’re prioritizing: core game systems, combat, and content. We’ve spent time on other things such as user interface and making sure graphics “feel” like they used to, but our primary focus is on gameplay.

Again, we’re following all of your discussions and loving your enthusiasm – and we’re going to get more information for you posted here soon (not soon™).

Thank you, and get ready for a Classic Summer!

[Eleccybubb]

Good.

Keeping in critical bugs for "muh experience" was never going to happen.

Can't wait to play a real MMORPG again this summer.

[Cerilis]

Was the demon staying until cast complete only implemented in a later patch/expansion, then?

[Gamez]

“Real MMORPG again”

[shoegazing]

it’s important to point out that there are some bugs we’re going to fix before launch, and there are some bugs that we don’t intend to address.

spell batching ???????

[lonely zergling]

Was the demon staying until cast complete only implemented in a later patch/expansion, then?

Correct. Think it was implemented in TBC if I had to guess. You can see the vanilla behavior in drakedogs pvp videos when he summons his infernal btw.

[Kuntantee]

it’s important to point out that there are some bugs we’re going to fix before launch, and there are some bugs that we don’t intend to address.

This is an attempt to prepare player base to low production quality. Well, how about no?

[Nerovar]

some differences aren’t worth fixing

No. Changes.

[Esper]

Are we going to be able to download Decursive and cleanse the entire raid with a single button as the addon intelligently removes the debuffs?

[bloodykiller86]

Good.

Keeping in critical bugs for "muh experience" was never going to happen.

Can't wait to play a real MMORPG again this summer.

you mean an outdated and grindy MMO lol

- - - Updated - - -

lets just hope to wake up and finally cancel classic

[Schmeebs]

Are we going to be able to download Decursive and cleanse the entire raid with a single button as the addon intelligently removes the debuffs?

Pretty sure that was already broken in 1.12, but I can't remember which batch broke half the add-ons/macros

[The7]

They should disallow addons altogether, while they're at it. People want a slog and boring grind, they should go all the way.

[Lithostrotos]

you mean an outdated and grindy MMO lol

- - - Updated - - -

lets just hope to wake up and finally cancel classic

Genuine question, why do you want to shit on peoples' parade? It's just so petty. Let the people who got classic be happy, that it exists makes literally no difference to you. Classic isn't something I will bother with a lot either, but at least people get what they have been asking for a long time.

[~Valen~]

This is an attempt to prepare player base to low production quality. Well, how about no?

And no f... were given that day

Bye felicia.

[bloodykiller86]

Genuine question, why do you want to shit on peoples' parade? It's just so petty. Let the people who got classic be happy, that it exists makes literally no difference to you. Classic isn't something I will bother with a lot either, but at least people get what they have been asking for a long time.

Because you forget the other side of it. They've already started asking for possible added content like more raids. If they fork WoW, everything after classic becomes null and void and the story is reset.....i dont want that. id rather there be no classic. i played it, i never want to go back lol plus MMOs should never bring back the past

[Lithostrotos]

Because you forget the other side of it. They've already started asking for possible added content like more raids. If they fork WoW, everything after classic becomes null and void and the story is reset.....i dont want that. id rather there be no classic. i played it, i never want to go back lol plus MMOs should never bring back the past

If they do anything like that, I am 99% sure that the canon story will be standard WoW and if they add more content, it will have a different team from WoW and obviously it will be worth the cost for them to add it because it's profitable and new content wouldn't affect lore or development time. However I am doubtful they will add any new content because they've said they want to keep it as a museum or something.

[Zequill]

Reading hard, they are not fixing 1.12 bugs, they are fixing 1.13 to closely match 1.12. Most of the stuff they fixed are not even bugs, more little detail that was not like 1.12

[Kolvarg]

you mean an outdated and grindy MMO lol

- - - Updated - - -

lets just hope to wake up and finally cancel classic

It's okay to not like things. Let people enjoy what they want.

[Darknessvamp]

They should disallow addons altogether, while they're at it. People want a slog and boring grind, they should go all the way.

But addons have been around since Vanilla...

[jackofwind]

Pretty sure that was already broken in 1.12, but I can't remember which batch broke half the add-ons/macros

Nope, it still works in 1.12