Shauren

WPP now supports it as of https://github.com/TrinityCore/WowPacketParser/commit/62e3cab188c9622596eaee1e8b052e6610f8ef64

Updated to 7.2.5.24742

Unlike CMaNGOS, we don't store completed and turned in quests in character_queststatus table but move them to character_queststatus_rewarded

--- Canned message start --- It appears the issue in the original post was solved, so this thread shall be closed. Should you encounter any other difficulties, please open a new thread. --- Canned message end ---

It would certainly help you to stop trying to use tools designed for legion client on wotlk client. Build extractors from 3.3.5 branch, not master

The only fucked up thing is your configuration/installation 7.2.5 works exactly the same as 7.2.0 did (assuming you updated everything properly)

If this was a regular linux I would just tell you to run make install step with sudo because you are trying to put files into a system dir

Yes, master branch auth database IS structurally backwards compatible with 3.3.5 master branch has additional tables not present in 3.3.5 (all of bnet) and columns (Region/Battlegroup in realmlist table)

They are not compatible in the way that you can run one and connect from both clients but they can share the same database (even if you run them both at the same time - but you need to use the database structure from master, there are more fields in tables)

Do git checkout 0b0d4c4011b1be37590104dae6a5b7a6ae378eef to go back to last supported 7.1.5 version

I liked it more when they also had a history of cdn configs for past builds

authservers are compatible (up to wod, old auth code removed from client) if you just add the neccessary build info https://github.com/TrinityCore/TrinityCore/blob/3.3.5/src/server/authserver/Authentication/AuthCodes.cpp

report libssl-dev version (the package used for compile), not openssl version (binary openssl tools) your error message indicates that libssl-dev version is 1.1.0

Use absolute path for DataDir config, not relative (this standard linux path behavior, not TC specific)

I don't know what core you are using but its not TC, our hotfix database item_sparse table does not have any fields with the names like on your screenshot