Nay

Read http://collab.kpsn.org/display/tc/Installation+Guide

Start VS in Administrator mode. Seems to be a problem with permissions.

Post the full compile log, Armandas.

VS 2013 6.x build has been fixed on https://github.com/TrinityCore/TrinityCore/commit/89a8a7e1a4bdc22d2da17b1a3bf34fd52bf87e85

​This is not longer needed since https://github.com/TrinityCore/TrinityCore/commit/c8950c55ef46470dd411fd9c6d77fa6382d9e48f (3 days ago)

All these graphical interfaces run on top of Git. Everything can be done with Git alone.

We actually already have most of that implemented... The name of the "sniffer packet software" is WowPacketParser With SniffData we can filter by all these fields: https://github.com/TrinityCore/WowPacketParser/blob/master/WowPacketParser/Enums/StoreNameType.cs#L8-L28 However this doesn't allow for users to easily upload sniffs to the platform. About anonymizing sniffs see https://github.com/TrinityCore/WowPacketParser/issues/171

WoW is not being written from scratch, every patch is an iteration over the previous so most work from previous versions is applicable to later versions.

Soon enough we'll have a platform to upload sniffs that is not a forums. I'll try to add those features you talked about to it.

git checkout -b 7.x

You need to set the variables I printscreen above, related to OpenSSL.

Every year and every day is quite far away. There aren't more vmaps, we simply extract more data for each vmap "file".

What makes you think that's happening?

I'm not sure why your OpenSSL variables are named like that. It should look like this: In your case, OpenSSL-Win32, since you are compiling in 32 bits (why thou?)

Yes, and the problem is quite clear. You need Boost instaled and BOOST_ROOT in the environment variables, like described in the wiki. You also don't have OpenSSL installed.

VMaps are not used directly in scripts, they belong to the terrain/maps. If you meant how to create VMaps for a area, I have no idea and that's out of the scope of TC.

The problem is somewhere else. Paste the output of your CMake GUI.

The error is quite clear. Found OpenSSL library: optimized;SSL_EAY_RELEASE-NOTFOUND;LIB_EAY_RELEASE-NOTFOUND;debug;SSL_EAY_DEBUG-NOTFOUND;LIB_EAY_DEBUG-NOTFOUND You need to install OpenSSL properly.

Are you sure that's the whole log? I don't see any error happening in your log.

I'm afraid such page would be nearly impossible to maintain. You can check some stuff that is happening in issues like https://github.com/TrinityCore/TrinityCore/issues/15079 (changelog), https://github.com/TrinityCore/TrinityCore/issues/15127 (SAI for Catalysm creatures), https://github.com/TrinityCore/TrinityCore/issues/15181 (Cataclysm Zones - Movement) or https://github.com/TrinityCore/TrinityCore/issues/15182 (Cataclysm Zones - Quests + Phasing)

Sniffing records everything sent between the client and the server (see Opcodes.h) There's a sticky already saying how to use the sniffer here. Atm we don't need anything from sniffs however any sniff will be useful eventually. You can upload the .pkt files somewhere and put the link in http://community.trinitycore.org/forum/13-wdbadbsniffs/

You can ignore all those "warnings". (Note to self: we need to hide those debug messages)

iSwürfel: you need to paste what the cmake GUI outputs

Just to make it clear, VS 2015 works fine with TC (however you'll need to compile your own Boost libs since they don't yet ship installers for msvc-14) And yes, you could have unchecked all the options in the VS install screen, including the emulators.

We are not required to always follow the official versions, we could stop on arbitrary 6.x version but so far that wasn't worth yet (weighting prons vs cons). 3.3.5a was always 12340 because there's no other build for 3.3.5a...