You cannot log into the ptr if you have two battlenet accounts under the same email. It gets stuck on connecting and if you hit cancel the 2 accounts go off the list. My other battlenet account gets on just fine.

Hey all,

I haven't tried copying the live WTF folder to the PTR folder, so I'm not sure that works. I would recommend trying to do this first to see if that works since the workaround can be kind of complicated.

Here's the workaround:

1. Open up the config.wtf file found In the WTF folder of the PTR build.
2. Add the following lines to the bottom of this file:

SET lastCharacterIndex "1"
SET accountName "youraccount@whateverisp.com"
SET accountList "!FIRSTACCOUNTNAME|SECONDACCOUNTNAME|ETC|"

3. Launch WoW-PTR and select the account you want to login with from the dropdown.
4. Login.

Make sure to replace youraccount@whateverisp.com with your actual battle.net login and FIRSTACCOUNTNAME/SECONDACCOUNTNAME/ETC with your WoW logins.

This should allow Battle.net accounts with multiple logins to login to PTRs. Also make sure when you enter your accountList info, that you do it in the exact same order that you would normally on the select account prompt. If you enter your account names out of order in the config.wtf file, the workaround won't work.

---

Q u o t e:
Also tried the workaround, got the dropdown list- but no go- it still stops at connecting with my account list (of inactive accounts) behind it.

Tried the WTF folder thing too. Also no go.

Then I tried the WTF folder thing AND the workaround...but still nothing. sad face.

---

Check to make sure that every account (spelled correctly) you have is in order when editing your config file. I had a little trouble with this myself when trying to get this workaround to work, because I kept listing my main account first (it is usually displayed last).

---

Q u o t e:
Is this new, because prior to the new patch I was able to log in with two accounts on the same b.net account just fine. I haven't tried since the patch.

---

There is a bug in the current PTR build that is causing this issue, this is simply a workaround until the next PTR build is released which should not have this issue.