They figured out how to import the data into the legion client and make the original data sets talk to the new configs. There is a video about it somewhere. So now you can log into classic with the 8.X client.
Most of the old models and textures for weapons and armor weren’t updated, unless they broke the player models. There’s actually quite a lot of Vanilla data (in terms of what’s in the 8.x client on your PC) still there.
Client, not servers.
you’re missing the point…
The “Client” is not the data inside the client.
“Vanilla” or “Classic” is the data set on both the Server side and Client side.
Classic and BFA share virtually zero data.
You cannot use a BFA proper client to log into a Classic server because the data for the client is 100% wrong.
None of the new graphics are included, none of the new sounds, menu, or any of that new jazz is in the Classic Client because the stuff that was “BFA” regarding Client side / server side data has been discarded and replaced by Classic Data.
Think about this like a cup of coffee…
You have a cup, it’s version 8.0…
You also have inside that cup some coffee and it’s also version 8.0
I dump that cup out and fill it with Coffee version 1.0
Now you have a coffee cup that’s 8.0 and coffee that’s 1.0.
That’s what this is… I know that’s a really really simple explanation, but that’s more or less what they did.
2 Likes
The executable has at least one file change in it. realmslist.conf
I assume that will be Beta servers, and I doubt indicative of launch servers. Their Beta servers are usually very different.
Omfg where are those guys that keep saying bla bla bla 7.3.5 bla bla bla legion client that i had discussed before???
![:sunglasses:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/sunglasses.png?v=6" ":sunglasses:")
1 Like
What? You were saying the client hasn’t run in years. It has. The old 1.12 client is still available.
Sure, but it hasn’t worked against a Blizzard server since 2006. Filled with bugs, exploits and some sort of sticky gunk it picked up somewhere over the years.
2 Likes
I understand perfectly.
The legion client is the shell, it offers modern protections in this case a “Thermal Mug” for a coffee analogy.
The vanilla client is a “Styrofoam Cup” in comparison.
The coffee is the data set and no you will not use a BFA client.
However, the data from BFA can still be poured into the thermal mug because it accepts new models, menus and graphics that were present in Legion.
Oh, great. And now It’s probably going to run like crap, and get hundreds of errors and crashes during normal gameplay.
2 Likes
Actually, to continue the metaphor, they’re removing the thermal lining of the BfA mug, and putting a slightly different lining in. Still accepts the right blend of coffee, but its neither a styrofoam cup or the original BfA mug.
(There is a separte WoW.exe for Classic that is not the Retail WoW.exe)
1 Like
Agreed, but that’s not what you said.
Actually in the metaphor it is a legion thermal mug and would only accept legion data as it is built to receive it in a certain configuration.
It has been stripped of its original coffee and replaced with 1.12 coffee.
Note the quotes.
It doesn’t count if its running against a Private Server. Blizzard isn’t patching it for exploits and security flaws and it hasn’t changed in 15 years.
Why not? You’re talking about the client.
Please try to understand the terms you’re using.
1 Like
True you could add stuff, but they have really been hard nose on that and said they’re not going there.
I don’t think adding all the new character models in the same way we add races would be too challenging…
The only hickup would be getting all the “Vanilla” gear and weapons to fit the modern character models and new races properly… Fitting the shoulders, helm, cloak, weapons, offhand, shields, and other “items” require manual fitment.
The “Skin” items like chest, most legs, etc… Stuff that stretches over the character model; these items are no brainer and automatic.
True. And at this point I’m going to give up trying to morph mug metaphors.
The Classic client will be (based on the build data we know now) a separate executable at 1.13.2 (or later), that will be updated with patches as per retail where appropriate, reusing retail folder data as the data permits, even though its in the classic folder.
I know I shouldn’t be like this, and I should be more mature about it, but I’m definitely going to dig up my posts where I challenged people to prove we’re using the 7.3.5 client.
1 Like
I know I used the 7.3.5 number as a foil for “We’re getting a 1.12 addon api”. Make sure to dredge up the ones where a number of us said we wouldn’t be surprised if the release updated to the 80100 interface.