A content database for mangos-zero, and World of Warcraft Client Patch 1.12 - Drums of War. It is compatible with client 1.12.1 (build 5875), and 1.12.2 (build 6005).
mangos-zero-database is released under the GPL v3. The file (LICENSE.mdown)
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.
The develop branch is where the development of mangos-zero 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-zero database is compatible with mangos-zero revision 1765 and newer. It also requires scriptdev0 revision 464 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-zero uses four databases:
zp_characters: where all character data is stored,zp_realm: where user accounts, and realms are defined,zp_world: where the world with creatures, items, objects, quests, etc. is defined,zp_scripts: and the ScriptDevZero 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.