Unintuitive behavior: presets assign source port to use based on executable name, not engine list entry

[thecnoNSMB]

Noticed this when looking through my options.json. It's generally fine in most cases, but can cause some confusing behavior: if the name of a source port executable changes for any reason, updating it in the "Initial Setup" will break all presets using that engine, which is particularly noticeable when using a source port's AppImage release on Linux (such as the recently-released UZDoom), since those filenames tend to include the version number, and as such will break the launcher on every update.

[Youda008]

Who the hell appends version number to an executable file name? That's such a bad habit. It would be better to convince them to stop doing that.
Oh well. I guess I'll have to invent some unique engine ID that will persist when the executable name or path changes.

[thecnoNSMB]

It appears that, although not required, this naming format is recommended by the AppImage spec and is implicitly expected for in some contexts. In my case, though, I'm able to easily work around it by pointing DoomRunner at a symlink that I can update periodically, so I would understand if you decided not to address this.