Carbenium

If you read the message carfully, you'll see that it's just a warning and no build error. Kind regards, Carbenium

--- 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 ---

Hi, this doesn't look like a clean TrinityCore server. We can only help you if you use the official code base (https://github.com/TrinityCore/TrinityCore/). Kind regards, Carbenium

You might want to take a look here: http://www.ownedcore.com/forums/world-of-warcraft/world-of-warcraft-bots-programs/wow-memory-editing/285075-wow-binary-collection-release-ptr.html Kind regards, Carbenium

@Shin: It is probably advantageous to implement a new machine readable output in WPP since the produced txt files aren't really consitent. That should be the first development step.

--- 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 ---

--- 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 ---

--- 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 ---

--- 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 ---

--- 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 ---

--- 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 ---

--- 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 ---

--- 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 ---

We don't use data from WDB/ADB files for quite a long time since all the relevant information is found in sniffs. Therefore we don't have any current tools to extract those files. Regards, Carbenium

Hi, we only support 3.3.5, 6.x and partially 4.3.4. There is no "official" 1.1.2 TC version. Regards, Carbenium

CMake -> File -> Delete Cache Then click "Configure" and a the compiler selection will pop up. Select the right VS version (without Win64 at the and) and you're good to go. Regards, Carbenium Edit: ofc click "Generate" too and open the new .sln file with VS to apply the changes.

If possible just wipe the world db and let the updater create it from scratch. That should be the easiest solution. Regards, Carbenium

Works on HEAD. I pushed a fix. Regards, Carbenium

Hi, 1. Yes, that is possible. You can distribute the connection_patcher.exe 2. See 1. 3. No. Everybody has to patch the game on his/her own. Give us some more info what exactly didn't work (connection.log for example) Regards, Carbenium

@m_pan Maybe a small statement from me why I locked the thread. Having a constructive discussion about Legion is totally fine with me, actually it is really appreciated. I had rather my problems with the last 4 posts. They weren't in any kind related to the discussion that thread was about. As Zedron already said: If someone is thinking that TC is just a polished Mangos, then I really have to assume that person never looked at the code or does not understand it. I also do not understand why someone is spending time to write posts which do only spread critisicm and sarcasm. We (and I mean all contributors, not just the "TC team") do this out of fun and I don't want people to spoil this fun. Regards Carbenium PS: A locked thread does not have to be locked forever...

TDB 6.03 & TDB 335.60 released.

So regarding the patching: 1. Parts of the server adress is hardcoded into the client. This has to be removed, so we can set it freely. 2. Some packets are encrypted with RSA. Since we can't break blizz' key, we had to patch our own into the client. 3. Some parts of the authentication process are in external modules. During the loading process some verification takes place, which had to be removed too. I guess that should sum it up. Regards, Carbenium

We won't include TDB into the Git tree since it would bloat the size even more. Regards, Carbenium

I'd say this is quite active development: https://gitlab.com/trinitycore/TrinityCore_434/commits/4.3.4 ;) Regards, Carbenium

--- 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 ---