• Stars
    star
    1
  • Language
    C++
  • Created over 2 years ago
  • Updated over 2 years ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

Based off of the initial leaked firestorm WOD core

Overview

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

BEWARE !

Never commit into interrealm only crash fix, wod branch is the prod branch !

Build Status

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

Detailed installation guides are available in the wiki for Windows, Linux and Mac OSX.

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

####How to Cppcheck run cppcheck --enable=all --xml-version=2 > PathToFile/cppcheck.xml --inconclusive path PathToFile/wod/src/ --verbose

and run ./cppcheck-htmlreport --file=PathToFile/cppcheck.xml --source-dir=PathToFile/wod/src --report-dir=PathToFile/wod/cppcheck/ to get the html out

How to compile

  • Clone the source. Download Visual studios 2015.
  • Once you do that, download the software in the release section, boost, DotNet, MySQL Community, Vcredist_x64, Win64OpenSSL 1_0_2u & git.
  • Once you've done this, you must make Boost an environment variable. Instructions to do so in the software release section
  • Download the Cmake version in the release. Run Cmake and build it by using the cloned source directory. You shouldn't have any errors when you use Cmake.
  • After a successful build of Cmake, you should have a build folder or whatever you named it to.
  • Go into that folder, after having VS 2015 installed. Open the .sln file. Once you've done this, select the build from debug to release.
  • Clean the solution & build. Depending on your computer specs this process may take awhile. If it takes a long time, that means it's working as there's a lot of warnings.
  • After a successful build. Go to the release folder that was just made. Make a new folder and copy/paste everything in there. Once you have this, run the authserver/world server. New files should appear.
  • Download the DBC files & maps/mmaps/vmaps/build from the release section & extract those files in that same folder with the worldserver.
  • Download the libssl32.dll libeay32.dll libmysql.dll ssleay32.dll ace.dll libmysqld.dll and copy/paste or extract into same folder.
  • Once you have this all set up. set up your mySQL community account (local). Once you have this set up, go into your authserver.conf & worldserver.conf to set your database usernames/password. auth, characters, hotfix & world.
  • Download Heidi SQL, connect to your local mySQL account with the mySQL service running (won't work if it's not running). Use your login information you used as your mysql account. Import the databases from the release section. You must go into the my.ini file and change the file size allowed to import the world.DB
  • Once everything is imported. Run the authserver & worldserver. Should work without crashing after your worldserver is done loading, create your account & your good to go!