After compiling the latest master version and downloading the latest client code, attempts to generate maps, dbc, vmaps, etc are unsuccessful due to conflicts between client version 7.3.0 vs Trinity master at 7.2.5. Is there a ballpark date on when the server will be updated to 7.3.0? Thank you.
Soon™.
Good evening to everyone,
Leave the reference to the client 7.2.5.24742
And then the Russian segment does not find the client the right version.
Of course it would be desirable to the client ruRU
sorry for my English
Please share the client wow 7.2.5.24742
@ewk Client can download from blizzard for free, i think, or take another version, for example WoD and open World of warcraft launcher.exe, it upgrade your client to latest version.
well, so the blizzard launcher will update my client to version 7.3.0
And accordingly I can not go to the test server that compiled from the source code TrinityCore
That’s why I’m asking for a version of the client that is suitable for testing.
and this is as written on gitHub master = 7.2.5.24742
@ewk Wait a few days, the version supported by the server will be 7.3.0, just wait… in the meantime update your client 
I understand that in the near future will make client support version 7.3.0
But just until the vacation wants to dig deeper
the client I have already downloaded 7.3.0
By the way, I have a client version 7.2.5.24330
Will I be able to change the client version of the database and log in to the server?
I think not, because maybe some opcodes was changed on 7.3.
@ewk the opcodes change usually when the first or second number in version change, if only change the thirth or build opcodes usually are intact.
Tray as you said, you’ll know right away if it works or not.
In your case you have 7.2.5 24330 the last version in 7.2.5 is build 24742, that only change build, opcodes will be exactly, just try, you dont lose anything.
Extractors? Maybe… Sniffer. Unknown!
Why don’t you update your server? Where is sniffer for 7.3.0? Your work was much faster for previous patches… What have done Blizzard in 7.3.0?
Maybe nobody wants to update it or just doesn’t have time 
But seriously if there really are issues with 7.3.0 it would be nice to know which kind of issues
It seems that the obfuscation that Blizzard was rumoured to bring in to prevent addons accessing unauthorized APIs have scrambled or perhaps encrypted the opcodes.
Or maybe something else.
However, if this is a major roadblock, then it should be opened up to the community and then perhaps a group effort might shed some light upon this.
Worst case is that it is stuck at 7.2.5 forever, I had to go back to backups to get my client as Battlenet updated it to 7.3.0 a while back.
It would be nice to have an update other than soon if possible.
7.3 will not be the next months. Since Blizzard has blocked access to the receipt of client information.
no, no))
Shauren, could you answer the questions, pls?
They haven’t even added the instances from Hellfire Citadel + to the areatriggers what makes you think they would care about an upgrade.
“I had to go back to backups to get my client as Battlenet updated it to 7.3.0” + “sniffer for 7.3.0”