Files protected against modifications
Nov 27, 2016 7:57:29 GMT
Val E Ryon, Xan, and 2 more like this
Post by eternity on Nov 27, 2016 7:57:29 GMT
The game has a file called "data/signature" (with no extension, you can find it in data1.cpk)
This is a txt files with a list of files and some hashes/signatures. The list includes the bac, and bcm files of the game. The game won't allow any of those files to be modified, and that includes downgrading to an older version of the file.
If you do so, you will get one of those integrity message boxes. This is also the reason why we can't specify bcm/bac files in new characters. (even if they are in original state, they are not in the listed paths of that file).
I 'm thinking of destroying this protection in a future version of xv2patcher, since it is getting in the way of modding (and its original purpose of anti-cheating is totally useless, cheaters have easier methods). But until then, you should know that hexediting those files is futile.
----
Format of every line the signature file:
The path of the file, followed by ";" followed by the sha1 of the file, followed by ";" followed by a 2048 bits number (which is probably related with an asymetric encryption algorithm, if that were the case, this can't be bypassed by modifying that file, it would need patches in xv2patcher).
This is a txt files with a list of files and some hashes/signatures. The list includes the bac, and bcm files of the game. The game won't allow any of those files to be modified, and that includes downgrading to an older version of the file.
If you do so, you will get one of those integrity message boxes. This is also the reason why we can't specify bcm/bac files in new characters. (even if they are in original state, they are not in the listed paths of that file).
I 'm thinking of destroying this protection in a future version of xv2patcher, since it is getting in the way of modding (and its original purpose of anti-cheating is totally useless, cheaters have easier methods). But until then, you should know that hexediting those files is futile.
----
Format of every line the signature file:
The path of the file, followed by ";" followed by the sha1 of the file, followed by ";" followed by a 2048 bits number (which is probably related with an asymetric encryption algorithm, if that were the case, this can't be bypassed by modifying that file, it would need patches in xv2patcher).
