I hear you on that one.
1 Like
They will come out with another version of Classic called “Vanilla,” which will not have any of these nerfs and it will cost $5 a month.
But seriously, my guess is that they worry that it will be too hard, and people will just quit out of frustration. I think it’s fair to think that even the most seasoned of WoW players and the most hardcore ‘Vanilla’ players have become accustomed to ‘QoL’ features and easier fights and mechanics over the years (in many games and not just WoW), and there is probably a fear that some people will hate this experience.
5 Likes
They’ve already decided that and posted about it multiple times. if you think it’s up to Blizz, then you’ll accept their multiple posts explaining they’re going with 1.12 balance.
You should become a game designer if you unequivocally know what will be the most “fun for everyone.” You’d make the best games in the world!
Nice taking it out of context ![:grinning:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/grinning.png?v=6" ":grinning:")
You should be a reporter or a politician.
The MOST fun for everyone (there is an individual scale). ALSO refering to the community that actually asked for Vanilla - not average Joe.
Guess I have to spell it all out for you friend.
3 Likes
You do realize there’s virtually no chance that Blizzard is going to throw away their beta testing till this point and go back into the data to revert nerfs, right? Maybe there will be a Classic+ in the future and you can repost this thread.
I’m still not discussing the “how”, I’m only discussing the “what”.
This thread is not only relevant to Classic’s launch, it will stay relevant as long as Classic exists.
What is fair, and what is possible - is not for me to decide.
3 Likes
while not the ‘inital’ experience classic it does reflect the state of the game prior to the BC pre-patch. This is pretty much true to the base game blizzard had the client for (1.12) they don’t have the code, apparently, for the earlier builds and to port each patch over to the new infrastructure would be extremely time consuming and expensive even if they did. Their compromise was building 1.12 and releasing staggered content include itemization. I think this is about the best solution.
regarding a game lasting 3 months instead of 4 weeks, I don’t think they will be releasing all 6 phases in 4 weeks lol. They have not published any time table for phase releases but I suspect 2-4 months between phases so you looking at a 18-24 month release cycle just to open Naxx much less gear up and clear it. sure a handful of guilds will probably clear each phase in a couple days or maybe a week but the vast majority of the community won’t be clearing Naxx for at least 2 1/2 to 3 years from launch.
Thanks for your input Shorty.
blizzard had the client for (1.12) they don’t have the code, apparently, for the earlier builds
That might be the case, or not - we do not know. Hence why this thread is aimed towards the “what” not the “how”.
regarding a game lasting 3 months instead of 4 weeks, I don’t think they will be releasing all 6 phases in 4 weeks lol
This was just an example on my part taken totally out of context in terms of the presented timeline.
The point being, that the game will last longer, in any sense if the challenge is greater. The game will regardless offer us with a lesser challenge since its a re-release ![:slight_smile:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/slight_smile.png?v=6" ":slight_smile:")
1 Like
Where can I find your post regarding damage on SM Cath?
A major question I have about these people zerging low level instances while drastically underlevelled is if warriors are holding aggro using Battle Shout. That was a borderline exploit that definitely existed in 1.12, but most warriors didn’t know about it. By now I’ll bet they all do, and Blizz is going to have to fix/nerf it pretty quick I would think.
I don’t know if it existed in earlier patches. In 1.12 Battle Shout gave threat for everybody it affected, including pets, and it didn’t matter if the person already had Battle Shout. So a warrior could just stand there spamming Battle Shout and hold aggro on infinite mobs forever. But enough about how my casual guild oneshot Nefarian.
Classic isn’t a live game like Retail, it’s a museum. Stop asking for changes.
“Warts and all.” This game design is a wart. Suck it up and deal with it like the rest of us.
1 Like
“Suck it up?” What is this, boot camp? We’re talking about a game.
Battle Shout spam was not intended to work. It clearly was not intended that warriors should ignore all their intended threat generation abilities in favor of spamming a party buff over and over. They just didn’t get around to fixing it in the vanilla timeframe.
One of the things I dislike the most about current dungeons is that tanks can hold threat on infinite mobs forever. In vanilla, they were not intended to be able to do so. A good tank could hold two and a great tank 3. Past that, no, the healer would pull.
Battle Shout spam makes things worse than retail. At least in retail the tank’s AOE threat abilities have to actually hit the mobs. I’m pretty sure with Battle Shout spam the threat happens if the mob can see all the people affected by the BS.
3 Likes
It was Ion Hazzikostas who proved that it was impossible to down C’Thun (by looking at the required raid DPS and healing). He was also the GM of Elitist Jerks.
Ion Hazzikostas is now the Game Director of World of Warcraft.
It’s safe to say that we won’t see un-nerfed C’Thun this time around.
It’s safe to say we will have un-altered 1.12 stats on bosses.
The rest is just speculation from Pserver specials.
They can’t un-nerf it anyway if the data for the earlier versions doesn’t exist anymore. Not without doing exactly what pservers do and guesstimating everything, which is arguably worse than just giving us straight 1.12 stats, etc.
I’m saying even if they DID have that data, they wouldn’t put pre-nerf C’Thun back into the game.
And I’m not disagreeing.
I was speaking generally.
I agree. If that is the case, they definatly as an example have to look at the effect of battle shout in terms of tanking.
No they don’t.
Classic is a museum, not a live game. “Warts and all,” remember?
I can clarify my response above; Blizzard may look at BS and change it to an earlier state - if that solves the problem. If the change means something completely new, not ever known to Vanillas patch history, then I say leave it be.
If we were to implement new, unknown to Vanillas patch history, changes then we have entered the path of the “slippery slope” argument.