You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: meta/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,6 @@ The only difference between these files is that enum files (DBDE) use numerical/
21
21
### Format
22
22
`Value Name // Comment`
23
23
This is very similar to DBD column definitions, but instead of a field type it has a decimal (enums) or hexadecimal (flags) value. Another difference is that only `Value` is required as there can be unnamed flags.
24
-
Just like DBD column definitions, `Name` can not contain spaces but can be followed by a `?` for unverified/placeholder names. It can also be followed by a comment starting after the name at `//`. Given both `Name` and `Comment` are optional, it is possible for a comment to start immediately after a name.
24
+
`Name` can contain spaces and can be followed by a `?` for unverified/placeholder names. It can also be followed by a comment starting after the name at `//`. Given both `Name` and `Comment` are optional, it is possible for a comment to start immediately after a name.
25
25
#### Versioning
26
26
If a flag/enum is only for a specific version, you can override the 'default' value for it by adding `(BUILD x.x.x.xxxxx) ` in front of the value. At time of writing this is tentative, more information is available [here](https://github.com/wowdev/WoWDBDefs/discussions/207#discussioncomment-16035912).
0 commit comments