summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/Contribute.md18
-rw-r--r--docs/Create-a-Script.md2
-rw-r--r--docs/FAQ.md8
-rw-r--r--docs/How-to-test-DB-only-changes.md8
-rw-r--r--docs/How-to-test-a-PR.md6
-rw-r--r--docs/Install-with-Docker.md2
-rw-r--r--docs/Requirements.md2
-rw-r--r--docs/Update.md4
-rw-r--r--docs/Upgrade-from-pre-2.0.0-to-latest-master.md6
-rw-r--r--docs/creature_text.md2
-rw-r--r--docs/installation_0.x.md2
-rw-r--r--docs/installation_1.x.md2
12 files changed, 31 insertions, 31 deletions
diff --git a/docs/Contribute.md b/docs/Contribute.md
index 872e567..939e5ee 100644
--- a/docs/Contribute.md
+++ b/docs/Contribute.md
@@ -1,16 +1,16 @@
You can contribute in several ways to AzerothCore:
-- [commenting an open issue](https://github.com/azerothcore/azerothcore-wotlk/wiki/Contribute#how-to-comment-an-issue)
+- [commenting an open issue](Contribute#how-to-comment-an-issue)
-- [opening an issue](https://github.com/azerothcore/azerothcore-wotlk/wiki/Contribute#how-to-open-an-issue)
+- [opening an issue](Contribute#how-to-open-an-issue)
-- [testing a pull request](https://github.com/azerothcore/azerothcore-wotlk/wiki/How-to-test-a-PR)
+- [testing a pull request](How-to-test-a-PR)
-- [testing DB-only changes](https://github.com/azerothcore/azerothcore-wotlk/wiki/How-to-test-DB-only-changes)
+- [testing DB-only changes](How-to-test-DB-only-changes)
-- [creating a pull request](https://github.com/azerothcore/azerothcore-wotlk/wiki/Contribute#how-to-create-a-pull-request)
+- [creating a pull request](Contribute#how-to-create-a-pull-request)
-- [improving our wiki](https://github.com/azerothcore/azerothcore-wotlk/wiki/Contribute#improve-the-wiki)
+- [improving our wiki](Contribute#improve-the-wiki)
## General information
To contribute, you obviously need a github account.
@@ -37,7 +37,7 @@ If **(and only if)** the bug hasn't been reported yet, you can [open an issue](h
## How to test a Pull Request
-- Read [How to test a PR](https://github.com/azerothcore/azerothcore-wotlk/wiki/How-to-test-a-PR).
+- Read [How to test a PR](How-to-test-a-PR).
## How to create a Pull Request
@@ -45,7 +45,7 @@ Official GitHub tutorial [here](https://help.github.com/articles/creating-a-pull
In order to create a Pull Request (PR), you have to fork the AzerothCore repository (via your web browser, using the top-right Fork button) and clone your fork locally with `git clone https://github.com/YOUR_USERNAME/azerothcore-wotlk.git`.
-If you already have a local fork, remember to [sync it](https://github.com/azerothcore/azerothcore-wotlk/wiki/Syncing-your-fork) before creating a new Pull Request to avoid conflicts.
+If you already have a local fork, remember to [sync it](Syncing-your-fork) before creating a new Pull Request to avoid conflicts.
Open a terminal and move to your local clone of the fork, then create a new branch by typing:
@@ -53,7 +53,7 @@ Open a terminal and move to your local clone of the fork, then create a new bran
Now add your changes to the code.
-**IMPORTANT:** If you are going to add some database contents or structure changes, read [how to deal with SQL files](https://github.com/azerothcore/azerothcore-wotlk/wiki/Dealing-with-SQL-files) first.
+**IMPORTANT:** If you are going to add some database contents or structure changes, read [how to deal with SQL files](Dealing-with-SQL-files) first.
Then you can commit your changes and push them:
diff --git a/docs/Create-a-Script.md b/docs/Create-a-Script.md
index bc319a1..4dd063c 100644
--- a/docs/Create-a-Script.md
+++ b/docs/Create-a-Script.md
@@ -1,6 +1,6 @@
# Script vs module
-On AzerothCore, we don't really use the usual scripts like in other emulators. Instead, we work with modules which are way more practical to use. See https://github.com/azerothcore/azerothcore-wotlk/wiki/Create-a-Module
+On AzerothCore, we don't really use the usual scripts like in other emulators. Instead, we work with modules which are way more practical to use. See Create-a-Module
# Scripts
diff --git a/docs/FAQ.md b/docs/FAQ.md
index 8c43e07..f2aabbc 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -2,8 +2,8 @@
#### 1 - How can I contribute? I am not a developer, I know nothing useful.
-- You can help us by testing our [Pull Requests](https://github.com/azerothcore/azerothcore-wotlk/wiki/Contribute#how-to-test-a-pull-request), and participating on the github issues' discussions. You can also provide support when you can in our discord, on the popular [stackoverflow](https://stackoverflow.com/questions/tagged/azerothcore) and on other emulation forums (ac-web.org for example). You can also help us with documentation (this wiki, or the readme), we need help with that too!
-- If you're a developer, check out this page: https://github.com/azerothcore/azerothcore-wotlk/wiki/Contribute
+- You can help us by testing our [Pull Requests](Contribute#how-to-test-a-pull-request), and participating on the github issues' discussions. You can also provide support when you can in our discord, on the popular [stackoverflow](https://stackoverflow.com/questions/tagged/azerothcore) and on other emulation forums (ac-web.org for example). You can also help us with documentation (this wiki, or the readme), we need help with that too!
+- If you're a developer, check out this page: Contribute
#### 2 - Why is AzerothCore using more ram than TrinityCore?
@@ -11,11 +11,11 @@ AzerothCore is based on SunwellCore (a fork from TC). SunwellCore was a public s
#### 3 - I want this fixed or this feature or this module. How can I proceed?
-You can open a bounty and if developers are interested by the job, they might do it. Read this: https://github.com/azerothcore/azerothcore-wotlk/wiki/Bountysource
+You can open a bounty and if developers are interested by the job, they might do it. Read this: Bountysource
#### 4 - I have an issue, where can I get help?
-Read this carefully: https://github.com/azerothcore/azerothcore-wotlk/wiki/How-to-ask-for-help
+Read this carefully: How-to-ask-for-help
## COMMON ERRORS
diff --git a/docs/How-to-test-DB-only-changes.md b/docs/How-to-test-DB-only-changes.md
index 4c8dca9..3e88294 100644
--- a/docs/How-to-test-DB-only-changes.md
+++ b/docs/How-to-test-DB-only-changes.md
@@ -1,6 +1,6 @@
## Introduction
-The main guide about [How to test a PR](https://github.com/azerothcore/azerothcore-wotlk/wiki/How-to-test-a-PR) will work for all kind of PRs.
+The main guide about [How to test a PR](How-to-test-a-PR) will work for all kind of PRs.
However it is common to have PRs that only make changes to the database (typically the `world` database).
@@ -12,7 +12,7 @@ For those PRs there is a simpler way to test them, which will be explained in th
This tutorial assumes that you:
-- have a **recent** version of AzerothCore installed in your system (either using the [traditional setup](https://github.com/AzerothCore/azerothcore-wotlk/wiki/Installation) or the [Docker setup](https://github.com/azerothcore/azerothcore-wotlk/wiki/Install-with-Docker)). We recommend using latest `master`.
+- have a **recent** version of AzerothCore installed in your system (either using the [traditional setup](Installation) or the [Docker setup](Install-with-Docker)). We recommend using latest `master`.
- have a GitHub account, you can [register one here](https://github.com/join) for free.
- have a database client such as [HeidiSQL](https://www.heidisql.com/), Navicat or similar.
@@ -22,7 +22,7 @@ Open the PR page and click on the "File Changes" tab:
![File Changes](https://user-images.githubusercontent.com/75517/52176720-ea4da900-27b6-11e9-8459-d58adf7fd50c.png)
-- If you see `*.cpp`, `*.h` file changes, then follow [this guide](https://github.com/azerothcore/azerothcore-wotlk/wiki/How-to-test-a-PR) instead.
+- If you see `*.cpp`, `*.h` file changes, then follow [this guide](How-to-test-a-PR) instead.
- If you only see `*.sql` changes, keep reading.
@@ -60,4 +60,4 @@ After you test the changes, you need to return in a clean state (as you were bef
## Reports
-For instructions about what needs to be tested, how to report your test results and examples of other reports, please read from [this part](https://github.com/azerothcore/azerothcore-wotlk/wiki/How-to-test-a-PR#what-needs-to-be-tested) of the main PR guide. \ No newline at end of file
+For instructions about what needs to be tested, how to report your test results and examples of other reports, please read from [this part](How-to-test-a-PR#what-needs-to-be-tested) of the main PR guide. \ No newline at end of file
diff --git a/docs/How-to-test-a-PR.md b/docs/How-to-test-a-PR.md
index 8a5791c..f49a951 100644
--- a/docs/How-to-test-a-PR.md
+++ b/docs/How-to-test-a-PR.md
@@ -16,12 +16,12 @@ Clicking on the label above will show you the list of all PRs that need to be te
You need to:
-- have AzerothCore installed in your system (either using the [traditional setup](https://github.com/AzerothCore/azerothcore-wotlk/wiki/Installation) or the [Docker setup](https://github.com/azerothcore/azerothcore-wotlk/wiki/Install-with-Docker)).
+- have AzerothCore installed in your system (either using the [traditional setup](Installation) or the [Docker setup](Install-with-Docker)).
- have a GitHub account, you can [register one here](https://github.com/join) for free.
### What if the PR has only DB changes?
-Some PRs have only database changes (no C++ changes). If that's the case, there is a [simplified procedure to test such changes](https://github.com/azerothcore/azerothcore-wotlk/wiki/How-to-test-DB-only-changes).
+Some PRs have only database changes (no C++ changes). If that's the case, there is a [simplified procedure to test such changes](How-to-test-DB-only-changes).
If you're not sure, just keep reading here and do the traditional PR test which will work for all kind of PRs.
@@ -66,7 +66,7 @@ Basically you need to **recompile your sources** and **update the DB**.
### Using traditional setup
-If you are using the traditional setup, you have to recompile following the steps of the [3) Compiling](https://github.com/azerothcore/azerothcore-wotlk/wiki/Installation#3-compiling) from the main setup guide.
+If you are using the traditional setup, you have to recompile following the steps of the [3) Compiling](Installation#3-compiling) from the main setup guide.
You also need to update your DB. You can use the DB assembler to do that, but usually it's quicker to just manually importing the pending sql file(s) that the PR includes. Such file(s) are located under `data/sql/updates/pending_db_*`.
diff --git a/docs/Install-with-Docker.md b/docs/Install-with-Docker.md
index ca958a9..a6b70b2 100644
--- a/docs/Install-with-Docker.md
+++ b/docs/Install-with-Docker.md
@@ -76,7 +76,7 @@ Now cd into the main directory using `cd azerothcore-wotlk`. **All commands will
## WoW Client Data files
-You also need to have the data files. Check the step "5) Download the data files" from the [installation guide](https://github.com/azerothcore/azerothcore-wotlk/wiki/Installation#5-download-the-data-files).
+You also need to have the data files. Check the step "5) Download the data files" from the [installation guide](Installation#5-download-the-data-files).
Put your data files into the `docker/worldserver/data/` folder that is inside `azerothcore-wotlk`.
diff --git a/docs/Requirements.md b/docs/Requirements.md
index 945013b..8146889 100644
--- a/docs/Requirements.md
+++ b/docs/Requirements.md
@@ -14,7 +14,7 @@
To configure MySQL in Ubuntu 18.04 and similar (set `root` password and other settings) read [this guide](https://www.digitalocean.com/community/tutorials/how-to-install-mysql-on-ubuntu-18-04).
-Note: on latest versions of Ubuntu the default mysql version is 5.7. If you're using this version, [read this](https://github.com/azerothcore/azerothcore-wotlk/wiki/Requirements#mysql-57).
+Note: on latest versions of Ubuntu the default mysql version is 5.7. If you're using this version, [read this](Requirements#mysql-57).
# Mac OS X
diff --git a/docs/Update.md b/docs/Update.md
index 1fcc220..8de53b8 100644
--- a/docs/Update.md
+++ b/docs/Update.md
@@ -2,13 +2,13 @@
Move to your AzerothCore sources directory.
-- If you have your own fork of AzerothCore, you need to [sync it](https://github.com/azerothcore/azerothcore-wotlk/wiki/Syncing-your-fork).
+- If you have your own fork of AzerothCore, you need to [sync it](Syncing-your-fork).
- Otherwise, if you cloned AzerothCore directly from the main repo, you have to `git pull` to update it.
## 2) Recompile
-Compile again your sources, this step is the same as the [Compilation step during Installation](https://github.com/azerothcore/azerothcore-wotlk/wiki/Installation#3-compiling), but generally you can skip the CMake part.
+Compile again your sources, this step is the same as the [Compilation step during Installation](Installation#3-compiling), but generally you can skip the CMake part.
For example, in Linux/Mac you just have to `cd build;` and run `make -j 4; make install`.
diff --git a/docs/Upgrade-from-pre-2.0.0-to-latest-master.md b/docs/Upgrade-from-pre-2.0.0-to-latest-master.md
index b9c544c..d529998 100644
--- a/docs/Upgrade-from-pre-2.0.0-to-latest-master.md
+++ b/docs/Upgrade-from-pre-2.0.0-to-latest-master.md
@@ -8,7 +8,7 @@ You need first to update your server to this commit: https://github.com/azerothc
`git checkout 1fc22a74088e235e78fa02decbaf0864899477d7`
-Now update your **database** as [you normally do](https://github.com/azerothcore/azerothcore-wotlk/wiki/Update#3-update-the-database).
+Now update your **database** as [you normally do](Update#3-update-the-database).
### Step 2. Upgrade to latest master
@@ -16,6 +16,6 @@ Update to latest master:
`git checkout master; git pull;`
-**Note**: if you are using your own fork of AC, as usual, you have to [sync it](https://github.com/azerothcore/azerothcore-wotlk/wiki/Syncing-your-fork)
+**Note**: if you are using your own fork of AC, as usual, you have to [sync it](Syncing-your-fork)
-Now update your **core and database** (again) as [you normally do](https://github.com/azerothcore/azerothcore-wotlk/wiki/Update). \ No newline at end of file
+Now update your **core and database** (again) as [you normally do](Update). \ No newline at end of file
diff --git a/docs/creature_text.md b/docs/creature_text.md
index 7afe21b..3e71d93 100644
--- a/docs/creature_text.md
+++ b/docs/creature_text.md
@@ -49,7 +49,7 @@ Imagine that our following Lich King creature_text only has 1 Group ID which is
If we want to make him say his line when he enters combat we only need to set his smart AI event type to 4 (when the npc gets aggro), action_type to 1 (action type equivalent to talk event) and action_param1 to 0 (which is our desired group id in creature_text).
-For more information about smart_scripts table check this [link](https://github.com/azerothcore/azerothcore-wotlk/wiki/smart_scripts).
+For more information about smart_scripts table check this [link](smart_scripts).
``` SQL
# Our Lich King will shout "Frostmourne hungers" on aggro
UPDATE smart_scripts
diff --git a/docs/installation_0.x.md b/docs/installation_0.x.md
index d5db696..aaaf85c 100644
--- a/docs/installation_0.x.md
+++ b/docs/installation_0.x.md
@@ -1,6 +1,6 @@
## 1) Installing the requirements
-Make sure your system fits with the [requirements](https://github.com/AzerothCore/azerothcore-wotlk/wiki/Requirements).
+Make sure your system fits with the [requirements](Requirements).
## 2) Getting the source files
diff --git a/docs/installation_1.x.md b/docs/installation_1.x.md
index 3004b3d..2067054 100644
--- a/docs/installation_1.x.md
+++ b/docs/installation_1.x.md
@@ -1,6 +1,6 @@
## 1) Installing the requirements
-Make sure your system fits with the [requirements](https://github.com/AzerothCore/azerothcore-wotlk/wiki/Requirements).
+Make sure your system fits with the [requirements](Requirements).
## 2) Getting the source files