Differences

This shows you the differences between two versions of the page.

--- directory_settings [2024/07/14 01:42] – johnsanc
+++ directory_settings [2025/04/27 15:09] (current) – [Archive Type] johnsanc
@@ Line 1: / Line 1: @@
 ====== DAT Rules ======
-DAT rules allow you to define locations for your ROMs and settings for how you want those ROMs stored. These settings offer a lot of flexibility and control over your collection. To get the most value out of RomVault its best to spend time understanding exactly what options are available and how they work.
+DAT rules allow you to configure how you want your ROMs stored. These settings offer a lot of flexibility and control over your collection. To get the most value out of RomVault its best to spend time understanding exactly what options are available and how they work.
-<WRAP alert>The RomVault UI will allow you map multiple DATs to a single directory. Do NOT map multiple DATs to the same ROM directory. Doing so may result in unintentional file deletions during a fix operation if the "[[global_settings#double_check_delete|Double Check Delete]]" global setting is disabled.</WRAP>
-<WRAP important>Directory rules can only be applied to standard directories, not auto-created virtual directories in the DatRoot. If you place multiple DATs into a single directory, you cannot apply a rule to an individual DAT within that directory. If you need to apply a directory rule to a specific DAT, then the DAT should reside in its own directory in the DatRoot.</WRAP>
 The directory settings can be accessed in two ways:
@@ Line 15: / Line 11: @@
 -----
-===== Rule Path and Directory Location =====
+===== Rule Path =====
-\\
-{{:settings:directory-paths.png?nolink&600 |}}
-\\
 \\
-==== Rule Path ====
 This field is for reference and is not editable. The root of your entire setup is always called "RomVault". "RomVault" is mapped to where ever you keep all of your ROMs.
 This may not seem intuitive at first, but this mapping ensures that the path references to your ROMs are stored in a relative fashion in the cache. For example, lets say you start by storing all your ROMs at ''C:\ROMs\''. At some point in the future you may run out of space on ''C:\'' and you need to move your ROMs to a NAS accessed with a mapped network drive of ''Y:\''. You can make this change to the RomRoot location without needing to rescan all of your ROMs.
-==== Dir Location ====
-The Dir Location is the path to your ROMs. The folder icon allows you to choose the location by browsing.
-The ROM locations can be modified directly in the RomVault config XML. This should not be required unless you want to use the long path syntax or reference a remote server. Examples:
-  * ''Y:\ROMs\''
-  * ''\\?\Y:\ROMs\''
-  * ''%%\\%%Server\Share\''
-  * ''\\?\UNC\Server\Share\''
 -----
 ===== Directory / Merge Rules =====
 \\
-{{:settings:directory-rule-main.png?nolink&600 |}}
+{{:settings:directory-rules.png?nolink&600 |}}
 \\
 \\
-==== Don't Auto Add DAT Directories ====
+==== Don't auto add DAT directories ====
 If two or more DATs share a directory in the DATRoot then RomVault will automatically create a virtual subdirectory for each DAT so they don't conflict with each other. If the "Don't Auto Add DAT Directories" option is __enabled__ then these directories will not be automatically created and the contents of the DATs will be effectively merged together. The result is that all of your ROMs from these DATs will be placed in the same directory.
-<WRAP info>Because this option causes DATs to be merged its likely you may encounter a DAT merge conflict if used haphazardly. This option is only useful under very specific circumstances.</WRAP>
+<WRAP info>Because this option causes DATs to be merged its likely you may encounter a DAT merge conflict if used haphazardly. This option is only useful under very specific circumstances, such as merging No-Intro regular and private DATs, or MAME extras.</WRAP>
 ==== Archive Type ====
 This option allows you to specify your preferred way packaging your ROMs. Options include:
-  * **File** - Sets will be stored uncompressed
+  * **Uncompressed** - Sets will be stored uncompressed
   * **Zip** - Sets will be .zip archives
   * **SevenZip** - Sets will be .7z archives
+  * **Mixed (Archive as File)** - Sets will be mixed types based on what the DAT specifies
+<WRAP info>The Mixed (Archive as File) option is a special setting that changes the scanning behavior. When this option is used, RomVault does not read the contents of 7z or Zip archives and instead hashes the archive itself. This option should only be used with DATs that have hashes of archives such as Scene, GOG, Laserdisc Collection, etc.
+DATs that have ''<romvault forcepacking="fileonly"/>'' in the header will force the **Mixed (Archive as File)** setting unless explicitly overridden by DAT rule.
+</WRAP>
 If a DAT explicitly specifies a forced packing type in its header then that will be used. The **Override DAT** option allows you to override that specification and use your preferred settings instead.
+==== Compression Type ====
+This option allows you to specify your preferred compression type. The options vary depending on the chosen Archive Type. Options include:
+  * Archive Type: Uncompressed
+    * No option
+  * Archive Type: Zip
+    * **Deflate - Trrntzip** - Archives will be compressed to TorrentZip format
+    * **ZSTD** - Archives will be compressed using zstd. The archive structure is the same as TorrentZip but uses zstd instead of Deflate for better compression.
+  * Archive Type: SevenZip
+    * **LZMA Solid - rv7z** - Archives will be compressed solid using the LZMA algorithm, max compression
+    * **LZMA Non-Solid** - Archives will be compressed non-solid using the LZMA algorithm, max compression
+    * **ZSTD Solid** - Archives will be compressed solid using the zstd algorithm, level 19
+    * **ZSTD Non-Solid**- Archives will be compressed non-solid using the LZMA algorithm, level 19
+  * Archive Type: Mixed (Archive as File)
+    * No option
+The **Convert when fixing** option will recompress any archives that do not match your preferred compression type. For example, converting regular Zip archives to TorrentZip format.
+For more information, refer to the [[archive_types|Archive Types]] guide.
 ==== Merge Type ====
 This option allows you to specify your preferred way of merging your ROMs. This is primarily used for MAME DATs. Options include:
@@ Line 85: / Line 91: @@
 ==== Single Archive ====
 Enabling this option will turn the DATs in these directories into single archives. If enabled, this option allows you to specify how to handle subdirectories. The options are:
-  * **Add SubDirs**
+  * **Use subdirs for all sets**
-  * **No SubDirs**
+  * **Do not use subdirs for sets**
-  * **Add SubDirs if conflicts**
+  * **Use subdirs for rom name conflicts**
-  * **Add SubDirs if multiple roms**
+  * **Use subdirs for multi-rom sets**
+  * **Use subdirs for multi-rom sets or set/rom name mismatches**
 This setting is extremely powerful and enables you to build a collection to match TOSEC torrents. It can also be used to create uncompressed sets without requiring subdirectories.
@@ Line 112: / Line 119: @@
 \\
 \\
+==== Add Category Sub Directories ====
+This option will use the category value from each set as a subdirectory. If a set contains multiple category elements, such as with No-Intro DATs, the highest priority category will be used. You can rearrange the category priority. The category subdirectory option is most useful for Redump DATs which have a single category value for every disc, such as Games, Demos, Preproduction, etc.
 ==== Use ID for Numbered DAT Names (No-Intro DATs) ====
-This option will prefix the set name with the value of the id attribute in the DAT. This is typically only applicable for No-Intro DATs that have release numbers.
+This option will prefix the set name with the value of the id attribute of the set. This is typically only applicable for No-Intro DATs that have release numbers.
 ==== Only Keep Complete Sets ====