We use friendly developer-facing options that simplify build configuration by populating several coordinated underlying arguments. Most users select the friendly option, while advanced users may subsequently override the individual arguments.
Horde template parameters currently have no declarative way for selecting one parameter value to populate related boolean and text parameters. Implementing this outside the template schema makes the behavior difficult to reuse and prevents the dashboard from representing it consistently.
We have submitted a pull request adding presets to list parameters. A selected preset populates explicitly identified boolean and text parameters, while explicit user-provided values retain precedence:
https://github.com/EpicGames/UnrealEngine/pull/15083
Could Epic review this approach and advise whether it is suitable for upstream inclusion?
[Attachment Removed]