This repository has up to date column/field definitions for database files used in World of Warcraft.
- Updated definitions for all World of Warcraft builds between 184.108.40.206654 and current
- New builds added soon after release (as long as there are no major DBC format changes)
- Human readable
- Machine readable (C# and Python code available as well as a tool to convert DBD to JSON/XML)
- Updated database definitions for all versions of World of Warcraft (work ongoing, some already available)
Cool stuff we might end up doing if this gets enough traction:
- Repository will feed automated updates on WoWDev.wiki
- Pull requests are automatically checked for validity
- More? Open an issue if you have any ideas
If you have any suggestions for changes or additions to the format, feel free to open an issue. The DBD format is currently specified as follows:
List of column definitions at the start of the file. This is defined once per column at the start to help keep column names the same across the file.
COLUMNS, followed by the following:
You can also add a comment to a column definition by adding
// Comment goes here at the end of the line.
Valid types that parsers should support:
Unverified columns (guessed, etc) have a
? at the end of
BUILD is required.
LAYOUT is required for versions that have it. Can be both.
Line starts with
LAYOUT followed by a list of layouthashes separated by a comma and a space. Can appear only once.
Line starts with
BUILD followed by a range, multiple exact builds separated by a comma and a space or a single exact build. Can appear multiple times.
Line starts with
COMMENT, only for humans. Can appear only once.
Ranges for current expansions should be specified per minor version to not conflict with other branches. Example:
BUILD 220.127.116.1136-18.104.22.16814 BUILD 22.214.171.12438-126.96.36.19920 BUILD 188.8.131.5278-184.108.40.20696 BUILD 220.127.116.1146-18.104.22.16847
As no more builds/branch conflicts are expected for anything older than the current expansion, ranges are allowed to span a full expansion. Example:
BUILD 22.214.171.12492-126.96.36.19995 BUILD 188.8.131.5222-184.108.40.20640
When using ranges, please confirm that the range is correct by verifying the version definition for all public builds included in it.
Multiple exact builds
BUILD 0.7.0.3694, 0.7.1.3702, 0.7.6.3712
Single exact build
ColName refers to exactly the same name as specified in the column definitions.
No size (floats, (loc)strings, non-inline IDs):
Size (8, 16, 32 or 64, prefixed by
u if unsigned int):
With comment (for humans):
ColName // This is a comment, yo!
ColName can be prefixed with annotations to indicate that this is a special kind of column in this version.
Annotations start with a
$ and end with a
$ and are comma separated when there's more than one. Current annotations:
id this column is a primary key. Example: (inline)
relation this column is a relationship. Has
noninline when stored in relationship table. Examples: (inline)
noninline this column is non-inline (currently only used for
$relation$). See non-inline examples above.
Files will be saved with DBName.dbd filenames where DBName is the exact name of the DBC/DB2. Every file has multiple definitions for each different structure that has been encountered for that file. Version structures are separated by an empty new line. All line endings should be in Unix format (\n).
Example definition file
You can view a sample definition here.
All feedback is welcome!