I just hope they make it like Vanilla because I’m more concerned about that then sticking it to private server players and winning some petty victory.
"NOT A BUG" List from the Beta Forum
It does work. Esfand just did it on stream. Here’s the twitch clip id: BrightThankfulClipsmomBleedPurple
Melodarin-rexxar
#44
Translation: “Just to be clear, the nature of WoW Classic invokes different memories for players that played private servers because the admins didn’t have the real code and had to change it using their ‘best guess’ and got most of it wrong and made improvements of their own based on their preference.”
/sit macro was never a thing, it was a bug on those other places that was abused.
Arms is back for leveling, baby. Screw Fury crit proccing.
While yes I’d prefer them to not replicate bugs or dumb things that were obviously wrong decisions, it would cause a riot with the #NoChanges trolls. They want vanilla with all the flaws and warts? That’s what they’ll get.
Some of those “bugs” people reported is hilarious. These are the people they are letting into beta? “Quests don’t appear on the map” indeed 
Mini-firetree
(Mini)
#46
It may work like it did back then, is he spamming /sit /stand macros? If he his its just lag and him spamming, I doubt its procing every hit while he’s doing that
Maichan-zuljin
(Maichan)
#47
lol, seriously. “Creature respawn rates are much slower than in Battle for Azeroth.”
Did someone really stated BFA in his bug report?
Metrohaha-firetree
(Metrohaha)
#48
- Being critically struck while using /sit to sit does not cause abilities like Enrage, Blood Craze, and Reckoning to activate.
Wow, gg Paladins then huh?
That was working incorrectly on private this whole time?
Damn, that’s a pretty crushing blow for Prot Paladins who were using it to game massive heals and weapon procs.
Just kind of gets thrown out casually by Blizzard.
Uh oh.
Has Blizzard confirmed that the hitbox in the twitch clip of two taurens dueling is accurate? Or is that merely the result of having two very large hitboxes interacting with each other?
Has anyone tested Tauren hitbox things with smaller hitbox targets?
What I want to know if the value in that clip is accurate for all combat, or if that is just merely the result of two large hitboxes interacting with each other.
Abruek-turalyon
(Abruek)
#50
It never worked to begin with.
We want an authentic experience, don’t we?
If only that’s what we were getting.
Still, it’s good to hear, and some of the examples they gave makes “warts and all” slightly more believable. I just wish they were more consistent with their application of it.
It was fixed by then. It only took a few times of Ironforge being wiped out completely before Blizzard said “Yeah, that needs to stop.” Same with Kazzak and Stormwind.
Makes me sad.
Metrohaha-firetree
(Metrohaha)
#53
Do we? Ive been playing the way i described on my paladin for the better part of 5 years?
At some point, i have to wonder authentic to what? To the product that changed 10 times in a year and a half, or the product everyone has been playing for the last 5 plus years that has never changed intentionally and is the reason for this product coming about.
Obviously i would want blizzard to be true to their source but, i am getting more and more worried about imbalances that will likely arise from these small differences.
Lets hope its for the best, because a product like this really has a shelf life. If end game isn’t interesting or properly engaging, what will people be doing a year from now or more?
5 years on a private server doesn’t mean Blizzard should change it…
Just because you got used to a bad facsimile doesn’t mean we have to.
The whole point is to get the accurate game back. Things will be different.
Metrohaha-firetree
(Metrohaha)
#56
If you say so. I’m just saying, these 50/50 type changes that no one really knows if they were one way or another can cast a stone that will ripple into a monster effect.
Prot Paladins just got a major nerf with this, and they were already in a tenuous state.
Let’s hope more “NOT A BUGS” don’t come out that will significantly alter PVE.
The reason its an issue in the first place is because its all based on Nostalrius, who had a very scientific approach to creating their server.
If they found evidence of something, they altered it.
This was something that, presumably, they found evidence of it working a certain way, so they left it.
Now all of a sudden, Blizzard says they were wrong?
Can we see the proof of this? Because Nostalrius has all the proof on their github before it was taken down.
But that’s all I have to say about that for now.
A small issue, but one that can compound in a big way.
Authentic to the thing those private servers has been trying to emulate.
Blizzard does. They have the data.
From what? The holy grail private server baseline? Get out of here, I contribute to those projects. We should all be praying Classic is as different from that as possible.
That’s a major assumption. So your stance is “because it’s this way at Nost, they clearly found proof”, when there’s actually a higher chance that it’s that way because that was their best guess.
Lol @ “all of a sudden”. Use “suddenly”.
Seriously mate, go get Nosts server code and spin up your own server, sounds like you want that more than Classic.
Caelle-exodar
(Caelle)
#59
Amusing. So you don’t really want the real version but your private server version simply because its what you have become accustomed to. I wondered just how long it would take to see this stance start leeching out.
Blizzard has an up and running version of 1.12 they are using to compare too. This isn’t guess work or some private server guy deciding he liked something better and left it that way.
They’re not. Blizzard has a perfect 1.12 client and server reference. These changes are genuinely what it was. The only people who are saying it wasn’t are referencing a different game.
Private Server Prot Paladins should never have gotten that exploit in the first place. That’s the point.
I don’t “remember” private servers, so any changes they made are not my Vanilla.
Blizzard is not using any of Nostalrius code or settings.
Yes. Because they are.