TribesLauncher considers tribes ascend server a valid injection target

[Griffon26]

When the TribesLauncher is started and there is already a TribesAscend.exe running as a server, TribesLauncher sees it as a valid injection target. This has a number consequences:

• if injection is set to auto, it injects into the server process
• it makes it impossible to launch a TA client through the TribesLauncher
• when both a client and a server process are running, injection may be done in the wrong process

[mcoot]

This actually already has a solution... which is not exposed by the UI. In the launcherconfig.yaml file, there is an InjectByProcessId flag which is false by default. If you set it to true, the launcher will inject into only the process ID it launched.

I added this feature mainly for my own testing - where I often need both a server and client running.

It is not exposed because it's not relevant to the usual user use case, and injecting by process ID means you can't start the game externally and then inject.

[Griffon26]

Could you instead look at the command line the process was started with and automatically exclude server processes? That'll take care of the most common use case without needing InjectByProcessId. The latter you could still use if you have 2 clients.

[mcoot]

That's a good point; I'll set that up when I'm next working on the launcher.

At some point I want to rework the launcher UI to separate things into tabs, but it's not top priority.