This topic was archived here:

https://web.archive.org/web/20230000000000fw_/https://www.zenhax.com/viewtopic.php?t=5002

dsdude123, posted Sun Sep 24, 2017 6:40 pm (26783)

---

Hi all,

Apologies in advance if this is in the wrong section, I have a somewhat unusual request so I wasn't sure whether this would belong in this section or "Help with QuickBMS & tools". I was wondering if anyone knew of any documentation for the TT Games DAT format. What I'm looking for in particular is information on the layout of the file such as "X bytes for the header, etc." I've tried to work it out myself with the script for extracting the files but I'm getting stuck on parts of the script such as the get commands (such as "get FILES long MEMORY_FILE") as for I'm not sure how this function works. In example, for the line "get FILES long MEMORY_FILE", how does QuickBMS know how many bytes to read from the file to get this value? I've tried looking at the QuickBMS documentation but so far I haven't found the answer I'm looking for.

If anyone could provide any information on where I could find such documentation or provide me with information on how the get function works that would be great. My goal with this information is to write a repacker tool for this format.

Thanks,
dsdude123

aluigi, posted Sun Sep 24, 2017 8:01 pm (26786)

---

It's a very complex format composed by various versions of the archive format.
Keep in mind that writing a rebuilder means you must focus on one of these versions.

The "get FILES long MEMORY_FILE" instruction means: read the 32bit field FILES from the header, in fact MEMORY_FILE contains the whole information table read from the file.
I suggest you to run quickbms with the -V option to have a full log of the data read from the file and the offsets:

Code:

quickbms.exe -0 -V ttgames.bms file.dat > log.txt