Battle.NET account + Blizzard Authenticator + today = fail

[Targ]

So is there any reason not to setup 5 different B.net accounts?

Will I not be able to transfer toons between B.net accounts or will I be banned for boxing using different B.net accounts?

[Lyonheart]

So is there any reason not to setup 5 different B.net accounts?

Will I not be able to transfer toons between B.net accounts or will I be banned for boxing using different B.net accounts?

There is no "good" reason to set up more than one.. you will still have to enter the authenticator ID individually. Putting them all on one account is best. If you have more than eight, make another one for that reason only. It is much easier for You to manage the accounts when they are all on the same bnet account.

For example, once they are linked, when you go to account management at the Bliz site, there is now a drop down list with all your accounts. So doing things like transfers and such are way less hassle than before.

[Vecter]

There is no "good" reason to set up more than one.. you will still have to enter the authenticator ID individually. Putting them all on one account is best. If you have more than eight, make another one for that reason only. It is much easier for You to manage the accounts when they are all on the same bnet account.

For example, once they are linked, when you go to account management at the Bliz site, there is now a drop down list with all your accounts. So doing things like transfers and such are way less hassle than before.

You missed the post about this. It in fact does not require multiple tokens from the authenticator to log into different b.net accounts. I have 2 b.net accounts and tried this morning and had to only use 1 token to log into both accounts at the same time. Why this is is anyones guess and could either mean Blizzard didnt think about this scenario or the change to logging into multiple accounts under a single b.net was unintentionally changed to its current 1 token - 1 account method.

[Bloodcloud]

You missed the post about this. It in fact does not require multiple tokens from the authenticator to log into different b.net accounts. I have 2 b.net accounts and tried this morning and had to only use 1 token to log into both accounts at the same time. Why this is is anyones guess and could either mean Blizzard didnt think about this scenario or the change to logging into multiple accounts under a single b.net was unintentionally changed to its current 1 token - 1 account method.

so this means that It could be a BUG/Fluke - THAT it currently works and blizz might fix it ?

actually setting up different B.Net accounts is no different from the current setup. You have your individual "account names" and use the token only once per account per login.

in a joined scenario you use the token for 5 logins on the same account.

pets: In other words if you want to have pets on all accounts by a single code and features alike, the less B.Net accounts you have the better

[Tonuss]

so this means that It could be a BUG/Fluke - THAT it currently works and blizz might fix it ?

That's what I was thinking. Or hoping, anyway.