Compressed Archives

RoM-Jacket offers the ability to identify and extract compressed archives in your library.
Extracted archives are moved into the RJ-Sorting folder.
Many emulators can read ZIP archives without difficulty, however 7Zip and RAR archives must be extracted before use.
RoM-Jacket "explodes" archives: folders are ignored and all files are extracted to a single directory.
Any archives will be extracted prior to any folder creation. This will use the archive name for folder creation and each archive will be extracted into a folder of its name. This will use the archive name for folder creation and will not be extracted.

Consolidate vs. Individuate

This will consolidate ROMs containing the same base-name and will group "duplicate" ROMs and multi-disc ROMs together. Effectively, this will help eliminate the need to scroll through many different versions of games in a library and will help wrangle multi-disc games. This is the preferred method of folder-generation for users wishing to tame their library and generate friendly-names for their frontend. This will simply give a folder to each ROM found. This is the preferable method of folder-generation for users wishing to configure the Hyperspin Frontend using proprietary XML tools.

Xpadder / antiMicro Profiles

***If you wish to control your frontend with a joystick using RoM-Jacket, a profile must be created for each game***
Emulators in the factory state will map keyboard keys to the system's buttons and joystick directions. RoM-Jacket can create profiles for these keys as they correspond to the native joystick layout of the machine. If the chosen console is a custom/unsupported system, a generic and multipurpose configuration is created. causes an empty profile to be created for each game to disable xpadder/antimicro while the emulator is running. When the game exits, Xpadder/antimicro loads the MediaCenter profile to resume control of the frontend. This is desirable for users who are processing a console with a custom emulator. You may choose to create a profile for your system and propagate it through the console's library using the Config Utility This is the default option for RoM-Jacket and creates a profile with only Emulator functionality mappings such as "Save/Load State" "Reset" "Exit/Power OFF" and unique functions such as "Rewind/Fast-forward. Emulators are configured to use directinput/xinput (XBOX 360 Joystick mappings).

Custom Emulators and Consoles

This wizard is preconfigured for many compatible emulators

If you have a console not identified by RoM-Jacket, wish to assign an alternative emulator to a console such as retroArch/MESS, or wish use an emulator unsupported by RoM-jacket, a simple GUI wizard is provided to assist in creating launchers.
Most emulators should not need to use this option, however some emulators require that the emulator be executed from its directory.
Most often, emulators require the full path of the ROM including the extension when launching a ROM:
"\..\Emulator.exe" -option "C:\Games\Console\Custom Console Name\Rom Name\Rom.ext"
Emulators often use simply the name of the file without the path extension included when launching. In this case use "ROM".
"..\Emulator.exe" -option ROM
By selecting yes with the "ROM" option you can change the command to:
"..\Emulator.exe" -option "ROM.ext"
Enter the name of the emulator's configuration file. Wildcards and paths are accepted.
If the configuration file is stored in the same folder as the emulator's executable, RoM-Jacket will copy it to each ROM's folder upon exit allowing you to retain the settings on a per-rom basis.
The custom emulator and console-template use a very basic structure that let you specify how a ROM is launched:
"...CustomPath\CustomEmulator.exe" options "ROM" arguments
Options are given after the emulator and before the ROM. Arguments are given after the ROM.
The switches are emulator specific: Consult your emulator's help/manual.
Custom commands can be injected into your launchers. 4 before the rom is launched and 3 upon the emulator's exit.
All commands follow batch syntax.