A non-merged set is the opposite of merged. Every single game—parent, clone, or hack—contains all the required data inside its own ZIP file.
Using the same example: The Street Fighter II: Champion Edition clone in a non-merged set includes a complete copy of the parent's graphics and sound. It does not look for any external files. If you move that ZIP to a folder, it runs immediately.
This is the definition of an FBNeo full non-merged ROM set: A complete collection where every individual game is a standalone, fully-functioning file. fbneo full non-merged rom set
Honesty is crucial. Non-Merged is not perfect for every scenario:
The FBNeo Full Non-Merged set covers many systems. Here are specific notes for the popular ones: A non-merged set is the opposite of merged
Frontends like LaunchBox, RetroArch (with FBNeo core), or EmulationStation cache game lists based on available ROMs. A Non-Merged set ensures that if you add a clone, it is immediately seen as a standalone game without requiring its parent to be present in the database.
A merged set takes the parent ROM and stuffs all the clone data into a single ZIP file. When you open the parent ZIP, you see files for Champion Edition, Turbo, Super Turbo, etc., all inside one archive. The FBNeo Full Non-Merged set covers many systems
Pros: Maximum space efficiency on a per-game basis. Cons: It is impossible to extract a single clone. If you want to share just Super Turbo with a friend, you have to send the entire massive parent file. Frontends often choke on merged sets because they can't distinguish between variations.
Do you have a friend who only wants to play Cadillacs and Dinosaurs and The Simpsons arcade game? With a non-merged set, you simply copy those two specific ZIP files. You do not need to send a 30GB parent archive.