A content database for mangos-one, and *World of Warcraft Client Patch 2.4.3 - Fury of the Sunwell. It is compatible with client 2.4.3 (build 8606).

This database is currently just an import of the TBC-DB project by X-Savior and is intended to help new users in finding content for their mangos-one installation.

The current data is based on TBC-DBC Update Pack 1.1.1.

The develop branch is where the development of mangos-one database is done. Any of the commits submitted here may or may not become part of the next release.

It is recommended to use the master branch for stable systems, and only use the develop branch if you intend to test commits and submit issues and/or reports.

The mangos-one database is compatible with mangos-one revision 1376 and newer. It also requires scriptdev2 revision 2271 in order to be fully enjoyable.

The basic principle behind this customized database repository is to keep the databases stored as individual tables, and all content rows stored as single lines to make changes more trackable for the user (that would be you).

The repository is developed and maintained using the excellent git-flow extension for git, to provide a clear, and visible workflow to the user.

By default mangos-one uses four databases:

• op_characters: where all character data is stored,
• op_realm: where user accounts, and realms are defined,
• op_world: where the world with creatures, items, objects, quests, etc. is defined,
• op_scripts: and the ScriptDev2 database.

In order to use this database repository, you will have to edit mysql_info, and edit in the desired username, hostname, and password.

Once you have the desired database user and rights configured in MySQL, you may use the mysql_import script to load the individual data tables into your databases. Should your database user have wildcard rights, the script creates the database - if not existent - and then populates them.

If you make changes to the database, either by adding/modifying content, or by making changes to the database structure, you may execute mysql_dump to save each table into the repository. Should you add or remove tables, add dump_data, dump_struc commands to mysql_dump, or remove them as needed.

If you feel like submitting an issue, please do so only if you are willing to provide a detailed report, and are available to verify any solution to the issue provided by the developers of this repository.