Improved Game Launcher Integration and Steam Interoperability

[RaulKong898]

Tell us the problem or your need

Currently, managing games that require separate launchers (Rockstar Games Launcher, Ubisoft Connect, EA App, etc.) even when installed through Steam can be cumbersome within Bottles. This often leads to:

Redundant Launcher Installations: Users might need to install a launcher both through Steam and again manually within a Bottle, wasting disk space and complicating setup.
Limited Launcher Integration: It's not always straightforward to manage games purchased directly through these launchers if you also have games from the same publisher on Steam. It may require manual configuration or separate Bottles.
Suboptimal Steam Interaction: When a game launched from a Bottle (via a third-party launcher) requires Steam, it often launches the Windows version of Steam through Wine, rather than the native Linux Steam client. This can lead to performance issues and inconsistencies. There is a need of a better conection betwen the Linux native Steam and Bottles

Describe the solution you'd like

I propose a multi-faceted improvement to Bottles' launcher integration:

1. Automatic Launcher Detection: Bottles should automatically detect the presence of separate game launchers (Rockstar Games Launcher, Ubisoft Connect, EA App, etc.) when a game is installed through the native Linux Steam client.

2. Flexible Bottle Integration: Upon detection, Bottles should provide the user with options for integrating the launcher:

• Add the launcher to an existing Bottle (containing other games).

• Add the launcher to a publisher-specific Bottle (e.g., a dedicated "Rockstar Games" bottle).

• Create a new Bottle specifically for the launcher.

3. Unified Launcher Management: Bottles should leverage the launcher installation provided by Steam whenever possible, avoiding redundant installations.

4. Direct Launcher Purchases: The integration should enable seamless installation and management of games purchased directly through the third-party launchers, even if the user also owns games from the same publisher on Steam. This would allow, for example, installing GTA V purchased on the Rockstar Games Launcher within the same Bottle (or a related Bottle) as GTA IV purchased on Steam, without manual intervention.

5. Native Steam Client Integration: When a game launched from within Bottles (via a third-party launcher) requires Steam, Bottles should prioritize launching the native Linux Steam client, not the Windows version through Wine. This improved Steam interoperability should be a general feature, applying to all launchers that rely on Steam.

Other solutions?

An alternative, less ideal solution, could be to provide very detailed, step-by-step documentation and tutorials on manually configuring various launchers within Bottles. However, this would place a greater burden on the user and wouldn't address the core issue of redundant installations and optimal Steam integration. Another solution could be a script.

Additional context and references

No response