Difference between revisions of "ZiPatch File Structure"

From FFXIV Classic Wiki
Jump to: navigation, search
m (APFS)
 
(75 intermediate revisions by 2 users not shown)
Line 1: Line 1:
All ZiPatch files for FINAL FANTASY XIV share the same overall structure. This format was later expanded in 2012 for DRAGON QUEST X and FINAL FANTASY XIV: A Realm Reborn, which are more similar in their DAT structure. Many of the block types found in this version were deprecated, but still remain in the executable for A Realm Reborn.
+
<div style="float:right;">__TOC__</div>
  
ZiPatch File Header
+
== History ==
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A            ‘ZIPATCH....</pre>
 
  
The ZiPatch File Header is followed immediately by ''n'' blocks, which each carry specific instructions.
+
ZiPatch (.patch) files are a compressed file format for FINAL FANTASY XIV. This file format was later modified in 2012 for DRAGON QUEST X and FINAL FANTASY XIV: A Realm Reborn, which are more similar in their DAT structure to each other than to FINAL FANTASY XIV. As such, many of the block types that are found in this version have been deprecated. Static analysis of their executables indicate that they may still be able to read this version.
  
<pre>
+
Initial, minimal research of the ZiPatch file format was made publically available [https://github.com/jpd002/SeventhUmbral/blob/master/launcher/PatchFile.cpp] in 2013 by Jean-Philip Desjardins for his open-source server emulator for FINAL FANTASY XIV, SeventhUmbral [http://seventhumbral.org/]. This implementation allowed the ZiPatch files that were backed up by Krizz [http://tehkrizz.net/] and others in the community to be applied to a new installation and improperly update the client to 1.23b.
[StructLayout(LayoutKind.Sequential, Pack=4)]
+
 
struct Block
+
== File Header ==
 +
ZiPatch files have a unique file header (12 bytes), which is used to identify the file format. The ZiPatch File Header is immediately followed by ''n'' blocks, read until EOF, each of which provide ffxivupdater.exe with information to carry out specific instructions.
 +
<pre style="width:60%">91 5A 49 50 41 54 43 48 0D 0A 1A 0A            ‘ZIPATCH....</pre>
 +
 
 +
 
 +
 
 +
 
 +
== Block Structure ==
 +
<pre style="width:60%">
 +
struct block_t
 
{
 
{
     int dataSize; // Little Endian
+
     int size;         // LE
     byte[] data; // data.Length is dataSize + 4 (inclusive of block type identifier)
+
     char data[];       // size + 4
     [MarshalAs(UnmanagedType.ByValArray, SizeConst=4)]
+
     unsigned long crc; // CRC32 (RFC 1952) of data
    byte[] crc;   // crc is a standard CRC32 checksum (RFC 1952) of data
 
 
}
 
}
 
</pre>
 
</pre>
  
The block type identifier is indicated by the slice of data[0..3]. Analysis of ffxivupdater.exe indicates the following block types as valid:
+
The slice, data[0..3], is a string used to identify the block type. Static analysis of ffxivupdater.exe indicates the following block types as valid.
 +
 
 +
<pre style="width:60%">
 +
"FHDR"
 +
"APLY"
 +
"APFS"
 +
"ETRY"
 +
"ADIR"
 +
"DELD"
 +
</pre>
 +
 
 +
 
 +
=== FHDR ===
 +
 
 +
FHDR blocks provide an abstract of the changes that should occur as a result of applying the ZiPatch in terms of the type and count of the changes to be made to the filesystem.
 +
 
 +
<pre style="width:60%">
 +
struct fhdr_t
 +
{
 +
    char version[4];  // [00 00 02 00] observed; Static analysis of ffxivupdater.exe indicates FileHeaderV2
 +
    char result[4];  // "DIFF" or "HIST" observed
 +
    int numEntryFile; // LE
 +
    int numAddDir;    // LE
 +
    int numDeleteDir; // LE
 +
};
 +
</pre>
 +
 
 +
=== APLY ===
 +
 
 +
APLY blocks have not been reversed. Two APLY blocks always appear immediately after the FHDR block.
 +
 
 +
<pre style="width:60%">
 +
struct aply_t
 +
{
 +
    int unknown1; // [00 00 00 01] and [00 00 00 02] observed
 +
    int unknown2; // [00 00 00 04] observed
 +
    int unknown3; // [00 00 00 01] observed
 +
};
 +
</pre>
 +
 
 +
=== APFS ===
 +
 
 +
APFS blocks have not been observed. While unknown, it is assumed that APFS blocks may deal with the filesystem architecture in some way.
 +
 
 +
<pre style="width:60%">
 +
struct apfs_t
 +
{
 +
};
 +
</pre>
 +
 
 +
Static analysis of ffxivupdater.exe indicates the following filesystem architectures as valid.
  
<pre>
+
<pre style="width:60%">
FHDR // File Header; observed
+
"NTFS"
APLY // Unknown; observed
+
"FAT"
APFS // Unknown; not observed
+
"FAT12"
ETRY // Entry File; observed
+
"FAT16"
ADIR // Add Directory; observed
+
"FAT32"
DELD // Delete Directory; observed
+
"CDFS"
 +
"UDF"
 +
"EXFAT"
 
</pre>
 
</pre>
  
The File Header block is a summary of the changes that will take place as a result of applying the ZiPatch.
+
It is unknown whether the following referenced text strings are also involved with APFS blocks.
 +
 
 +
<pre style="width:60%">
 +
"Total incremental file size: %lld"
 +
"Total incremental disk size: %lld"
 +
"Total incremental max disk size: %lld"
 +
</pre>
  
[StructLayout(LayoutKind.Sequential, Pack=4, Size=20)]
+
=== ETRY ===
struct FileHeader
+
 
 +
ETRY blocks provide the information for ffxivupdater.exe to make changes directly to the filesystem by performing explicit operations on the specified file path, relative to the installation directory. The operation is dependent on the chunk_t mode.
 +
 
 +
<pre style="width:60%">
 +
struct etry_t
 
{
 
{
     [MarshalAs(UnmanagedType.ByValArray, SizeConst=4)]
+
     int pathSize;    // LE
     byte[] _version;         // version format is unknown, but may be major/minor. Analysis of ffxivupdater.exe indicates the string FileHeaderV2
+
    char path[];      // pathSize
 +
     int count;        // LE
 +
    chunk_t chunks[]; // count
 +
};
  
     [MarshalAs(UnmanagedType.ByValArray, SizeConst=4)]
+
struct chunk_t
     byte[] _result;         // DIFF or HIST observed
+
{
 +
     int mode;            // [41 00 00 00] 'A'; [44 00 00 00] 'D'; [4D 00 00 00] 'M' observed
 +
     char prevHash[20];   // SHA-1
 +
    char nextHash[20];  // SHA-1
 +
    int compressionMode; // [4E 00 00 00] 'N' and [5A 00 00 00] 'Z' observed
 +
    int size;            // LE
 +
    int prevSize;        // LE
 +
    int nextSize;        // LE
 +
    char data[];        // size
 +
};
 +
</pre>
  
    int _numEntryFile;      // Little Endian
+
The chunk_t mode indicates whether the specific entry file chunk_t will be added ''A'', deleted ''D'', or modified ''M''. In order to validate the operation, SHA-1 hashes are used to verify file deltas. The chunk_t compressionMode indicates whether the specific entry file chunk_t has no compression ''N'' or is compressed with the zlib algorithm ''Z''.
     int _numAddDirectory;   // Little Endian
+
 
     int _numDeleteDirectory; // Little Endian
+
=== ADIR ===
}
+
 
 +
ADIR blocks provide the information for ffxivupdater.exe to make changes directly to the filesystem by creating a new directory for the specified path, relative to the installation directory, if it does not already exist.
 +
 
 +
<pre style="width:60%">
 +
struct adir_t
 +
{
 +
     int pathSize; // LE
 +
     char path[]; // pathSize
 +
};
 
</pre>
 
</pre>
  
>>ADIR
+
=== DELD ===
uint pathSize (Little Endian)
+
 
byte path[pathSize]
+
DELD blocks provide the information for ffxivupdater.exe to make changes directly to the filesystem by deleting the directory for the specified path, relative to the installation directory, if it exists.
  
>>DELD
+
<pre style="width:60%">
uint pathSize (Little Endian)
+
struct deld_t
byte path[pathSize]
+
{
 +
    int pathSize; // LE
 +
    char path[];  // pathSize
 +
};
 +
</pre>

Latest revision as of 19:17, 8 June 2019

History

ZiPatch (.patch) files are a compressed file format for FINAL FANTASY XIV. This file format was later modified in 2012 for DRAGON QUEST X and FINAL FANTASY XIV: A Realm Reborn, which are more similar in their DAT structure to each other than to FINAL FANTASY XIV. As such, many of the block types that are found in this version have been deprecated. Static analysis of their executables indicate that they may still be able to read this version.

Initial, minimal research of the ZiPatch file format was made publically available [1] in 2013 by Jean-Philip Desjardins for his open-source server emulator for FINAL FANTASY XIV, SeventhUmbral [2]. This implementation allowed the ZiPatch files that were backed up by Krizz [3] and others in the community to be applied to a new installation and improperly update the client to 1.23b.

File Header

ZiPatch files have a unique file header (12 bytes), which is used to identify the file format. The ZiPatch File Header is immediately followed by n blocks, read until EOF, each of which provide ffxivupdater.exe with information to carry out specific instructions.

91 5A 49 50 41 54 43 48 0D 0A 1A 0A            ‘ZIPATCH....



Block Structure

struct block_t
{
    int size;          // LE
    char data[];       // size + 4
    unsigned long crc; // CRC32 (RFC 1952) of data
}

The slice, data[0..3], is a string used to identify the block type. Static analysis of ffxivupdater.exe indicates the following block types as valid.

"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"


FHDR

FHDR blocks provide an abstract of the changes that should occur as a result of applying the ZiPatch in terms of the type and count of the changes to be made to the filesystem.

struct fhdr_t
{
    char version[4];  // [00 00 02 00] observed; Static analysis of ffxivupdater.exe indicates FileHeaderV2
    char result[4];   // "DIFF" or "HIST" observed
    int numEntryFile; // LE
    int numAddDir;    // LE
    int numDeleteDir; // LE
};

APLY

APLY blocks have not been reversed. Two APLY blocks always appear immediately after the FHDR block.

struct aply_t
{
    int unknown1; // [00 00 00 01] and [00 00 00 02] observed
    int unknown2; // [00 00 00 04] observed
    int unknown3; // [00 00 00 01] observed
};

APFS

APFS blocks have not been observed. While unknown, it is assumed that APFS blocks may deal with the filesystem architecture in some way.

struct apfs_t
{
};

Static analysis of ffxivupdater.exe indicates the following filesystem architectures as valid.

"NTFS"
"FAT"
"FAT12"
"FAT16"
"FAT32"
"CDFS"
"UDF"
"EXFAT"

It is unknown whether the following referenced text strings are also involved with APFS blocks.

"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"

ETRY

ETRY blocks provide the information for ffxivupdater.exe to make changes directly to the filesystem by performing explicit operations on the specified file path, relative to the installation directory. The operation is dependent on the chunk_t mode.

struct etry_t
{
    int pathSize;     // LE
    char path[];      // pathSize
    int count;        // LE
    chunk_t chunks[]; // count
};

struct chunk_t
{
    int mode;            // [41 00 00 00] 'A'; [44 00 00 00] 'D'; [4D 00 00 00] 'M' observed
    char prevHash[20];   // SHA-1
    char nextHash[20];   // SHA-1
    int compressionMode; // [4E 00 00 00] 'N' and [5A 00 00 00] 'Z' observed
    int size;            // LE
    int prevSize;        // LE
    int nextSize;        // LE
    char data[];         // size
};

The chunk_t mode indicates whether the specific entry file chunk_t will be added A, deleted D, or modified M. In order to validate the operation, SHA-1 hashes are used to verify file deltas. The chunk_t compressionMode indicates whether the specific entry file chunk_t has no compression N or is compressed with the zlib algorithm Z.

ADIR

ADIR blocks provide the information for ffxivupdater.exe to make changes directly to the filesystem by creating a new directory for the specified path, relative to the installation directory, if it does not already exist.

struct adir_t
{
    int pathSize; // LE
    char path[];  // pathSize
};

DELD

DELD blocks provide the information for ffxivupdater.exe to make changes directly to the filesystem by deleting the directory for the specified path, relative to the installation directory, if it exists.

struct deld_t
{
    int pathSize; // LE
    char path[];  // pathSize
};