RomM version
Latest Docker image - I believe that's 3.5.1
Describe the bug
When using versioned platform folders for EmulatorJS supported platforms, the games in those folders are recognized by the scanner, but are unable to be played.
To Reproduce
Steps to reproduce the behavior:
Set up a standard gba platform folder and add at least 1 game.
Notice the game is playable.
Add a non-standard gba-romhacks platform folder.
Configure the config.yml file like so:
system:
versions:
gba-romhacks: gba
Add at least 1 game to the gba-romhacks folder.
Folder is recognized as the GBA platform and game is (or can be, depending on game/romhack) recognized by scanner
Notice the game is unplayable.
Expected behavior
Games in versioned platform folders should still be playable with EmulatorJS if the main platform is supported.
Screenshots
Standard gba platform folder (notice the Play buttons):
Non-standard gba-romhacks platform folder (notice the lack of Play buttons even though the folder is recognized as GBA):
Desktop (please complete the following information):
OS: Arch Linux and Windows 11
Browser: Chrome and Firefox
Version: Latest stable version of everything
Smartphone (please complete the following information):
RomM version Latest Docker image - I believe that's 3.5.1
Describe the bug When using versioned platform folders for EmulatorJS supported platforms, the games in those folders are recognized by the scanner, but are unable to be played.
To Reproduce Steps to reproduce the behavior:
gba
platform folder and add at least 1 game.gba-romhacks
platform folder.config.yml
file like so:gba-romhacks
folder.Expected behavior Games in versioned platform folders should still be playable with EmulatorJS if the main platform is supported.
Screenshots Standard
gba
platform folder (notice the Play buttons):Non-standard
gba-romhacks
platform folder (notice the lack of Play buttons even though the folder is recognized as GBA):Desktop (please complete the following information):
Smartphone (please complete the following information):