[Feature] Play games in browser about romm

[r4lix]

would love this, even a shorcut that redirect to a hosted instance of EmulatorJS would be great

[zurdi15]

This is not in the near scope, but definetly would be a very good feature

[webysther]

@zurdi15 I think the best alternative is using a .env to allow enable a external link or sort of. Then selfhosted of any service can be used. Like the jellyfin provide link to imdb, tmdb and another services, a icon from emulatorjs with the game. To get the game ID I think need to be implemented in future to be automatic as a plugin, but manual link help a lot.

[AndrewBudziszek]

I created an issue here as a feature request.

[webysther]

@AndrewBudziszek maybe can be expanded to linuxserver.io emulatorjs that use the same name project (but is different one), they use emulatorjs as engine and from libreretro with wasm. They have the same problem, is not possible to open a canonical url to the game in browser.

For me is the best implementation so far with very modular and incremental that make sense work with, the emulatorjs is a reverse engineer and will take lots of time to works and is not so compatible like LSIO version.

This is my homelab with the docker container and configured:

When open a game he project works as PWA as you can see:

https://www.youtube.com/watch?v=aZD8n5R6-W4

[Casuallynoted]

I believe this issue has also been resolved with the 3.0 update, but I realise there are a select few platforms that are still not fully working (N64 to be fixed in the next update, and CD-based consoles requiring bios support). Figured I'd comment and say this is a thing in 3.0, but not sure if the issue should be closed due to those outstanding things or if those would count as their own issues.

[zurdi15]

I believe this issue has also been resolved with the 3.0 update, but I realise there are a select few platforms that are still not fully working (N64 to be fixed in the next update, and CD-based consoles requiring bios support). Figured I'd comment and say this is a thing in 3.0, but not sure if the issue should be closed due to those outstanding things or if those would count as their own issues.

Yeah I think this can be closed sinde the feature is there, the rest is a matter of upgrading emulatorjs in our side when we can :)