Status: 2026-09-22. Retail files were read only.
Result
chunk_24.texdb is a standalone flat Key/Offset database without asset names. The Retail DLC-3 dataset is 1,011,361,794 bytes in size and contains 8,586 entries; the header, table, and payload data are contiguous. A spot-check test with Oodle confirms the entries and the 8c06 Kraken stream.
An empty chunk_26.texdb (32 bytes, zero entries) is therefore only suitable for a Decl-/Mount-probe chunk. For a map with DLC-3 textures, at least the complete TexDB content of chunk_24.texdb must be provided. There are no names there that could be replaced from c3v1 to c3v1_custom.
Alias Consequence
The TexDB can be byte-for-byte reused, if the generated chunk_26.resources use the same texture keys and the same image names as DLC 3. This saves no files: it remains an approximately 1-GB bundle. Once the resource names are rewritten to c3v1_custom, it is not proven that the old 64-bit texture keys still fit. A key rebuild is not secure without a demonstrated hash function.
tools/probe_texdb.py can check headers, contiguous offsets, single streams, and tile chains, but cannot reconstruct asset names from the TexDB.
Practical Blocker
The current alias prototype intentionally has an empty TexDB. Directly copying the Retail TexDB is technically possible but is approximately 1 GB in size and does not yet prove that a newly named Resource Index correctly references its keys. The reliable next test is therefore an isolated bundle build with unchanged resource names plus complete chunk_24.texdb; a true new map name remains open until the Asset-/texture key mapping is proven.