Français
General
Scrape
Template
Gestion de Roms
Gamelist
- Sauvegarde du gamelist.xml
Outils
Divers
English
General
Scrape
Template
Roms management
Gamelist
- Saving the gamelist.xml
Tools
Miscellaneous
General
Scrape
Template
Gestion de Roms
Gamelist
Outils
Divers
General
Scrape
Template
Roms management
Gamelist
Tools
Miscellaneous
I use system names (directory) different from those proposed by Recalbox/Batocera/Retropie or I want to add a system and scrape the images of the game. How to do it?
By default ARRM associates the names of the systems (directories) with their equivalent on Screenscraper (or TheGamesDB). This association is made via the file 'systemes_screenscraper.txt' (for screenscraper) or the file 'systemes_tgdb.txt' (for TheGamesDB) which is in the directory %appdata%\nexouille soft\arrm\database\
Access to this file can be done via the icon to the right of the button ' Screenscraper ' or ' Thegamesdb.net '
Take the Master System as an example, by default the rom directory name for the Master System is 'mastersystem' for Recalbox / Batocera and Retropie.
If your Master System directory is named for example 'sega master system' you will have to modify some files :
You will have to add a line in the file ' systemes_screenscraper.txt ':
sega master system|2
For information, the Screenscraper system number can be found by searching for your system on the screenscraper.fr site. When you have found your system, its number appears ( platform ) in the url of the site: https://www.screenscraper.fr/systemeinfos.php?plateforme=2&alpha=0&numpage=0
which will result in the file ' systemes_screenscraper.txt '
... mastersystem|2 sega master system|2 nes|3 family_computer|3 snes|4 ...
It will be necessary to add a line in the file ' systemes_tgdb.txt ':
sega master system|35
For information, the TheGamesDB system number can be found by searching for your system on thegamesdb.net. When you have found your system, its number appears (id) in the site url: https://thegamesdb.net/platform.php?id=35
which will result in the file ' systemes_tgdb.txt '
... sega_pico|4958 segacd|21 sega master system|35 sfc|6 sg-1000|4949 ...
In order to associate the right extensions with this new system, you will also need to modify the extensions file: systemes_extensions.txt which is in %appdata%\nexouille soft\arrm\database\systemes_extensions.txt
Access to this file can be done via the 'edit extensions' button in the 'Main Options' tab.
Example with this modified file:
... sega32x|.32x;.smd;.bin;.zip;.md;.7z segacd|.cue;.iso;.chd;.bin sega master system|.sms;.zip;.bin;.7z sg1000|.sg;.zip;.bin;.7z sg-1000|.sg;.zip;.bin;.7z ...
If you use the functionality ' Auto template ' (automatic association of a template depending on the system), you must modify the file %appdata%\nexouille soft\arrm\database\template_association.txt and add your system.
Example with this modified file:
... sega32x|Next_Pixel_1080_console\Next_Pixel_1080_console.xml segacd|Next_Pixel_1080_console\Next_Pixel_1080_console.xml sega master system|Next_Pixel_1080_console_old\Next_Pixel_1080_console_old.xml sfc|Next_Pixel_1080_console\Next_Pixel_1080_console.xml sg-1000|Next_Pixel_1080_console_old\Next_Pixel_1080_console_old.xml ...
If you use the functionality ' Systems Sorter, Sort file es_systems.cfg ' in 'Tools' tab (which allows you to display the systems in the order you want on EmulationStation), you must modify the file %appdata%\nexouille soft\arrm\database\systems_sorting.txt and add your system.
Example with this modified file:
... sega32x;Mega Drive 32X;Sega;1994;console;0 segacd;Mega-CD;Sega;1991;console;0 sega master system;Master System;Sega;1986;console;0 sfc;Super Famicom;Nintendo;1991;console;0 sg-1000;SG-1000;Sega;1983;console;0 ...
If you want to tweak it, you can also adapt the system logo that appears in ARRM, by copying the file ' mastersystem.png ' into ' sega master system.png ' which is in the d directory 'installation of the application in the' logos' sub-directory
When you modify these files, remember to relaunch the application to take them into account.
If the system you added did not exist in your frontend, you must add it to the es_systems.cfg file in your frontend.