Right, which means it’s not the full BfA client then because that’s a huge amount of refactoring to implement.
A lot of older guides from say more than a couple of months ago are filled with outdated or incorrect information for Classic. I notice it a lot in the Paladin guides, even the more recent ones. Just blatantly wrong things (e.g. saying to use a Reckoning build when the /sit macro stuff doesn’t work the way it did on private servers)
DX12 not being enabled does not mean it’s not the 8.x client. If you are saying it’s not the exact client. That is known. They are using a modified 8.x client.
Oh, and it looks like the multithreading capability is tied to DX12. So not having DX12 kills the multithreading.
1 Like
This is the correct answer.
That’s why I said it’s a mix between the Legion and BfA client. Some kind of branch/halfway step between them. As for the DX12 stuff, I don’t see them having left the code in the engine, hence why they probably started with mostly the Legion client and merged in a few pieces from the BfA engine, creating a hybrid. I suppose someone could decompile it all and see for sure, but that’s against the rules and such.
Getting back on topic though, I’m still pretty positive that they broke the API to break the census addon. If it were to prevent guild spam stuff, they would have broken the API ages ago and they still haven’t in retail. If it were to break the spy addon, it wouldn’t make a difference anyways because you can’t /who the opposite faction. This doesn’t really have an effect on LFG addons because those just use parsing and addon channels to communicate.