Nay

You can change language in Battle.net.

Git Extensions is not a requirement, you only need Git (I honestly don't know why the wiki uses Git Ext.) Side note: we need to fix the dependency mess, needing MySQL just to compile tools is quite.. stupid.

@Togelmombo: Fixed on https://github.com/TrinityCore/TrinityCore/commit/b63082971fac8e239f08db0d16113c46c7c1e3ee

Fixed in https://github.com/TrinityCore/TrinityCore/commit/e2fb3bbd466641c794438933e636d63ebf19432e

If there's mini-events, let them finish (i.e don't rush killing the npcs or so); if you see a talkeable npc, talk with it (for gossips); Explore the whole area Subv wrote a "mini-guide" but it's in Spanish... https://gist.github.com/Subv/c3498b5e952c5c978bcf

Get http://community.trinitycore.org/topic/9849-trinity-cores-sniffer-for-wow-62020253/ running and play like you did before. After that upload the .pkts somewhere and put them in http://community.trinitycore.org/forum/13-wdbadbsniffs/ I don't think there's anything specific that we *need* right now so anything that you can get will be useful.

Packet opcodes and structs are reverse engineered from the client. You can find a bit about that from the WPP project Packets have a header and a body. In the header it's defined the direction (client->server, server->client), the timestamp it was sent, the opcode id and some other fields. The body is simply a bunch of bytes that only make sense once the opcode is known. Here's an example of reading a packet: https://github.com/TrinityCore/WowPacketParser/blob/master/WowPacketParser/Parsing/Parsers/GuildHandler.cs#L705-L712

This error happens because CMake is picking up the wrong libmysql.lib. See http://collab.kpsn.org/display/tc/Application+Error%3A+0xc000007b and https://github.com/TrinityCore/TrinityCore/issues/15072#issuecomment-123811344

Why do you guys keep compiling in 32 bits when you can do it in 64 bits? Your libmysql.lib is 64 bits because it's in C:/Program Files/MySQL. If you insist on 32 bits you need to use a 32 bits MySQL install. There's a zip on the wiki.

ConnectionPatcher is known to work on Windows, for the current version.

genion19: I think you should report that issue at https://github.com/TrinityCore/TrinityCore/issues (be detailed!) The texts shouldn't be hardcoded in the code.

At this moment, it is better if you use something like SQLYog or phpmyadmin to browse the DB schema instead of relying on the structure in the wiki. P.S PrevQuestId and NextQuestId (and a few others) were moved to `quest_template_addon`

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

​http://collab.kpsn.org/pages/viewpage.action?pageId=12714432

Ok, however what matters is the libmysql.lib which is chosen by CMake (which you should override).

Krang: What MySQL version do you have installed?

​I have no idea how many times we have to say it but do not change that gamebuild unless you know what you are doing. You are not the first nor the last one doing that tho. P.S Sorry for the mini rant, just tired of people doing the same mistakes and then wondering why stuff doesn't work

bnetserver can't handle 3.3.5 and authserver can't handle 6.x connections. I'm fairly sure you can have all of the servers on the same machine however you need to use different ports.

There's no MySQLEAY.Dll. This might help: https://github.com/TrinityCore/TrinityCore/issues/15068

Ahmmm... you really should get some sleep. You need to drag WoW-64.exe to connection_patcher.exe (or call "connection_patcher.exe WoW-64.exe" in the console). You can get connection_patcher.exe by compiling the core with tools enabled.

Downgrade MySQL 5.7 to 5.6.

Check if you are linking against the correct libmysql.lib

Compile in Debug mode and check if there's a crashlog in the Crashes folder.

Post the output of the mapextractor. The .blp files are not needed.