You are in the server queue.
- Thread starter Jackdstripper
- Start date
Yes I am getting this everytime. I wait about 30 to 45 min and get through the queue then this happens when I enter the game. I ve been playing fine the last 2 days prior to today
Got the same and now this.
EOS - Failed to init EAC make sure you are starting the game using the MortalOnline2.exe
I've been waiting for a couple hours now... im about to demand my money back. Im tired of gamr companies underestimating the amount of people that want to play their games and cant figure this out... the online gaming has been around for 25 years and they still make the same mistake year after year.
Update!!!!!! I got to see my character and it said "Enter Nave" i pressed play and instantly client crashedI've been trying to beat the Haven ->> real world boss ALL day. It keeps me in "You are in the server queue." for 20-30minutes then crashes me to mainmenu or client crashes. Repeat. For 10 hours now.
Repeat first post indefinitely.
same crashes here @Dixie , already also tried to start the game direct via mortalonline2.exe, but even that did not brought any help. "as well as reinstalling the game, EAC and reboots."(edited)
any recomondations? as i trie to connect since yesterday evening, could play in heaven normaly but joining the real world stoped me completely.
"Go to your installation folder and locate the EasyAntiCheat folder. Rightclick on EasyAntiCheat_EOS_Setup.exe and execute it as admin. or use the EAC_Install.bat batch file.
this worked for me." (edited)
any recomondations? as i trie to connect since yesterday evening, could play in heaven normaly but joining the real world stoped me completely.
"Go to your installation folder and locate the EasyAntiCheat folder. Rightclick on EasyAntiCheat_EOS_Setup.exe and execute it as admin. or use the EAC_Install.bat batch file.
this worked for me." (edited)
Last edited:
So, I've collected a lot of data from forum posts, reddit, Discord and various streams, and I believe I've identified a pattern. Hopefully others who are experiencing this will be able to confirm.
I was able to login on Day 1 and move from Haven to Myrland with no issues. At the end of Day 1, I chose to logout, versus stay in game AFK or macro. Today every time I tried to login, I would spend between 18 and 21 minutes in the queue, get the login screen, and then crash, with the Unhandled Exception: 0x80000003 - UE4 error message.
In collecting data, it seems that the people who were actively logged into game, afk or macroing, when the server down in the morning, are NOT experiencing the 18-21 minute queue and crash cycle, and all those who ARE, seem to be people who were not in game when it went down...
Does this match your experience, either if you are crashing, or if you are not?
I was able to login on Day 1 and move from Haven to Myrland with no issues. At the end of Day 1, I chose to logout, versus stay in game AFK or macro. Today every time I tried to login, I would spend between 18 and 21 minutes in the queue, get the login screen, and then crash, with the Unhandled Exception: 0x80000003 - UE4 error message.
In collecting data, it seems that the people who were actively logged into game, afk or macroing, when the server down in the morning, are NOT experiencing the 18-21 minute queue and crash cycle, and all those who ARE, seem to be people who were not in game when it went down...
Does this match your experience, either if you are crashing, or if you are not?
I'm in this category.
I am having the queue-enter nave-crash with UE4 error cycle. From the 2nd day after the start.
First I could easily enter Haven and Travel to bakti, i logged out there and could just once log in to the bank before crashing.
I was not inside server when server shutted down.
This is utterly dissattisfying knowing i'm one of the few of my guild left out from the starting phase of the game..
Interesting info. I wonder if this changes people's PoV on the server issue. I logged out when the game started lagging unbearably. I can probably look up in some chat program when I did. Then I was never able to get back in. I was able to get back in after the reset, but it was morning so I was there within ten minutes of it coming back up.
It's definitely not as clear cut as whether you were in game or not when the server went down, but it does seem there is an account state which a subset of people are in, with commonalities like the 20-minute queue and crash cycle, and others who just never leave the queue, and others who never enter it - but who all ran the game at the same time.
Seems like I logged in the morning shortly after reset cuz like I said it was really getting laggy (like 1 second lag), came back around noon to try, couldn't get in. Tried around 4pm with the clear saved data thing and got in, but I couldn't even move items out of my bank, so I logged again, and was unable to get in again after that. That's on Wednesday.
But yea I do think just staying in the game was the key, but that's assuming you didn't get kicked (I did a bunch day1, but was able to log right back in.)
But yea I do think just staying in the game was the key, but that's assuming you didn't get kicked (I did a bunch day1, but was able to log right back in.)
As we wait, here is a reminder of where New World was at launch, and where it is now a mere 4 months later:
While long server queues weren't the only factor that led to its downfall, it was probably one of the major contributors.
SV, whatever you're going to do, you better do it fast. The long line of people out there will not wait while you try to resolve the server queue, and they aren't going to be as patient and forgiving as some of us here are.
While long server queues weren't the only factor that led to its downfall, it was probably one of the major contributors.
SV, whatever you're going to do, you better do it fast. The long line of people out there will not wait while you try to resolve the server queue, and they aren't going to be as patient and forgiving as some of us here are.