When the launcher is started for the first time and TribesAscend is already running, the button briefly shows Update (because no TAMods.dll is present), but then immediately goes to Inject.

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