@felice2011 3 and 4 of the diagram is not how xdelta works exactly i could be off but everything before that is spot on bro.i have worked with xdelta a bit and this is how i worked it out and it does work maybe your method is right but lets give all options to the guys :-)
xdelta works by having the original game folder.if there is a update to a game we create a second folder of the original game folder/file we update the game,either folder can be used .
we then point xdelta to the original folder and then point xdelta to the second folder which is updated.then a vdiff patch is made with the difference of the 2 folders.
BAM you have a update :-) which is small compare to some of the patch sizes released.
This also works on Steam games if you have a slow connection and the game has a 5gb or 6gb and a friend can do this xdelta patch for you it could bring the update size down to 500mb and this will not cause account to be banned just as a example.
my problem with the above diagram is the original file/folder,if you going to do a xdelta between the original and repacked the is no base line between the the 2 file/folder one has all the files in its original state and the repacked file/folder has all the extracted files from using quick bms.you going to do a xdelta you basically going to have a patch the size of the original folder/files cause the in no link between any of the files when doing xdelta..
if anyone have some input feedback would be great to see what else xdelta can do.i am not a expert but i was just giving my input.
@Felice & ChronoCross i mean no disrespect to you and the input you have shared. just giving my 2c lol :P
this is the xdelta i am using its have a nice little built script to create the patch in a inno setup.
http://krinkels.org/resources/inno-s...ate?update=626