It listed 1 = us, 3 = eu, 4 = ptr, which does indeed seem to be more version than region. version was referred to as region_ish in both header and entry, which may be utter bogus though.Multiple records will have the same 'index' when pushed at the same time. The index is not exactly an index but a push ID.There have previously been two versions of this page which different naming: Strings are inline, and IDs are always provided before the record, regardless of whether or not there is an ID value in the record data additionally. There is no offset map, field compression of any kind, and no deduplication. The file uses the same record structures as the WoW binary requires but with none of the mechanics found in newer DB2 formats. It is theorized that the file is a sort of 'packet replayer' for the WoW executable, used for updating client-side DB2s to latest hotfixes on boot up, before confirming with the server about the newest changes. It even sometimes contains server-side database changes (entries with an unknown 'table_hash'). It contains server-provided new and changed records for all client-side database tables.

All files in the 'ADB' folder were consolidated into a single new file, DBCache.bin. WDB5 and WCH8 were retired simultaneously in Patch 7.2.0 Build 23436. Note: If offset_map exists, all the strings will be embedded inline in the records (as null-terminated c-strings). Uint32_t IDs // Optional - can be detected by pulling 'flags' from relevant DB2 Struct offset_map_entry // Optional - can be detected by pulling 'flags' from relevant DB2 This part of the structure is optional.The string block usually still exists, just as size 2 with two blank entries. Uint16_t length // this is the length of the record located at the specified offset Uint32_t offset // this offset is absolute, not relative to another structure this can (and often will) be zero, in which case you should ignore that entry and move on This section only applies to versions (7.0) … 'record_size' should account for this (it would be '8' in the example given in the previous sentence). If you have a record with three fields: Int32, Int8, and Int8 - then there will be 2 bytes of padding at the end of every record, including the last one. Note: Each record is aligned to the length of the longest field type in the record.Short string_lengths // sum of lengths of all strings in row Int indices // maps from id to row index in records below static_assert (header.record_size = sizeof (record_type))

Wow legion ptr folder