Phalcode
Feature Request: Add a drop down list of executables to executable-related Custom Metadata fields
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.
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?
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?
We do archive parsing anyway to auto detect game types so don't worry about that. I think your original idea was great.
