Difference between revisions of "DAZIP"

From Dragon Age Toolset Wiki
Jump to: navigation, search
Line 1: Line 1:
 
DAZIP files are packages of [[export]]ed resources ready to be installed and loaded into the Dragon Age game. The format is actually just a renamed ZIP file, and can be opened by any zip editor to manually extract or manipulate the contents.
 
DAZIP files are packages of [[export]]ed resources ready to be installed and loaded into the Dragon Age game. The format is actually just a renamed ZIP file, and can be opened by any zip editor to manually extract or manipulate the contents.
  
Inside are the exported binary resources for a module, packaged into ERFs and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.
+
Inside are the exported binary resources for a module, packaged into [[ERF]]s and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.
 +
 
 +
== Known issues ==
 +
 
 +
Certain types of file are not packaged into ERFs and may be omitted from the DAZIP file by the current builder-to-player packaging process. Known examples include TGA files and BIK files. If you're using these sorts of resources you can manually insert them into the DAZIP file using any standard ZIP-editing program.
  
 
[[Category:File types]]
 
[[Category:File types]]

Revision as of 23:48, 16 September 2009

DAZIP files are packages of exported resources ready to be installed and loaded into the Dragon Age game. The format is actually just a renamed ZIP file, and can be opened by any zip editor to manually extract or manipulate the contents.

Inside are the exported binary resources for a module, packaged into ERFs and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.

Known issues

Certain types of file are not packaged into ERFs and may be omitted from the DAZIP file by the current builder-to-player packaging process. Known examples include TGA files and BIK files. If you're using these sorts of resources you can manually insert them into the DAZIP file using any standard ZIP-editing program.