file moving and renaming
I am not sure what is your case. If par3 client will search all other directrories on HDD to find moved/renamed files, it will becomes very slow. That is same as calculating hashes/checksums of all files on your HDD... Remember that, as it detect damaged files also, all files were possible to match. I don't know proper English words.
So 16-bit and incomplete recovery is the best i think
I notice that definision of Block and Slice are different. In QuickPar/PAR2, slice and block is same. In current PAR3, slice and block is different. Slice is a virtually splited pieces of source files. Block is a unit of recovery.
My idea is not 32-bit Reed-Solomon. It is difficult to find the position of Partially Damaged Blocks, when the block has one checksum only, and "incomplete recovery" is weaken against shift of data. But, if the one block has multiple-checksums like 4, it is more possible to locate the damaged blocks by using the checksum of complete part. When one block has 4 checksums, total slices becomes max 65536 * 4 simply. Because recovery itself is done by 16-bit RS, memory size may not be problem so much.
yutaka, I hope you are alive after earthshake?
I am safe. Because I was busy, I could not use internet. I live west side of Japan islands and earthquake became weaken on my city. When I felt the eathquake, I did not think so huge damage was happen on north east sea side. I was surprised by watching TV news, too. I am not sure, disaster's side effect will reach to here.