[Flatpak] Launch RuneLite via pre-installed Flatpak

[deadmeu]

Would it be possible to add functionality such that when launching RuneLite through Bolt, the existing Flatpak net.runelite.RuneLite may be launched instead? I would like to treat Bolt as purely a mechanism for authentication and have my RuneLite data managed in its own space with its own set of permissions.

[Adamcake]

A mechanism like that would have to assume that everyone is using flatpak for everything, which they may not be. It would also go against flathub's app guidelines which say that a flathub app must use its own sandboxed data and config, and not try to integrate with existing configurations.

[deadmeu]

Does the auth handling performed by Bolt require data to be stored directly in RuneLite's config directories?

I was hoping that there may be a mechanism to pass this data to RuneLite or any other client (either as a CLI argument or maybe using D-Bus). With this, Bolt could make use of something like the App Chooser portal and allow the user to select an existing RuneScape related application to launch with. In this case, there would be no need to modify the data/config of the selected application, so there should be no violation of Flathub's guidelines.

With a standard interface for providing auth/session data to clients, it would allow players to keep their existing client installations (and all of their config, screenshots, data directories, etc.) without Bolt downloading and executing the clients in its own context.

[Adamcake]

Bolt is very much designed to manage its own packages. The "custom jar path" exists for people who might want to make source builds on their own PC, but even that is a bit of a hack.

If you want to launch your own installation, it may be best to bypass launchers entirely, and make your own launch script using the environment variables that a launcher would normally set.

env JX_SESSION_ID=... JX_CHARACTER_ID=... flatpak run com.runelite.RuneLite

The session ID only expires if unused for 30 days.