@clockwork42 I know this thread is a few months old but figured out how to do exactly what I believe you are trying to do and I wanted to post it in case you or anyone else is still looking like I was up until recently.
I separated MSU-1 into a distinct system from the rest of SNES called "snesmsu1". Here is what my "/roms/snesmsu1" folder looks like:
For this setup you would also need to make a folder called "snesmsu1" at "/opt/retropie/configs/snesmsu1". You could copy the "snes" folder from "configs" as a starting point. I removed all emulators from "emulators.cfg" except for lr-snes9x and replaced the reference to "snes" with "snesmsu1" so that it looks like this:
I also edit "retroarch.cfg" replacing the reference to "snes" with "snesmsu1" so that it looks like this:
# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line
input_remapping_directory = "/opt/retropie/configs/snesmsu1/"
The crucial part that will make runcommand execute your 'rom.sh' files as scripts instead of trying to open them with the default emulator is the command node in your "es_systems.cfg" file. Here is what my system node for "snesmsu1" looks like, including the command:
With the above in your "es_systems.cfg" and a folder named snesmsu1 in your "roms" folder, you will have a separate section in EmulationStation for SNES MSU-1. You will also have to use a theme that has an "snesmsu1" section. Otherwise, you will have a blank, unthemed section for "snesmsu1".
Only '.sh' files in your "snesmsu1" folder will be displayed in this section in EmulationStation. Notice in my screenshot that the names of all the folders that contain the actual game files begin with a dot which makes them hidden in Linux so they aren't displayed in EmulationStaion. Your "gamelist.xml" file points to one of the '.sh' files in the "path" node for each game and then you can have all your metadata and media set up as well and everything will look pretty in EmulationStation.
Other than that, here is an example of what my 'Chrono Trigger (MSU-1).sh' looks like for launching the game:
Because of the different commands in "es_systems.cfg" for launching regular SNES ROMs vs. running shell scripts, you really do need to separate MSU-1 into a different system from regular SNES. Actually, you could combine them, but if you want to keep things organized as described then you would have to create a similar shell script for each regular SNES ROM as well. I prefer to have them separated for aesthetics, organization and ease of use.
With everything configured as I described, EmulationStation looks nice and tidy and so does my "/roms/snesmsu1" folder. I hope this helps.
@arambecker No my approach would be a bit more.
A tool to find duplicates.
As I said in my first post. If you have selections of several regions.
Maybe 1000 roms it would be usefull to search for a gametitle and to select duplicates.
Game 1 (J)
Game 1 (U)
Game 2 (JUE)
Game 3 (J)
Game 3 (E)
You already programmed delimiter so there needs "just" to generate an automatic search term.
That's not the way your script is intended to work and I think it will need a heavy rework. But this would be usecase, too
ROM Names > Automatic generated search term
Game 1 (J) > Game 1 (
Game 1 (U) > Game 1 (
Game 2 (JUE) > Game 2 (
Game 3 (J) > Game 3 (
Game 3 (E) > Game 3 (