A content database for mangos-classic, and World of Warcraft Client Patch 1.12 https://github.com/cmangos/classic-db
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
cala 4ad219fca0 [2937] Revert [2928] 1 month ago
ACID [2934][TDB][ACID] Fix many creature_ai_texts and fill broadcast_text_id where possible 2 months ago
Full_DB [2467] Classic DB release version 1.10.1 "The Shifting Sands" 10 months ago
Updates [2937] Revert [2928] 1 month ago
dev [0971] Added dedicated development directory 5 years ago
utilities [2914] Make object 181444 despawnable on usage 2 months ago
.gitignore [1450] Allowed the use of subdirectories for development 3 years ago
AUTHORS [1476] Finalize inclusion into CMaNGOS organisation 3 years ago
COPYRIGHT.md [2117] Exclude copyrighted content from GPL 1 year ago
InstallFullDB.sh Remove redundant spell.sql application in install script 4 months ago
LICENSE.md Use default GPL3.0 license 1 year ago
README.md [2467] Classic DB release version 1.10.1 "The Shifting Sands" 10 months ago
appveyor.yml [2467] Classic DB release version 1.10.1 "The Shifting Sands" 10 months ago


Classic DB for CMaNGOS/mangos-classic

A content database for mangos-classic, and World of Warcraft Client Patch 1.12 - Drums of War. It is compatible with client 1.12.1 (build 5875), 1.12.2 (build 6005) and 1.12.3 (build 6141).

Classic DB is released under the GPL v3. The file (LICENSE.md) must be a part of any redistributable packages made from this software. No licenses should be removed from this software if you are making redistributable copies.

Classic DB contains copyrighted materials that are not part of the GPL v3. Informations about copyrighted materials are located in the file (COPYRIGHT.md).

World of Warcraft content and materials are trademarks and copyrights of Blizzard or its licensors. All rights reserved. Classic DB is part of CMaNGOS project and is not affiliated with Blizzard or its licensors.


The Classic DB database is compatible with mangos-classic rev z2742 and newer.

Getting started

The basic principle behind this database repository is to have a single SQL file holding every table in the database. When something is changed into the database the modification is done by adding a small SQL update files placed into the updates directory. Every time an user (that would be you) wishes to change something into the database, he/she have to create and add the right SQL file. This helps tracking what changes are made, when and where.


Classic DB is the main content database: mangos where the world is defined with creatures, items, objects, quests, etc.

It must be applied after creating the mangos database from your mangos core distribution, usually mangos-classic from CMaNGOS project.

If you used the default values when installing your mangos core, simply run into a bash compatible shell (like Bash Git for Windows) the following command ./InstallFullDB.sh.

It will create a single file InstallFullDB.config.

If you have modified the default values for connecting to the database, in order to use this database repository, you will have to open InstallFullDB.config, and edit in the desired database, username and password according to how you have configured your MySQL server. Default values for mangos core are username:mangos, password:mangos, database:mangos. For security reasons, it is strongly adviced to use different username and password.

Once you have the desired database user and rights configured in MySQL, you may run again the ./InstallFullDB.sh command to load the individual data tables into your database, populate them and apply all updates since the last milestone.

For a full installation guide, please refer to CMaNGOS installation instructions.


You are welcome to contribute to this database project. There are three main ways of contributing. Choose the one fitting your skills.

  1. Open a ticket/issue on CMaNGOS issue tracker on GitHub. Describe the issue as accurately as possible, how things currently are, how things should be instead. Example: “NPC Mighty Skeleton in Western Plaguelands does not wield its weapon. It should have a sword.". You can improve your issue report by giving the ID/entry of the creature, object, quest, spell... it helps developers to find quickly where is the problem. In-game GM commands like .guid, .lookup quest (or creature, spell, object), .gobject near (or target) are great to get those informations
  2. If you have SQL knowledge you can also open a ticket/issue and provide a fix, even partial. To help you to understand the DB structure, have a look a the wiki page or feel free to ask developers in the issue report. You can also try to fix currently open issues
  3. Make a pull request. If you feel like cloning the database repository, you can test your own fixes and do a pull request that will be reviewed and discussed with you before merging

Whenever possible, provide sources about the issue to help developers to get a better understanding of the issue (wowwiki, wowpedia, wowhead, official data...). Note that everything coming from private servers is not a reliable source.

Note that the more complete your contribution is (i.e. close to a pull request), the quicker it will become part of the database. But as this is a community project, the developers will always try to help you move through the various stages of contributing!