Launcher + Authenticator

I understand that I shouldn't launch with the Launcher, but on 1 account (with my Wow accounts) I have an authenticator, and I just hate pulling my phone out etc., so I use the Launcher, as it authenticates me automatically.

For my other D3 accounts, I don't have any authenticator, so not using the launcher is fine.

When I use the launcher on main and no launcher on alts, sometimes it works well, and sometimes this happens:
Main will start at is2. Alts will be is3/4 etc. This causes anything to do with a "Slot" in ISBoxer to break. Round Robin believes there's an is1, is2, is3, etc. What exists in reality, out of those, is just is2 and is3, meaning the first instance receives no input (where slots are concerned). Also anything hardcoded to a slot will not work for slot 1 (is1).

If you tell me I must never use the launcher, I'll understand. Just posting this in case it helps discover a way to incorporate the D3 Launcher (which Authenticates and logs in, it's convenient!) with running a team.

PS. irc seems to be down

I think I found a workaround. It worked twice, anyways.

What seems to cause the sessions to be named starting at is2 is clicking play RIGHT AWAY on the D3 Launcher. While the launcher is launching, there are 3 sessions. After I allowed it to idle, there were 2. Waiting to press play caused to sessions to be named appropriately.

Note, this is only for a single slot (the first launched one) using the launcher. I can't speak to having the 2nd, 3rd, etc using the launcher.

[lax]

If the game instances are getting misnumbered, open up the main Inner Space console (right click IS, select Console) and within this console enter "Sessions" with no quotes. This will tell you what processes are running that IS is affecting, and it will tell you exactly what is taking up the "is1" name. Generally when the wrong process takes it, I just need to filter out that process from Inner Space.

If it's a matter of timing, you can try adjusting the launch delay between characters with a setting in your Character Set. Select it in the top left pane, then at the top of the bottom right pane is the launch delay option

I caught this happening again, despite the speed at which I pressed "Play"

I've attached the picture (ISSessions.png) of the Sessions command in the IS Console. It appears the Launcher is obtaining a Session (is1) sometimes, but not all the time. I'm only inferring this because when I went KILL is1, the launcher closed. I have no idea what is51 is in the pic, and couldn't see any visual queue of what happened when I did KILL is51.