Went into a Freehold 16. Myself (Veeps-Shu’Halo) and an Ele Shaman (Turrom-Dalaran) froze in loading screen while trying to enter the dungeon. Had to exit out of game and relaunch the game. After the first pull our tank a Guardian Druid (Thuglife-Azralon) got DC’d and never came back. Pls look into this
I literally can’t get into M+ freehold. I’ve joined 5 12-13s at this point, try to load in, and it won’t load all the way and I get locked out of my character for 10-15 mins.
I’m experiencing the same bug. Sometimes the entire party can get stuck on the loading screen when entering Freehold.
Same here. My +21 FH group all got disconnected last night on loading screen for the instance for 5 minutes at least. After finally reconnecting I saw my entire party offline. As they all slowly were able to get back in they stated they disconnected when trying to zone in to the instance like me.
Happening to me as well. Tried repairing game files, didn’t work.
This just happened to me tonight. My whole party got disconnected while loading into Freehold. Then we couldn’t log back in because it said a character with that name already exists. Had to close and restart my client to get back in.
Lol, just ran into the same problem and same solution- close wow and battlenet, log back in.
Rinse and repeat if you get the “Character name already exists” notif.
Cheers
Having the exact same issue. 2 Freeholds, a 10 and a 9 I joined have just been infinite loading screen bugs.
Just had this happened to a whole group zoning into neltharions lair, 3 of us came back 2 never re logged. Please address this blizzard
It’s happening all over.
i can’t even move with out it freezing
It’s not just dungeons. I swear every time I hearth or portal somewhere this happens (maybe not every but 2 out of 3) it’s getting really frustrating that I keep having to alt f4, wait for my toon I was on to no longer show in a zone (it goes blank) then I can get back on it. Otherwise I get the “a character with that name already exists” warning.
On illidan. Can’t login to server. Was just kicked out of game. 2nd “World Server” down notice i’ve seen this weekend. Seems like a critical issue. been constant “abort instance” messages throughout the weekend.
Some of us weekend warriors, this is our only time to play and get our progress this week.
It’s not just Freehold. Swapping zones (going into/out of mythics, hearthing, etc.) is causing loading screen freeze followed by disconnect followed by “a character with that name already exists.” My friends and I gave up trying to run m+ last night because it’d take 20 minutes of crashes, relogs, and restarts in between each run. It was getting really annoying. It still is really annoying.
Just had this occur to me on two separate occasions with two separate groups. There was about one hour in between. Half my group got into the dungeon and wound up leaving because the the other half who wound up disconnecting took a good amount of time. Mentioned this to my guild and a handful have been experiencing the same issue.
Happend to us last night. 13 Freehold, was in voice chat with another group who ALSO had a 13 freehold. One group could get in, the other group could not.
The radio silence on this is infuriating. Freehold and NL have been the biggest offenders for me with even the entire party getting kicked out mid-M+ and not being able to get back in.
I’ve been having the same issue since a few days ago. Loading screens will sometimes DC me and Freehold I don’t seem to be able to go into at all without getting DC’d then locked out of my character.
Already tried repairing the game files. Not sure what is happening.
This issue makes the game unplayable. All of the people I play with experience it so I know it’s common at this point. Blizz can hotfix a class in a day but takes them ~2 weeks to fix a game breaking bug.
this sucks, keep happening