The POD format is used by Terminal Velocity to store much of the game data.
There is no known signature, however POD files do have an identification string which could be used to pick out the file type. It is currently unknown whether the game will work with different strings. The strings are located at offset 4 (just after the UINT32LE containing the file count.) They are null padded and 80 bytes long.
|STARTUP.POD||Startup 1.1 Gold||Stock disk version/shareware startup|
|STARTUP.POD||Startup 1.1 Gold Hires||Cd-rom version startup|
|SHARE.POD||TV 1.2 Shareware||Shareware data|
|DISK.POD||Disk Version 1.1 Gold||Standard diskette data|
|CDROM.POD||TV 1.2 CD-ROM||Cd-rom data|
And here are signatures for fury 3
|STARTUPX.POD||Startup Fury3 Trial Version||fury3 trial startup|
|FURY3X.POD||Fury3 Trial Version Egypt2||fury3 trial data|
|STARTUP.POD||Startup Rel 28||Fury3 startup pod|
|FURY3.POD||Fury3 Rel 26||Fury3 data|
|FURYSE.POD||Furyse with AVI||F!Zone data|
The file begins with the following data:
|UINT32LE numFiles||Number of files in the POD|
|char id||Null-padded file description (see #Signature above)|
Immediately following the header are numFiles file entries.
|char filepath||File name and path (e.g. "ART\ANT0000.RAW")|
|UINT32LE size||File size|
|UINT32LE offset||File offset|
The file data follows the file entries at the offsets indicated.
The following tools are able to work with files in this format.
|Name||Platform||Extract files?||Decompress on extract?||Create new?||Modify?||Compress on insert?||Access hidden data?||Edit metadata?||Notes|
This file format was reverse engineered by Malvineous. If you find this information helpful in a project you're working on, please give credit where credit is due. (A link back to this wiki would be nice too!)