mirror of
https://github.com/azerothcore/mod-ale
synced 2025-11-29 15:38:17 +08:00
34 lines
2.4 KiB
Markdown
34 lines
2.4 KiB
Markdown
#Installation
|
|
Get the core:<br/>
|
|
[](https://travis-ci.org/ElunaLuaEngine/Eluna-TC-Wotlk) [Eluna TrinityCore WOTLK](https://github.com/ElunaLuaEngine/Eluna-TC-Wotlk)<br />
|
|
[](https://travis-ci.org/ElunaLuaEngine/Eluna-TC-Cata) [Eluna TrinityCore Cataclysm](https://github.com/ElunaLuaEngine/Eluna-TC-Cata)
|
|
|
|
[](https://travis-ci.org/eluna-dev-mangos/ElunaCoreClassic) [Eluna cMaNGOS Classic](https://github.com/eluna-dev-mangos/ElunaCoreClassic)<br />
|
|
[](https://travis-ci.org/eluna-dev-mangos/ElunaCoreTbc) [Eluna cMaNGOS TBC](https://github.com/eluna-dev-mangos/ElunaCoreTbc)<br />
|
|
[](https://travis-ci.org/eluna-dev-mangos/ElunaCoreWotlk) [Eluna cMaNGOS WotLK](https://github.com/eluna-dev-mangos/ElunaCoreWotlk)
|
|
|
|
On **TrinityCore** navigate to `\src\`<br />
|
|
On **MaNGOS** navigate to `\src\game\`<br />
|
|
|
|
Open `git bash` in `LuaEngine` folder and do
|
|
1. `git init`
|
|
2. `git remote add origin https://github.com/ElunaLuaEngine/Eluna`
|
|
3. `git pull origin master`
|
|
|
|
Compile the core normally (use cmake on TC)
|
|
|
|
#Updating
|
|
When updating you should take up the `commit hashes` you are on, just in case.
|
|
You can get it from git with `git log` for example.
|
|
Use this when git is open in the source folder as well as in LuaEngine folder.
|
|
You should take note what are the newest SQL updates in `sql/updates/*` folders.
|
|
|
|
Use `git pull` in core source and in LuaEngine folder to get the newest source changes and Eluna from github.
|
|
Try compiling and if you encounter errors, report to [support](https://github.com/ElunaLuaEngine/Eluna#links) or [issues](https://github.com/ElunaLuaEngine/Eluna/issues).
|
|
You can revert back to the old sources by using `git reset --hard 000000`, where 000000 is the `commit hash`.
|
|
|
|
If the compiling was successful, you should update your database if needed.
|
|
You can do this by running all **new** SQL files in `sql/updates/*`.
|
|
You need to see your notes from before pulling the updates or you can use the old commit hash to see on github what were the last files you ran.
|
|
An easy way is to just look at the created/modified date on the files.
|