arcdps now launching with all windows

[tgdm]

I had GW2Launcher set up in a way which would only launch arcdps with the first client I opened, or so I thought. I had been using it that way for years, but a few weeks? months? ago it started to open with all clients. I figured it was maybe a fluke so I checked to see if there was an updated beta version, but I'm still having the same problem. Figured I'd post it here because other people I know are experiencing the same issue.

My GW2 launch settings are:

Mode: Virtual
Localized Execution: (off)
Localized Coherent UI: (off)

[Healix]

DX11 or DX9 as of July will cause this. DX11 loads addons from the main GW2 folder, so all accounts will end up using whatever addons you have in there. DX9 loads addons from the bin64 folder, which prior to the CoherentUI update in July required write access, so it was only used by the first account to launch, whereas now all accounts will share it (unless Localized CoherentUI is enabled).

If you want to control addons per account with DX11, localized execution set to full is required.

[tgdm]

I tried enabling Localized Execution, set it to Full, chose Core for sync. Still set to Virtual as the mode

arcdps is still loading up on alternate accounts. With "Core" selected for sync, you can go in and delete the addon files specifically and then it's fine afterwards question mark? Am I missing something?

And a sidenote to anyone else coming here for similar problems: If you're running any kind of mouse/keyboard software with profiles per game, localized execution means that the game most likely won't be detected until you update the file path to the new folder

[Healix]

After launching an account, localized execution will create a # folder for the account under the Gw2Launcher folder in the main GW2 folder (the ID for an account can be found under Edit > Statistics). The # folders are a replica of the main GW2 folder, which you now treat as the main GW2 folder for the account.

If you only want addons on one account, delete all # folders except the one you want, then enable "exclude addons when generating folders" under the settings for localized execution. Alternatively you can just delete the addon files from each # folder.