How can I setup manifest action's used as launch options, to utilize the same EXE?

When setting up actions that point to the same .exe or .lnk for variations such as arguments, any following actions after the first are removed from the apps list of buttons.

For example:

```[[actions]]

name = "Play"

path = "Game.exe"

[[actions]]

name = "Play Ultra LOW"

path = "Game.exe"

args = ["-UltraLow"]```

That second actions use of the same .exe, causes it to be removed by the app as an option. There is an alternative where shortcuts can be used.

For example:

```[[actions]]

name = "Play"

path = "Game.exe"

[[actions]]

name = "Play Ultra LOW"

path = "Game.exe - Shortcut.lnk"

args = ["-UltraLow"]```

In this instance, both options would finally show up in the app. But this leads to a bloat of shortcuts in the installation directory, and shortcuts by default don't use local directory. They use full system directories like c:\

I was wondering the same thing. I use a shortcut to pass Unreal the appropriate command (-vulkan, -dx10 etc) via a shortcut, and was hoping to do it via manifest more cleanly.
If you do want a portable shortcut in the interim, you can do it like this:
C:\Windows\System32\cmd.exe /c .\executable.exe -switch

Same issue here. I wanted to supply “Play” vs “Continue” (auto-load last save)