/DynastyCore

DynastyCore Warlords of Dreanor 6.2.3 20779 (Development On Hiatus)

Primary LanguageTSQL

Overview

World of Warcraft Warlords of Draenor (6.2.3 20779) emulator based on TrinityCore project (6.x), JadeCore (5.0.5), Garrosh (5.4.X)

Note

Do not use the World Database in the sql/base folder use the database here: https://github.com/TheGhostGroup/DynastyCore/releases it's not perfect but it works. More updates to come and better world databases in the future. At the moment I'm the only one working on this.

Patched Client Exe

At current the only patch exe that works is this one https://mega.nz/#!2YtTHarS!8v1gOioOooUN1JBWmG56-QCPE9QVDxjK9X40MSk20vk Make sure when setting the realm list address in config.wtf that you set the file readonly as there is a bug and the client will try to change the address causing issues connecting.

Requirements

  • Platform: Linux, Windows or Mac
  • Git ≥ 1.7+
  • ACE ≥ 6.2.0
  • MySQL ≥ 5.5.0+
  • CMake ≥ 3.2+
  • OpenSSL ≥ 1.0.0
  • GCC ≥ 4.7.2 (Linux only)
  • MS Visual Studio ≥ 12 (2013) (Windows only)
  • Xcode 7 (Mac only)

Install

Comming Soon! When I Get The Time To Make A Tutorial.

In order to complete the installation of the core, you need some other dependencies, they are:

  • LibCurl, under linux its the package libcurl4-openssl-dev, under windows you may have to compile it your self,
  • EasyJson headers, for that you only need to execute in your git repo :
git submodule init && git submodule update --remote
  • If you have the message Git was NOT FOUND on your system please uninstall and update your git version (you can also change the path for the binary on yout PATH)
  • NEW Windows user you need the mysql server installed, download the last version (5.7+) here : MySQL Community Server if you need the x86 build just change the include path on cmake
  • NEW If you use MSVC 2013 you MUST have the update 3+

Commit naming convention

  • When fixing bug, by all means include the issue number.
  • When completing feature if you have some task identifier, include that.
  • If the identifier included goes with subject, it often makes sense to just reuse it. (Use Core/XXX: "Commit name" format)
  • If the project is large, mention which component is affected.
  • Describe the change in functionality , never the code (that can be seen from the diff).