Use relative paths by default
Current NourForge and supported external formats prefer exact relative-path verification when path data is available.
GitHub
NOURFORGE ARCHIVE VERIFY CHECKER · GUIDE
Choose matching behaviour deliberately when one manifest covers multiple discs or files have moved from their original relative paths.
Current NourForge and supported external formats prefer exact relative-path verification when path data is available.
Where supported, an exact filename or exact SHA-256 can help identify a moved file. Relocation is surfaced in results so a PASS does not hide the path difference.
This mode verifies files present on the selected volume while treating manifest entries on other expected volumes as informational rather than failures or warnings.
For a complete archive, missing and extra files are meaningful discrepancies and should remain visible.
Closest-name fallback applies only to supported legacy situations, uses conservative similarity rules and raises warnings. Confirm the actual content evidence before relying on it.
NEED MORE HELP?
Tell us where a guide or workflow can be clearer. Open NourForge Archive Verify Checker support →