Failed to join instance
I was in the middle of a very nice map, and then I found out that I could not exit. Trying to go through a portal gave me the following message.
Error: Failed to join instance because: Disconnected from server. Error: Failed to join any instances. I tried dying so that I could resurrect in my hideout, but that gave me the same message. I then tried logging out to reset, and when I got back to my hideout, the rest of my portals were gone. ![]() Last edited by ShinyBeastOfThought#4681 on Apr 22, 2015, 1:40:43 AM
This thread has been automatically archived. Replies are disabled.
|
![]() |
I've activated Zana's daily mission today but haven't finished it. I started to mapping then. I've met Zana in one of the maps (see first screenshot), done mission for her but after that, when I come to my hideout, I can't go through Zana's daily mission portal anymore (see second screenshot), got the same error like ShinyBeastOfThought. I don't know what to do now, how to abandon this mission? I can't do other master's missions from my hideout :(
Spoiler
![]()
Spoiler
![]() --edit-- OK, after restarting a game, portal's gone. Last edited by Thoian#5941 on Apr 22, 2015, 3:38:36 PM
|
![]() |
have same problem bug report reference number is 2.514.468.958
|
![]() |
That message means the instance crashed (or expired in the case of poster #2). You can close a daily by typing /abandon_daily.
If you can't leave a map, your hideout or the eternal lab instance crashed. When that happens, you won't be able to get back to the map if you leave, so finish what you want to kill and pick up the items you want to keep. Guild Leader The Amazon Basin <BASIN>
Play Nice and Show Some Class www.theamazonbasin.com |
![]() |
be happy that at least you can play, I on the other hand try to play and first beach kicks out of instance when I click door to enter town, then kick form instance every time thereafter trying to go to coast from Lions pass or whatever its called.
Devs do not respond with how to possibly fix, game looks well designed but this instancing crap that insta kicks a split second into attempting to connect says something is fubared and of course no response for possible fixes etc says they must be blind to the problem or done know what to do...Maybe roll back to previous version? Or change the way the whole kick from instance works. |
![]() |