FFXIV Classic Wiki - User contributions [en]

ZiPatch File Structure

2019-06-07T02:44:08Z

Deviltti: /* APFS */

<div style="float:right;">__TOC__</div>

== 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 [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.

== 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 size; // LE
char data[]; // size + 4
unsigned long crc; // CRC32 (RFC 1952) of data
}
</pre>

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>
"NTFS"
"FAT"
"FAT12"
"FAT16"
"FAT32"
"CDFS"
"UDF"
"EXFAT"
</pre>

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>

=== 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.

<pre style="width:60%">
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
};
</pre>

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.

<pre style="width:60%">
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== 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.

<pre style="width:60%">
struct deld_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

ZiPatch File Structure

2019-06-07T02:43:40Z

Deviltti: /* APFS */

<div style="float:right;">__TOC__</div>

== 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 [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.

== 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 size; // LE
char data[]; // size + 4
unsigned long crc; // CRC32 (RFC 1952) of data
}
</pre>

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 types as valid.

<pre>
"NTFS"
"FAT"
"FAT12"
"FAT16"
"FAT32"
"CDFS"
"UDF"
"EXFAT"
</pre>

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>

=== 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.

<pre style="width:60%">
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
};
</pre>

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.

<pre style="width:60%">
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== 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.

<pre style="width:60%">
struct deld_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

ZiPatch File Structure

2019-06-07T02:37:00Z

Deviltti: /* DELD */

<div style="float:right;">__TOC__</div>

== 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 [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.

== 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 size; // LE
char data[]; // size + 4
unsigned long crc; // CRC32 (RFC 1952) of data
}
</pre>

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>

It is unknown whether the following referenced text strings are 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>

=== 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.

<pre style="width:60%">
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
};
</pre>

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.

<pre style="width:60%">
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== 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.

<pre style="width:60%">
struct deld_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

ZiPatch File Structure

2019-06-07T02:34:05Z

Deviltti: /* APFS */

<div style="float:right;">__TOC__</div>

== 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 [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.

== 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 size; // LE
char data[]; // size + 4
unsigned long crc; // CRC32 (RFC 1952) of data
}
</pre>

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>

It is unknown whether the following referenced text strings are 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>

=== 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.

<pre style="width:60%">
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
};
</pre>

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.

<pre style="width:60%">
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

<pre style="width:60%">
struct deld_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

ZiPatch File Structure

2019-06-07T02:28:47Z

Deviltti: /* APLY */

<div style="float:right;">__TOC__</div>

== 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 [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.

== 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 size; // LE
char data[]; // size + 4
unsigned long crc; // CRC32 (RFC 1952) of data
}
</pre>

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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre style="width:60%">
struct apfs_t
{
};
</pre>

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

<pre style="width:60%">
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre style="width:60%">
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
};
</pre>

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.

<pre style="width:60%">
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

<pre style="width:60%">
struct deld_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

ZiPatch File Structure

2019-06-07T02:27:48Z

Deviltti: /* Block Structure */

<div style="float:right;">__TOC__</div>

== 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 [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.

== 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 size; // LE
char data[]; // size + 4
unsigned long crc; // CRC32 (RFC 1952) of data
}
</pre>

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 appear to immediately follow 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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre style="width:60%">
struct apfs_t
{
};
</pre>

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

<pre style="width:60%">
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre style="width:60%">
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
};
</pre>

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.

<pre style="width:60%">
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

<pre style="width:60%">
struct deld_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

ZiPatch File Structure

2019-06-07T02:27:07Z

Deviltti: /* FHDR */

<div style="float:right;">__TOC__</div>

== 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 [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.

== 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 size; // LE
char data[]; // size + 4
unsigned long crc; // CRC32 (RFC 1952) of data
}
</pre>

The slice of 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 appear to immediately follow 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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre style="width:60%">
struct apfs_t
{
};
</pre>

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

<pre style="width:60%">
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre style="width:60%">
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
};
</pre>

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.

<pre style="width:60%">
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

<pre style="width:60%">
struct deld_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

ZiPatch File Structure

2019-06-07T02:25:45Z

Deviltti: /* History */

<div style="float:right;">__TOC__</div>

== 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 [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.

== 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 size; // LE
char data[]; // size + 4
unsigned long crc; // CRC32 (RFC 1952) of data
}
</pre>

The slice of 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 are 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.

<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 appear to immediately follow 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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre style="width:60%">
struct apfs_t
{
};
</pre>

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

<pre style="width:60%">
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre style="width:60%">
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
};
</pre>

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.

<pre style="width:60%">
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

<pre style="width:60%">
struct deld_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

ZiPatch File Structure

2019-06-07T01:12:51Z

Deviltti: /* History */

=== 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 the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre>
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
};
</pre>

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.

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

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T01:11:49Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre>
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
};
</pre>

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.

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

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T01:09:45Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre>
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
};
</pre>

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 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.

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

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T01:09:09Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre>
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
};
</pre>

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 is compressed with the zlib ''Z'' algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T01:08:26Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre>
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
};
</pre>

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 is compressed with the zlib 'Z' algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T01:06:48Z

Deviltti: /* APLY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre>
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' (add); [44 00 00 00] 'D' (delete); [4D 00 00 00] 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // [4E 00 00 00] 'N' (none); [5A 00 00 00] 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
char data[]; // size
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T01:03:07Z

Deviltti: /* File Header */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
struct aply_t
{
int unknown1; // [00 00 00 01]; [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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre>
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' (add); [44 00 00 00] 'D' (delete); [4D 00 00 00] 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // [4E 00 00 00] 'N' (none); [5A 00 00 00] 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
char data[]; // size
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T01:01:46Z

Deviltti: /* APLY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
struct aply_t
{
int unknown1; // [00 00 00 01]; [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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre>
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' (add); [44 00 00 00] 'D' (delete); [4D 00 00 00] 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // [4E 00 00 00] 'N' (none); [5A 00 00 00] 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
char data[]; // size
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T01:01:33Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

<pre>
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' (add); [44 00 00 00] 'D' (delete); [4D 00 00 00] 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // [4E 00 00 00] 'N' (none); [5A 00 00 00] 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
char data[]; // size
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T01:00:09Z

Deviltti: /* APLY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
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 directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

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

struct chunk_t
{
int mode; // 0x41 - 'A' (add); 0x44 - 'D' (delete); 0x4D - 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N' (none); 0x5A - 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
char data[]; // size
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:51:52Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
struct aply_t
{
int unknown1;
int unknown2;
int unknown3;
};
</pre>

The following are observed values for APLY blocks.

<pre>
[00 00 00 01 00 00 00 04 00 00 00 01]
[00 00 00 02 00 00 00 04 00 00 00 01]
</pre>

=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

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

struct chunk_t
{
int mode; // 0x41 - 'A' (add); 0x44 - 'D' (delete); 0x4D - 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N' (none); 0x5A - 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
char data[]; // size
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:50:55Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
struct aply_t
{
int unknown1;
int unknown2;
int unknown3;
};
</pre>

The following are observed values for APLY blocks.

<pre>
[00 00 00 01 00 00 00 04 00 00 00 01]
[00 00 00 02 00 00 00 04 00 00 00 01]
</pre>

=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

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

struct chunk_t
{
int mode; // 0x41 - 'A' (add); 0x44 - 'D' (delete); 0x4D - 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N' (none); 0x5A - 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:46:48Z

Deviltti: /* APLY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 appear to immediately follow the FHDR block.

<pre>
struct aply_t
{
int unknown1;
int unknown2;
int unknown3;
};
</pre>

The following are observed values for APLY blocks.

<pre>
[00 00 00 01 00 00 00 04 00 00 00 01]
[00 00 00 02 00 00 00 04 00 00 00 01]
</pre>

=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

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

struct chunk_t
{
int mode; // 0x41 - 'A' (add); 0x44 - 'D' (delete); 0x4D - 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N' (none); 0x5A - 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified, relative to the installation directory. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:43:22Z

Deviltti: /* APFS */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 ===
=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

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

<pre>
"Total incremental file size: %lld"
"Total incremental disk size: %lld"
"Total incremental max disk size: %lld"
</pre>

=== 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.

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

struct chunk_t
{
int mode; // 0x41 - 'A' (add); 0x44 - 'D' (delete); 0x4D - 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N' (none); 0x5A - 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified, relative to the installation directory. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:42:44Z

Deviltti: /* APFS */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 ===
=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

It is unknown whether the following referenced text strings deal with APFS blocks or APLY blocks.

<pre>
' Total incremental file size: %lld'
' Total incremental disk size: %lld'
' Total incremental max disk size: %lld'
</pre>

=== 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.

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

struct chunk_t
{
int mode; // 0x41 - 'A' (add); 0x44 - 'D' (delete); 0x4D - 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N' (none); 0x5A - 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified, relative to the installation directory. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:39:08Z

Deviltti: /* Block Structure */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
"FHDR"
"APLY"
"APFS"
"ETRY"
"ADIR"
"DELD"
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 ===
=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

=== 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.

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

struct chunk_t
{
int mode; // 0x41 - 'A' (add); 0x44 - 'D' (delete); 0x4D - 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N' (none); 0x5A - 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified, relative to the installation directory. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:38:43Z

Deviltti: /* FHDR */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
FHDR
APLY
APFS
ETRY
ADIR
DELD
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 ===
=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

=== 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.

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

struct chunk_t
{
int mode; // 0x41 - 'A' (add); 0x44 - 'D' (delete); 0x4D - 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N' (none); 0x5A - 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified, relative to the installation directory. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:38:22Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
FHDR
APLY
APFS
ETRY
ADIR
DELD
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 ===
=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

=== 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.

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

struct chunk_t
{
int mode; // 0x41 - 'A' (add); 0x44 - 'D' (delete); 0x4D - 'M' (modify) observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N' (none); 0x5A - 'Z' (zlib) observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified, relative to the installation directory. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:20:58Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
FHDR
APLY
APFS
ETRY
ADIR
DELD
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 ===
=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

=== 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.

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

struct chunk_t
{
int mode; // 0x41 - 'A'; 0x44 - 'D'; 0x4D - 'M' observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N'; 0x5A - 'Z' observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
};
</pre>

The chunk_t mode indicates whether the specific entry file chunk_t will be added, deleted, or modified, relative to the installation directory. 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 is compressed with the zlib algorithm.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:15:57Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
FHDR
APLY
APFS
ETRY
ADIR
DELD
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 ===
=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

=== ETRY ===

ETRY blocks provide the information for ffxivupdater.exe to make changes directly to the filesystem, dependent on the chunk mode.

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

struct chunk_t
{
int mode; // 0x41 - 'A'; 0x44 - 'D'; 0x4D - 'M' observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N'; 0x5A - 'Z' observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
};
</pre>

The chunk mode indicates whether an entry file will be added, deleted, or modified in the installation directory. SHA-1 hashes are used to determine whether the operation was successful.

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:11:35Z

Deviltti: /* ETRY */

=== 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. However, static analysis of the A Realm Reborn executables indicate that they may still be able to read this version.

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 incorrectly 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, each of which provide ffxivupdater.exe with information to carry out specific instructions.
<pre>91 5A 49 50 41 54 43 48 0D 0A 1A 0A ‘ZIPATCH....</pre>

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

The slice of 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>
FHDR
APLY
APFS
ETRY
ADIR
DELD
</pre>

=== FHDR ===

FHDR blocks are 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.

<pre>
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 ===
=== APFS ===

APFS blocks have not been observed directly in ZiPatch files. It is assumed that this may deal with the filesystem in some way.

<pre>
struct apfs_t
{
};
</pre>

=== ETRY ===

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

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

struct chunk_t
{
int type; // 0x41 - 'A'; 0x44 - 'D'; 0x4D - 'M' observed
char prevHash[20]; // SHA-1
char nextHash[20]; // SHA-1
int compressionMode; // 0x4E - 'N'; 0x5A - 'Z' observed
int size; // LE
int prevSize; // LE
int nextSize; // LE
};
</pre>

=== 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>
struct adir_t
{
int pathSize; // LE
char path[]; // pathSize
};
</pre>

=== DELD ===

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

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

ZiPatch File Structure

2019-06-07T00:01:51Z

Deviltti: /* Block Structure */

ZiPatch File Structure

2019-06-07T00:01:35Z

Deviltti: /* Block Structure */

ZiPatch File Structure

2019-06-06T23:54:48Z

Deviltti: /* ADIR */

ZiPatch File Structure

2019-06-06T23:54:33Z

Deviltti: /* DELD */

ZiPatch File Structure

2019-06-06T23:52:54Z

Deviltti: /* Block Structure */

ZiPatch File Structure

2019-06-06T23:48:15Z

Deviltti: /* DELD */

ZiPatch File Structure

2019-06-06T23:46:39Z

Deviltti: /* FHDR */

ZiPatch File Structure

2019-06-06T23:46:30Z

Deviltti: /* ADIR */

ZiPatch File Structure

2019-06-06T23:46:18Z

Deviltti: /* APFS */

ZiPatch File Structure

2019-06-06T23:46:10Z

Deviltti: /* APFS */

ZiPatch File Structure

2019-06-06T23:45:37Z

Deviltti: /* APFS */

ZiPatch File Structure

2019-06-06T23:45:19Z

Deviltti: /* APFS */

ZiPatch File Structure

2019-06-06T23:44:17Z

Deviltti: /* APFS */

ZiPatch File Structure

2019-06-06T23:43:20Z

Deviltti: /* ADIR */

ZiPatch File Structure

2019-06-06T23:43:05Z

Deviltti: /* FHDR */

ZiPatch File Structure

2019-06-06T23:38:32Z

Deviltti: /* ADIR */

ZiPatch File Structure

2019-06-06T23:34:55Z

Deviltti: /* File Header */

ZiPatch File Structure

2019-06-06T23:34:07Z

Deviltti: /* History */

ZiPatch File Structure

2019-06-06T23:31:10Z

Deviltti: /* History */

ZiPatch File Structure

2019-06-06T23:29:52Z

Deviltti: /* History */

ZiPatch File Structure

2019-06-06T23:25:50Z

Deviltti: /* History */