Pages (Latest 10 updated) :

Add a module

  1. Get the module from the catalogue: (For this example, we'll be using this module: mod-npc-services)

    • Clone it using Git as you did during the core installation. Set the Destination to "C:\Azerothcore\modules\mod-npc-services" (Recommended method) [Jump to step 9 to make sure it cloned correctly]
    • Use the download button on the catalogue page
    • Use Download ZIP button on the module's Github page
  2. If in the previous step you chose not to clone the repo, you'll need to extract the downloaded ZIP archive. Once this is done, your resulting folder should look like this: img1

  3. Due to a discrepancy between the way AzerothCore loads modules and how Github names ZIP code archives, you will need to rename the directory name. The folder will have the branch name placed onto the end of it, as in mod-npc-services-master. You will need to remove this branch name, leaving only mod-npc-services: img2 edit

  4. Copy the renamed folder, as you'll be pasting it into the modules folder

  5. Navigate to your AzerothCore modules folder (C:\Azerothcore)

  6. You will see in that directory the modules folder: img3 edit

  7. Open the modules folder, it should look quite sparse: img4

  8. Paste the module folder into the modules folder, it should now look like this: img5

  9. Now to recompile! Open CMake and configure. If the module has loaded correctly, you should now see it in the CMake log as well: img6 edit

  10. Then generate: img7 edit

  11. Now open the generated project file, clean, and build the solution

SQL Queries

  • If your module contains a sql folder, you will need to run the queries inside for the module to function correctly: img8 edit

    • Opening this folder, we should then see any of these three folders: auth, characters, or world. In the example module, it contains a world folder: img9

    • Depending on the module, there could be more than one query file you would need to execute. Refer to the readme of the module for information regarding this. In our case, there is only one .sql file to run, so our job is easy: img10

  1. Open your SQL editor of choice. In this case, we will be using HeidiSQL. You will need to select the database the query applies to on the left before you run the query. Since our query was in the world folder, we will select acore_world. Once the database is selected, we will then load the SQL file: img11

  2. Once you navigate to the SQL file and open it up, it will open the query in a new tab. Double check that the database tab is pointing to the right database, then run the query using the marked button above the tabs: img12 edit

With that, the module is installed! In the case of mod-npc-services, we'd then launch our server and run the command .npc add 55002 (The NPC Entry) to spawn the NPC.

DBC Patches

If your module contains DBC files (Such as mod-arac or mod-worgoblin) there are a couple extra steps you need to take to install them correctly. The DBC files included with the module will need to be copied to your server's DBC folder in its Data directory. If you're unsure where this directory is, it is set in your worldserver.conf under the DataDir option.

You will also need to add these patches to your client. In the case of mod-arac, it's small enough that you can grab the Patch-A.MPQ file directly from the repository. You can then copy it into the Data folder of your Wow client. However, in the case of a bigger patch like mod-worgoblin, you'll need to take the whole patch-contents folder and copy it to the Data folder of your Wow client, but you'll also need to rename the folder to Patch-A.MPQ. You will need to do this step for every user connecting to your server with these changes.

You don't necessarily have to use the letter A specifically. If you use the common HD patch for example, you may find that you have many patches in your Wow Data folder already, and if Patch-A is already taken, the client will also accept numbers 1-9 and letters A-Z. Be aware, however, that the client has an order in which it will read patches, specifically it will read patches 1-9,A-Z, with the contents of 1 being the first and the contents of Z being the last loaded by the client.

If you're using a client other than enUS, you may have to place the patch file in your locale folder and name it accordingly. For example, using a deDE client, the path would look like Data/deDE/patch-deDE-A.MPQ. This is due to other localizations of the client having differences in patch load order.