Differences

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

--- subdirs [2022/01/31 00:01] – johnsanc
+++ subdirs [2025/04/27 04:48] (current) – [Use subdirs for multi-rom sets or set/rom name mismatches] johnsanc
@@ Line 1: / Line 1: @@
 ====== Single Archive Options ======
-RomVault has the ability to store your sets in a variety of ways using the Single Archive option in Directory Settings. This feature is unique to RomVault - no other ROM manager can manipulate the way sets are stored. The examples below demonstrate what each option does.
+RomVault has the ability to store your sets in a variety of ways using the Single Archive option in DAT Rules. This feature is unique to RomVault - no other ROM manager can manipulate the way sets are stored. The most common use case for Single Archives is to bundle potentially thousands of small ROMs into a single zip.
-Assume a DAT with the following games:
+The examples below demonstrate what each option does. Assume a fictitious DAT with the following games:
 <code>
@@ Line 40: / Line 40: @@
 </code>
-===== Add SubDirs =====
-This will put every ROM into a parent directory using the set name. This is the traditional way ROM managers store sets.
-  * game1/game1.rom
-  * game2/game2.rom
-  * game3/file1.rom
-  * game3/file2.rom
-  * game4/file1.rom
-  * game4/file2.rom
-  * game4/file3.rom
-  * game5/game1.rom
+===== Use subdirs for all sets =====
+This will put every ROM into a subdirectory using the set name.
-===== No SubDirs =====
+  * ''game1/game1.rom''
+  * ''game2/game2.rom''
+  * ''game3/file1.rom''
+  * ''game3/file2.rom''
+  * ''game4/file1.rom''
+  * ''game4/file2.rom''
+  * ''game4/file3.rom''
+  * ''game5/game1.rom''
+<WRAP tip>TOSEC rom sets are often packaged using this **Use subdirs for all sets** single archive method. This drastically reduces the number of files making it ideal for archiving collections that are updated infrequently.</WRAP>
+===== Do not use subdirs for sets =====
 This will put every ROM into the base directory. If there are any ROM name conflicts, the ROMs will be renamed by appending an underscore character and an incrementing number. This setting is generally only useful if you know the DAT does not have any name conflicts across ROMs.
-  * file1.rom
+  * ''file1.rom''
-  * file1_0.rom
+  * ''file1_0.rom''
-  * file2.rom
+  * ''file2.rom''
-  * file2_0.rom
+  * ''file2_0.rom''
-  * file3.rom
+  * ''file3.rom''
-  * game1.rom
+  * ''game1.rom''
-  * game1_0.rom
+  * ''game1_0.rom''
-  * game2.rom
+  * ''game2.rom''
+===== Use subdirs for rom name conflicts =====
+This will put every ROM into the base directory, however if there are ROM name conflicts across sets then those sets will be stored in subdirectories. This setting is useful if you prefer no subdirectories, but want to be certain you do not run into any scenarios where ROMs are renamed with an incrementing number.
+  * ''game1/game1.rom''
+  * ''game2.rom''
+  * ''game3/file1.rom''
+  * ''game3/file2.rom''
+  * ''game4/file1.rom''
+  * ''game4/file2.rom''
+  * ''game4/file3.rom''
+  * ''game5/game1.rom''
+===== Use subdirs for multi-rom sets =====
+This will put ROMs into set subdirectories if the set contains multiple ROMs. All other ROMs will be placed in the base directory. Naming conflicts are handled by appending an incrementing number to the file name. This option is useful in combination with the "file" archive type for DATs that are predominately very large and poorly compressible single-file sets.
+  * ''game1.rom''
+  * ''game2.rom''
+  * ''game3/file1.rom''
+  * ''game3/file2.rom''
+  * ''game4/file1.rom''
+  * ''game4/file2.rom''
+  * ''game4/file3.rom''
+  * ''game1_0.rom''
+<WRAP tip>The **Do not use subdirs for sets** and **Use subdirs for multi-rom sets** settings can be used in conjunction with the **Uncompressed** archive type to store uncompressed single-file sets without subdirectories, such as PS3 ISOs.</WRAP>
-===== Add SubDirs if conflicts =====
+===== Use subdirs for multi-rom sets or set/rom name mismatches =====
-This will put every ROM into the base directory, however if there are any ROM name conflicts whatsoever then this setting falls back to "Add SubDirs" behavior for the entire DAT. This setting is useful if you prefer no subdirectories, but want to be certain you do not run into any scenarios where ROMs are renamed with an incrementing number.
+This will put ROMs into set subdirectories if the set contains multiple ROMs or if the rom name does not match the set name. This is a useful setting for DATs that contain poorly named ROMs, or DATs of files extracted from media.
-  * game1/game1.rom
-  * game2/game2.rom
-  * game3/file1.rom
-  * game3/file2.rom
-  * game4/file1.rom
-  * game4/file2.rom
-  * game4/file3.rom
-  * game5/game1.rom
+  * ''game1.rom''
+  * ''game2.rom''
+  * ''game3/file1.rom''
+  * ''game3/file2.rom''
+  * ''game4/file1.rom''
+  * ''game4/file2.rom''
+  * ''game4/file3.rom''
+  * ''game5/game1.rom''
-===== Add SubDirs if multiple roms =====
+<WRAP tip>The **Use subdirs for multi-rom sets or set/rom name mismatches** setting can be used in most cases and is effectively a combination of the previous settings. It ensures no ROM names are modified due to name conflicts, bundles ROMs together in sets where applicable, and keeps the directory structure as shallow as possible.</WRAP>
-This will put ROMs into the base directory if the following conditions are met:
-  * The set must consist of a single ROM only
-  * The set name must match the ROM name (case sensitive) minus the file extension
-All other ROMs will be placed in subdirectories using the set name. This option is useful in combination with the "file" archive type for DATs that are predominately very large and poorly compressible single-file sets.
-  * game1.rom
-  * game2.rom
-  * game3/file1.rom
-  * game3/file2.rom
-  * game4/file1.rom
-  * game4/file2.rom
-  * game4/file3.rom
-  * game5/game1.rom