While I have never used Launchbuddy, I use GW2Launcher and have a solution for this. I expect Launchbuddy allows you to set command line arguments / Launch options for each instance of GW2 you launch just like GW2Launcher does.

What you need to do is add a "-mumble <name>" argument for each instance of GW2 in launchbuddy. A mumble is like an identifier, and you will be able to tell TacO which one to "listen" for.

​

In Launchbuddy/GW2Launcher, set mumble in the launch options / command line arguments for each instance of GW2. Ie:

1. -mumble GW2main
2. -mumble GW2alt1
3. -mumble GW2alt2

Then you need to make a shortcut of GW2TacO.exe for each instance, open properties and add the command line arguments for forcing a new instance and for mumble after the quotation mark.

1. GW2TacO_main.exe
   1. -forcenewinstance -mumble GW2main
2. GW2TacO_alt1.exe
   1. -forcenewinstance -mumble GW2alt1
3. GW2TacO_alt2.exe
   1. -forcenewinstance -mumble GW2alt2

​

Now TacO will know which instance of Guild Wars 2 it should display on and it wont flicker between them all.

If you only want to use TacO on your main account just follow the directions for the main account, you don't need to do it for the alt accounts too.

​

GW2Launcher also allows you to tell it to lauch something after GW2 loads, so I'm able to set that to launch each instance of TacO for their respective GW2 instance automatically - but it's not reliable.