mirror of
https://github.com/Drop-OSS/drop.git
synced 2026-07-22 00:26:55 -04:00
[GH-ISSUE #357] FR: Multiple Executable Selection Per Version #338
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Elite-Alien on GitHub (Feb 25, 2026).
Original GitHub issue: https://github.com/Drop-OSS/drop/issues/357
Some games have multiple executable files. One for a configuration, one for the game, and some even a server for lan hosting. Currently there can only be one executable set per game and this presents a problem for portable games with these extra executable files.
This would also need to be added to the client to allow the selection of multiple executable files.
Not part of the request. I can remove it if asked.
https://github.com/Elite-Alien/Portable-Game-Launcher/tree/main
This is a little code I quickly spat out for a temporary fix for a work around for the time being. I present this mainly as a sort of example of how I see things working. My code uses a config.json which you fill in the name of the game and the locations of the executable files. It then determines what OS it is and if it is using umu-run or Wine. The client would need a popup similar to Steam and the server would need to be able to write the config.json for the version of game to build the menu per executable.
I am not suggesting to use my code only showing it as a proof of concept basically. I made it quickly in a few minutes of my time. I've not tested it on Windows or Mac for that matter. Only with Linux as a temporary solution until something like this eventually gets built into Drop. Again I can remove the link if requested as I'm not trying to advertise it or anything and it's not something I will be working on anyway. So, proof of concept and a temporary fix.
@DecDuck commented on GitHub (Feb 25, 2026):
Have you tried the v0.4.0 release candidate? It supports this.
@Elite-Alien commented on GitHub (Feb 25, 2026):
I see you just released this about eleven hours ago. The update checker in the "Tasks" section isn't even telling me it exists either, hmm. Well, nope I didn't know this existed yet. I need to upgrade then.
Weird. Anyway, disregard what I requested then. Sorry for the request that was already accomplished. Thanks as always for the work.
Ah, that's why pre-release. That's why.
@DecDuck commented on GitHub (Feb 25, 2026):
Oh, the update checker checks for full-releases not, release candidates.
Edit: just saw that you realised, sorry.