RomVault appends an incrementing number like _0 to filenames if there is a naming conflict. If the base filename contains periods, this incrementing number is placed in the wrong position instead of at the end of the filename before the extension. It appears RV is looking for the first period in the filename and placing the number immediately before it.
Steps to reproduce:
Place any DAT in your datroot
Modify the dat such that there are two sets with the exact same name. Make sure you have a copy of the files to match this set.
Modify both set names to include multiple periods, like in the screenshot linked below
Scan the files that will match your manual duplicate entry
Find Fixes and Fix ROMs
Notice the incrementing number to mitigate a naming conflict is placed in the wrong position of the archive name
Expected behavior:
(screenshot)
johnsanc
3 years ago
RomVault appends an incrementing number like
_0to filenames if there is a naming conflict. If the base filename contains periods, this incrementing number is placed in the wrong position instead of at the end of the filename before the extension. It appears RV is looking for the first period in the filename and placing the number immediately before it.Steps to reproduce:
Place any DAT in your datroot
Modify the dat such that there are two sets with the exact same name. Make sure you have a copy of the files to match this set.
Modify both set names to include multiple periods, like in the screenshot linked below
Scan the files that will match your manual duplicate entry
Find Fixes and Fix ROMs
Notice the incrementing number to mitigate a naming conflict is placed in the wrong position of the archive name
Expected behavior:
The incrementing number should be placed immediately before the file extension, or at the end of the filename if there is no extension.
(screenshot)