UFOvfs is a utility for working with the virtual file system(VFS) used to hold the data for UFO: Aftermath.
UFOvfs can perform the following actions:
ufovfs action [-options] vfsname [header | outdirectory] [files]
c vfsname files | - create filesystem with the size required to hold files |
a vfsname files | - add files or directories into filesystem |
x vfsname [files] | - extract files or directories from filesystem |
l vfsname [directories] | - list filesystem directories |
5 vfsname | - count MD5 sum for filesystem |
m vfsname | - check MD5 sum of filesystem |
n vfsname header | - set VFS header |
z | - compress data while adding |
d | - add just content of the command line directories |
5 | - count MD5 sum (for adding and joining) |
o | - outdirectory parameter is after vfsname (for extracting only) |
h | - header parameter is after vfsname (for adding) |
w | - overwrite existing files (for adding and extracting) |
t | - truncate existing filesystem (for adding only) |
0 | - no problems |
-1 | - there were some problems |
To create a VFS you have to know what files it will hold. The ufovfs utility checks these files for the size and then creates the VFS to hold them. At this phase the files need not be in the right directory structure and the files need not to be the ones which will be finaly added into the VFS. The matter is the size.
Action letter: c
Possible options: none
Parameters: vfsname, directories or filenames to check the size
Example:
ufovfs c gamedata.vfs strategic/textures tactical/configs/game/listofweapons.txt share/sound/wavs
You can extract the whole VFS, any directory or any file from the VFS. Files are extracted to the same directory structure they have in the VFS. You can specify the directory the files will be extracted to. By default the existing files are not overwritten.
Action letter: x
Possible options: o, w
Parameters: vfsname, outdirectory, directories or files for extraction
Example:
ufovfs x -ow gamedata.vfs output strategic/textures tactical/configs/game/listofweapons.txt share/sound/wavs
You can add directories or files into the VFS. The VFS must exist. An existing filesystem could be truncated before adding to avoid overwrites. By default the existing files in the VFS are not overwritten. You can assign a directory in which the data for adding are placed and only the structure inside this directory will be added. Files could be compressed while adding. You can count the MD5 sum after adding. You can assign a header to the VFS before adding. The header can have 255 characters maximaly.
Action letter: a
Possible options: d, z, 5, h, t
Parameters: vfsname, header, output directory, directories or filenames to add
Example:
ufovfs a -z5h gamedata.vfs "testing data" strategic/textures tactical/configs/game/listofweapons.txt share/sound/wavs
ufovfs a -d gamedata.vfs data
You can list the whole VFS or any directory in the VFS.
Action letter: l
Possible options: none
Parameters: vfsname, directories
Example:
ufovfs l gamedata.vfs strategic/textures share/sound/wavs
You can count the MD5 sum of the VFS. Note that you should count it after adding of all the files otherwise the sum won't be correct.
Action letter: 5
Possible options: none
Parameters: vfsname
Example:
ufovfs 5 gamedata.vfs
You can check whether the MD5 sum of the VFS is correct.
Action letter: m
Possible options: none
Parameters: vfsname
Example:
ufovfs m gamedata.vfs
You can assign a header to the VFS. The header is just a name of the VFS; it has no special usage. The header can be 255 characters long maximum.
Action letter: n
Possible options: none
Parameters: vfsname, header
ufovfs n gamedata.vfs "testing data"
Prev: none | Next: UFObintxt | Up: Home |