merge_types
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
merge_types [2021/11/29 14:48] – johnsanc | merge_types [2023/07/04 15:36] (current) – johnsanc | ||
---|---|---|---|
Line 3: | Line 3: | ||
{{ : | {{ : | ||
+ | |||
+ | |||
+ | ===== Non-Merged Set ===== | ||
+ | A non-merged set contains absolutely everything necessary for a given game to run packaged in a single folder or archive. Every game is completely independent from any other game. | ||
+ | |||
+ | A non-merged set is ideal for those who only want to use specific games on their PC, Raspberry Pi, etc. Since all games are self-contained, | ||
+ | |||
+ | <WRAP info> | ||
+ | |||
+ | ===== Split Set ===== | ||
+ | A split set is one where the parent set contains all of the normal data it should, and the clone sets contain only what has changed as compared to the parent set. This saves some space, but isn’t quite as efficient as a merged set. The clone sets can't operate without their parent set. | ||
+ | |||
+ | <WRAP info>The parent and clones in split sets do not include BIOS or DEVICE files - they are separate files within the set. This is per MAME design. For example: 100lions.zip, | ||
+ | |||
+ | |||
+ | ===== Merged Set ===== | ||
+ | A merged set takes the parent set and its clone sets and puts them all inside the parent set's folder or archive. Using Pac-Man as an example: A merged set takes the Puckman, Midway Pac-Man (USA) sets, along with various bootleg versions, and combines it all into puckman.zip (the parent' | ||
+ | |||
+ | <WRAP info>The parent games in a merged set do not include BIOS or DEVICE files - they are separate files within the set. This is per MAME design. For example: 100lions.zip, | ||
+ | |||
+ |
merge_types.1638197313.txt.gz · Last modified: 2021/11/29 13:48 (external edit)