Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request]: Allow manually adding the same program multiple times #1335

Closed
Lucki opened this issue Apr 17, 2022 · 0 comments
Closed

[Request]: Allow manually adding the same program multiple times #1335

Lucki opened this issue Apr 17, 2022 · 0 comments
Assignees
Milestone

Comments

@Lucki
Copy link

Lucki commented Apr 17, 2022

Tell us the problem or your need

It's possible to manually add programs but every executable is only added once. It might be beneficial to be able to add the same executable multiple times to expose different functionality through launch options.

  • In the upcoming Library view every game can have its own entry.
    • My main thought here is that most game launchers allow setting launch options which directly start a game or take you to the correct landing page.
    • This could also be handy to expose every single game of a launcher to other programs with bottles-cli or as a .desktop file.
  • Another side effect is that this will allow different feature sets of a program through launch options or scripts.
    • I don't have a particular example here but I can imagine this being useful to sometimes start a game in VR mode, on a special display or with a specific resolution - as long the program exposes functionality with launch options.
    • Same adheres for pre-run and post-run scripts.
Example of three different programs pointing to the same executable:

grafik

Also have a look at the yaml config below.

Describe the solution you'd like

It seems it's currently not working because the value in the yaml file is set to the executable name. It's already possible to do this by adding the configuration manually to the yaml file. So I guess this will need a change to an unique ID of some sort.

Changing this will also have an impact to the command line interface where it's currently possible to call a program in a bottle by the executable name which would be ambiguous then (bottles-cli run -e EXECUTABLE). Current workaround is to call bottles-cli run -p PROGRAM instead.

Example of the yaml configuration from the screenshot above:
[…]
External_Programs:
    Bejeweled 3:
        arguments: origin://launchgame/71715
        executable: Origin.exe
        name: Bejeweled 3
        path: Z:\mnt\games\launcher\origin\Origin.exe
    Origin.exe:
        arguments: ''
        executable: Origin.exe
        name: Origin
        path: Z:\mnt\games\launcher\origin\Origin.exe
    Peggle Deluxe:
        arguments: origin://launchgame/1007718,1020191,1023599,1025152
        executable: Origin.exe
        name: Peggle Deluxe
        path: Z:\mnt\games\launcher\origin\Origin.exe
[…]

Other solutions?

  • It's entirely possible to set this up manually as shown above - it's just not very convenient.
  • For some launchers it's possible to add the game executables which then starts the launcher but…
    • …some are picky, less convenient or loose core functionality with this method (Battle.Net)
    • …for some it's not possible because there is no separate executable for each title (Maniaplanet)
  • GameHub has a similar feature called "Custom Emulators" which is basically the same but not very well documented.

Additional context and references

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Done
Development

No branches or pull requests

2 participants