Repository navigation
Validate Datfile shows issues for folder entries #2
Description
Hi, when creating a Dat using these options:
The resulting Datfile doesn't pass the built-in validator and shows a lot of errors for the folders:
Something is wrong here, either the validator should skip over these entries and not report an issue or the Creator Studio should create these lines with the required attribute so that it passes.
Activity
Eggmansworld commentedon Jul 27, 2026
I would need to see a generated datfile that throws these validator errors. I would want to inspect it to see if the default sha1 value for a placeholder folder is present or absent. Provide that, and we can move this forward.
Eggmansworld commentedon Jul 27, 2026
Thanks for reporting this. You framed the options exactly right, and the first one was correct: the validator should skip these.
A rom name ending in
/is a directory marker — it records that a folder exists rather than describing a file. RomVault writes these itself, with a zero size and CRC and no other hashes, so requiring a sha1 of them was reporting a problem that was not one. The "Grouped + Folders" structure produces them by design, which is why you saw so many.The fix: directory entries are exempt from the required-attribute check, while any values they do carry are still validated.
Testing: a dat mixing good roms, valid folder markers, a folder marker with a malformed CRC, a rom missing its sha1, and a rom with a malformed CRC — the three real problems are still reported and the valid markers no longer are.
Fixed in v0.1.5.
Stop the validator reporting folder entries as broken