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

Feature Request: Add a drop down list of executables to executable-related Custom Metadata fields #442

Open
kjack9 opened this issue Oct 20, 2024 · 2 comments
Labels
💻 client There are things to do on the client 🔧 feature New feature or request 🎛️ server There are things to do on the server

Comments

@kjack9
Copy link

kjack9 commented Oct 20, 2024

Is your feature request related to a problem? Please describe.
It takes a lot of extra time to examine each game's .7z file to see what executable should be set in the custom metadata fields "Default Launch Executable" and "Default Installer Executable". The path then needs to be merged with the executable name and either copy-pasted or manually entered, increasing errors.

Describe the solution you'd like
Parse the contents of the .7z file when it is added/updated. Store candidate executables in the DB and then reference them from the app. Let me know if it's worth me making a separate feature request for this functionality in the backend repo.

For a game of type "setup":

  • populate a dropdown for "Default Installer Executable" with all candidate executables in the archive
  • leave "Default Launch Executable" a blank freeform field (since you can't predict what executables it will produce)

For a game of type "portable":

  • disable the "Default Installer Executable" field
  • populate a dropdown for "Default Launch Executable" with all candidate executables in the archive

All fields should allow custom freeform input as an option to cover any corner cases where the user needs to specify something other than what is pre-filled.

Describe alternatives you've considered
You could use installed copies of the game to determine what executables are available in the dropdown, even for games of type "setup".

Additional context
Nada.

@kjack9 kjack9 added 💻 client There are things to do on the client 🔧 feature New feature or request labels Oct 20, 2024
@kjack9 kjack9 changed the title Add a drop down list of executables to executable-related Custom Metadata fields Feature Request: Add a drop down list of executables to executable-related Custom Metadata fields Oct 20, 2024
@Alfagun74 Alfagun74 added the 🎛️ server There are things to do on the server label Oct 20, 2024
@kjack9
Copy link
Author

kjack9 commented Oct 22, 2024

I thought of a solution to this that would be a lot easier to implement, app-side only. If I'm an administrator, can you just give me a button that copies my settings on a local game up to the server?

image

I'd also want the same functionality for a game of type "W_S".

This would remove the requirement for archive parsing and for storing executable information. Thoughts?

@Alfagun74
Copy link
Contributor

We do archive parsing anyway to auto detect game types so don't worry about that. I think your original idea was great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 client There are things to do on the client 🔧 feature New feature or request 🎛️ server There are things to do on the server
Projects
Status: 🔧 Planned
Development

No branches or pull requests

2 participants