HOME
FORUMS
RECENT POSTS
INTREPID TRACKER
ALPHA TWO
PRIVATE TEST REALM
Home
Alpha Two
Alpha Two Bug Reports
Alpha Two Resolved Bugs
Forever queue [1] bug
Drungle
When joining the server, it will forever say Position in queue: [1]
Currently joining Vyra. Once, I clicked cancel and then play again, it updated to show the actual number, but then went right back to [1] and stays there.
Find more posts tagged with
Staff
Forums
Recent Posts
Intrepid Tracker
My Posts
Discord
Support
Download
Comments
Krisco
We've confirmed yesterday that it isn't a queue, it's a lottery. We had a few people waiting in queue for a couple of hours and others who just kept dropping and loading back in and waiting 10 minutes. The people who waited for too long, if they did end up getting in, would get booted upon entry for being idle or servers timing out (something along those lines). I was one of the ones who decided to risk it and re-enter queues every 10 minutes and ended up getting in on my 2nd attempt, after waiting for about 1.5 hours in queue the first time round. Tin hat theory so be careful with this information... haha.
Nabuuu
My level 1 have no issue to log in/out/in/out.
My level 8 is always lost in the queue.
Alluring
Merged all Queue bug threads.
Please check to see if your bug/error has been reported before making a new post - Thank you
Dolgs
You'll occasionally find devs posting in the discord channels with more info / debugging... the coin flip nature of the issue is what made this even more painful. Hopefully they get a solution out with this downtime.
Vaknar
For those of you stuck at queue position: [1]:
Were you logging in to an existing character?
Did you get disconnected, or did you log out?
Where was your character when you disconnected/logged out?
Are you able to get on with a new character?
Do keep in mind that queue position: [1] can simply be due to high volume of testers in queue, and no remaining capacity on the server
bash
I'm getting the same went from 9,999 to 1 still sitting on 1 for entering Lyneth
Vaknar
Merged similar bugs into this thread
Child Item