Don’t have to be so rude.
You realize that running multiple instances of the launcher is a resource hog and a completely unacceptable solution, no?
4 Likes
See:
The main people that are continuing to have this problem seem to be the people that refuse to use the simple and temporary solutions given. Having a few bnet launchers open is not going to even be noticible on a modern PC, if you do what I said. But these are the people that are likely doing sketchy stuff with extra accounts like botting or real money carries, where they use VPNs for the other clients to prevent Blizzard from banning their primary account. So they refuse to use the launcher for those accounts because it might send some kind of identifying information back to Blizzard that could get their primary account banned when the time comes.
Again, there are two simple solutions: Remove your authenticator or use the bnet launcher (along with the option to have multiple clients open if needed). Be thankful that Blizzard even allows the clients to be logged into without the launcher.
The problem is that the launcher cannot be logged in on more than one PC at a time. If they were to change that restriction, I’d have no big issue using the launcher, but having to log it out and log it in to a different PC constantly is annoying as hell and disrupts conversations.
1 Like
No.
This is a bug, and they need to fix it. We don’t need to be thankful that part of their software is broken. The login screen exists for a reason, and we’re not going to bend over and grab our ankles just because they messed up and broke something.
Also… it doesn’t right now.
6 Likes
I said be thankful they even allow it… Nowhere does it state they have to allow users to do so. At any moment’s notice, they could remove your ability to do so and force you into only being able to log in with the launcher… Like almost every other MMO out there…
Blockquote
Be thankful that Blizzard even allows the clients to be logged into without the launcher.
Wow.
Neither are acceptable solutions in the modern climate. Especially given Blizzard’s current, abusive, track record outside of their relationship with their player base. If a change like this was intentional, it is on them to make an announcement about it prior to enacting it.
This will only cause them to lose even more subs. Although, with the Microsoft intent to purchase it’s not like they have to care anymore.
7 Likes
You’re acting like it’s some ultra abusive horrible thing… It’s not… It’s a 150MB of ram launcher that uses next to no CPU when it’s minimized. Almost every other major online gaming platform requires a launcher to be opened to play. Probably 95% of WoW players launch the game from the bnet launcher. In a few years, you’ll likely see the bnet launcher merged with the Xbox app, what are you going to do then?
No, they don’t owe you a single heads up. You agree to that when you say yes to the TOS. From the EULA: https://www.blizzard.com/en-us/legal/fba4d00f-c7e4-4883-b8b9-1b4500a402ea/blizzard-end-user-license-agreement
- Alterations.
B. Alterations to the Platform. Blizzard may change, modify, suspend, or discontinue any aspect of the Platform or Accounts at any time, including removing items, or revising the effectiveness of items in an effort to balance a Game. Blizzard may also impose limits on certain features or restrict your access to parts or all of the Platform or Accounts without notice or liability.
Woah, hold up there. You are making a massive assumption here.
I use wow.exe to load a second account with different graphical settings, because running a copy of wow in the background on ultra is a complete waste of system resources. That second account has a bank toon, and a couple of lowbie alts. No sketchy stuff.
As I said before, if the launcher allowed multiple copies of wow to exist using a different config I would use it. Even multiple launchers (also a waste of resources) does not fix this because they both open the same config file. So, the only way to do this (and its not sketchy!) is to load from wow.exe.
There is also the issue that the launcher can only run from one computer at a time. I used to run my second account on a different machine, but it became such a pain because their automated security would flag it all the time even though it is a fully supported option, that I now run both from the same machine.
Removing my authenticator is a completely unacceptable solution, period. I will cancel the second account, and Blizzard will lose my sub money, before I intentionally create a security vulnerability and open myself up to being hacked. Blizzard has gone to great lengths to encourage everyone to secure their accounts with an authenticator, so advising their customers to remove it goes against their own company goals. It is bad advice.
7 Likes
Nah, not really. If this was such a big issue and was soooo widespread, there would be thousand comment threads on the forums. The attitude, unwillingness and gymnastics to avoid even attempting to use the launcher kind of tells all. The majority of the people having the issue are multiboxers and there are a lot of (mostly true)stereotypes that come with those waters.
Takes like one global cooldown to drag the slider to 1 and hit okay. No need for a second config file.
Last I checked, the config.wtf file is saved in your WTF folder, so that means you’re likely running an external script or *.bat file to swap config files, which means it probably takes just as long to execute as it does to slide the graphics to 1 and hit okay.
It shouldn’t, so long as your fingerprint information stays the same like HWID/IP/MAC or w/e they check. But it’s been a while since I’ve logged in on another computer in my house, so I’d have to test this out.
Then the best temporary solution at hand is to use the launcher… They will either fix it soon or you’ll see some change in how logins work. This likely wasn’t some accidental thing that happened, this is most likely them changing something to combat botting, account theft and real money trade accounts.
EDIT: Installed bnet on another computer, logged it for the first time and hit approve on my phone. All it did was make my first computer’s launcher ask me to reconnect, nothing weird and WoW didn’t log me out or anything either (launched WoW from the launcher and was playing a character). I hit reconnect in the bnet launcher and business as usual, didn’t ask me to reapprove or anything on my phone.
Again. Using a 2nd launcher is still an unacceptable solution because of how people run settings on multiple accounts.
Launching externally of the launcher and logging in allows them to save those settings specific to that account. Logging into that account from the launcher does not.
Yes, the system resources impact of a 2nd launcher may be negligible. Even that is still unacceptable.
You’re making assumptions on people hardware, usage and general aptitude that just aren’t correct. To top it all off, you’re consistently coming off as an ahole while doing so. Which is to say – you are not helping here. People know all this stuff, you’re just being combative because they’re not accepting your solution. Honestly, maybe you should take this as a time to step back, reflect and let the professionals at Blizzard handle it.
5 Likes
I just started having the exact same issue with the wow classic tbc client not recognizing my Authenticator Code. I tried resync, doesn’t work. When I enter the authenticator code manually on the login screen in the wow tbc client, it disconnects me.
I tried removing and reattaching the authenticator. Still doesn’t work. (my authenticator is the mobile app). Haven’t changed phone, haven’t touched the app, it’s working perfectly on the BNet portal and all.
Would appreciate directions or other links to people who have this same issue. Even better, would appreciate if the support could provide an answer, put those Microsoft dollars do good use and answer ;p
1 Like
Yes, I have a similar problems. There are two accounts on my battle.net account. I can log into one of them, but if I log out and then try to switch to the other account, it asks me for an authenticator code. I have tried everything the people above did (and more, lol), and the only way I can get into the other account is to exit the game and then switch which account the launcher is set to log into. So the launcher or the game is definitely the problem, not the authenticator.
1 Like
Suspecting this morning’s Battle.net maintenance screwed something up.
Problem started happening during it. Tried to change to another WoW account and got asked for authenticator code, entered it and immediately disconnected. Finally rebooted PC, went thru Battle.net login process, still wanted authentication but worked this time.
6 hours later, same problem happened again. Something got broken.
Just to note, I also have two WoW accounts tied to same Battle.net account.
2 Likes
Geez, don’t necro a 3 year old post. Start a new one. There is almost 0 chance the issue from 3 years ago is the issue that.
The issue is happening to me as well. 2 accounts on under one Battlenet, never had to enter the authenticator code before, just login to the launcher via SMS and was good to go but now asks for the code, tried everything people said above but just doesn’t work.
Had to remove authenticator for now but hoping this is something that can be fixed.
1 Like
It’s not just wow. It’s their entire ecosystem.
Occasionally, if you’re one of the unlucky few, it won’t even let you login to the website using the authenticator. It just refreshes right back to the login screen when you hit approve in the authenticator app.
1 Like
Would love to hear an update on this.
1 Like
Given that Ironthorne has said above that it’s a known issue and they’re working on it, is the Tech Support forum really where you want to come in swinging, making accusations and trolling people?
7 Likes
Still having this issue here.
3 Likes
Wow this still isnt fixed.
$5 this is actually intentional and they are just waiting us out to give up and let it go?
3 Likes