Skip to content

How to Install

Jump to bottom
ZhengPeiRu21 edited this page Aug 9, 2023 · 11 revisions

This is an AzerothCore module. It is installed through the same method as other AzerothCore modules.

  1. Download the project repo either by:

    a. Using Git (git clone https://github.com/ZhengPeiRu21/mod-individual-progression.git)

    b. Clicking Code->Download Zip in GitHub UI

  2. Place the project module folder (mod-individual-progression) in your AzerothCore modules folder. The folder must be named exactly mod-individual-progression. Ensure that -master is not on the end of the folder name! It is added by GitHub when downloading the ZIP and must be removed. The final structure should look like (AzerothCoreRoot/modules/mod-individual-progression/src).

  3. Re-run Cmake to detect the newly installed module

  4. Start your AzerothCore build

  5. While waiting for the building, run the SQL files. Please pay special attention to the following:

All files that begin with "optional_" or "zz_optional" have some changes that some players may want to not run (for example, removing quest region markers on the map like pre-3.2 WoW, or using correct Vanilla item stack sizes, which tend to be smaller than WotLK,) They are configured to the most commonly desired defaults, but please examine these files to decide if you would like to not use any of them. If you would like to not use a change, simply delete or do not run that particular SQL file.

The SQL files can be run one of two ways:

 a. If using the AzerothCore auto-db updater: Copy all files into AzerothCore/data/custom/db_world

 b. Manually installed through your SQL interface of choice (SQL CLI, HeidiSQL, etc.)
  1. Copy mod-individual-progression/conf/individualProgression.conf.dist to the config/modules directory relative to your AzerothCore binary. If the modules folder does not exist, please create it.
  2. Make a copy of the individualProgression.conf.dist file that you just copied, and name it individualProgression.conf. You should have both the .conf and the .conf.dist files in the config/modules/ directory, just as with the worldserver.conf files for base AzerothCore.
  3. Please examine the configuration options in individualProgression.conf and adjust them to your preference, though the defaults should be desired by most users.
  4. Please ensure that EnablePlayerSettings in your worldserver.conf is set to 1 - this is used to store per-player progression data.
  1. The Optional files provide several adjustments that require a custom client patch due to data that cannot be changed only on the server. Most notably, these include original Vanilla profession recipes and spell reagents, and restoring the Rogue poison skill. If you decide to use the optional patches, it is recommended that you ensure every player connecting has the custom patch, or they will run into issues such as the crafting recipe UI showing the WotLK version of a recipe, but the server requiring the Vanilla ingredients. If you would like to use the optional patches:

a. Extract dbc.zip in the mod-individual-progression/optional directory

b. Move all of the .dbc files into the dbc directory of your server, overwriting the existing files. (Please back up the existing files first if you would like to uninstall the module later.) There should be a total of 4 dbc files overwritten.

c. Place the patch-V.mpq file into the Data directory of the client.

d. Patch-J is an optional client patch that will restore the original login screen. Patch-U is an optional client patch that will restore original loading screens. Both of these are visual only changes that are completely optional and client-only, and only affect the client where they are installed. Individual players can choose whether or not to install them.

e. Additionally, for an even more accurate pre-WotLK experience, users may wish to install this addon, which hides vendor prices for items unless at a vendor. This feature was removed in late WotLK, allowing the client to always show item prices. This is a regular WoW addon installed by placing into the Interface/Addons directory. Like the loading screen patches, this is visual only and can be installed per player according to player preference.

Clone this wiki locally