The client always checks the server for every .CAR asset file it needs to open. If the client already has the file in question, it includes an MD5 checksum in the HTTP header. If the checksum does not match the file, it needs to be re-downloaded.
If a checksum does exist, the path and filename of the request is compared to the entries in the file. If it doesn't exist in the list, the file is always assumed to be up to date.
If the checksums do not match, the server begins offering a fresh download.
The line is split at the first equals sign [=].
The left side is a path and file name. Requires internet URL/unix style forward slashes.
The right side is the expected MD5 checksum of the file, wrapped in quotation marks.
Empty lines are ignored.