Skip to content

Verify

Jump to bottom
Matt Nadareski edited this page Sep 19, 2025 · 10 revisions

Verify from DAT

Flags: -ve, --verify

When used, this will use an input DAT or set of DATs to blindly check against an input folder. The base of the folder is considered the base for the combined DATs and games are either the directories or archives within. This will only do a direct verification of the items within and will create a fixdat afterwards for missing files.

Options

Flags Short Description Long Description
-dat=, --dat= Input DAT to be used User-supplied DAT for use in all operations. Multiple instances of this flag are allowed.
-dep, --depot Assume directories are romba depots Normally, input directories will be treated with no special format. If this flag is used, all input directories will be assumed to be romba-style depots.
--depd, --depot-depth Set depth of depot for inputs Requires -dep, --depot. Optionally, set the depth of input depots. Defaults to 4 deep otherwise.
-out=, --output-dir= Set output directory This sets an output folder to be used when the files are created. If a path is not defined, the runtime directory is used instead.
-ho, --hash-only Check files by hash only This sets a mode where files are not checked based on name but rather hash alone. This allows verification of (possibly) incorrectly named folders and sets to be verified without worrying about the proper set structure to be there.
-qs, --quick Enable quick scanning of archives For all archives, if this flag is enabled, it will only use the header information to get the archive entries' file information. The upside to this is that it is the fastest option. On the downside, it can only get the CRC and size from most archive formats, leading to possible issues.
-h=, --header= Set a header skipper to use, blank means all Set the header special field for the output DAT(s). In file rebuilding, this flag allows for either all copier headers (using "") or specific copier headers by name (such as "fds.xml") to determine if a file matches or not. See Copier Headers for more information.
-caf, --aaruformats-as-files Treat AaruFormats as regular files Normally, AaruFormats would be processed using their internal hash to compare against the input DATs. This flag forces all AaruFormats to be treated like regular files.
-ic, --chds-as-files Treat CHDs as regular files Normally, CHDs would be processed using their internal hash to compare against the input DATs. This flag forces all CHDs to be treated like regular files.
-ind, --individual Process input DATs individually In cases where DATs would be processed in bulk, this flag allows them to be processed on their own instead.
-dm, --dat-merged Force creating merged sets Preprocess the DAT to have parent sets contain all items from the children based on the cloneof tag. This is incompatible with the other --dat-X flags. See Merging Modes for more details.
-dfm, --dat-full-merged Force creating fully merged sets Preprocess the DAT to have parent sets contain all items from the children based on the cloneof tag while also performing deduplication within a parent. This is incompatible with the other --dat-X flags. See Merging Modes for more details.
-ds, --dat-split Force creating split sets Preprocess the DAT to remove redundant files between parents and children based on the romof and cloneof tags. This is incompatible with the other --dat-X flags. See Merging Modes for more details.
-dnd, --dat-device-non-merged Create device non-merged sets Preprocess the DAT to have child sets contain all items from the device references. This is incompatible with the other --dat-X flags. See Merging Modes for more details.
-dnm, --dat-non-merged Force creating non-merged sets Preprocess the DAT to have child sets contain all items from the parent set based on the romof and cloneof tags. This is incompatible with the other --dat-X flags. See Merging Modes for more details.
-df, --dat-full-non-merged Create fully non-merged sets Preprocess the DAT to have child sets contain all items from the parent sets based on the cloneof and romof tags as well as device references. This is incompatible with the other --dat-X flags. See Merging Modes for more details.
-ini=, --extra-ini= Apply a MAME INI for given field Apply any valid MAME INI for any valid field in the DatFile. Multiple instances of this flag are allowed. See Extras for more information.
-fi=, --filter= Filter a game/rom field with the given value(s) Filter any valid item or machine field from inputs. See Filters for more information.
-ofg, --match-of-tags Allow cloneof and romof tags to match game name filters Requires -fi=, --filter=. If filter or exclude by game name is used, this flag will allow those filters to be checked against the romof and cloneof tags as well. This can allow for more advanced set-building, especially in arcade-based sets.

Examples

There are currently no examples

Clone this wiki locally