Ssg - speak to us

[stingreddog]

Just tell us what to do! Do we wait in this non-moving line or keep relogging?

C-O-M-M-U-N-I-C-A-T-E PLEASE!

[Nonde]

I don't suggest relogging as I tried it twice after reading someone was able to get in after relogging and on both occasions ended up at 2,996 in the queue.

I would also like to hear from devs, inc what is server capacity? Friend who got in tells me are 1200 or more in atm so if server capacity is less than 4,200 would seem to be no hope at all.

[Mithithil]

Now getting connection timed out issues even before a login.

There is something very wrong even if only as a business public image issue.

[Cordovan]

The response has been huge, which has necessitated some queuing. People in a queue will be let in without having to log out then back in repeatedly. We are also working with our operations team to make sure as many people as possible can both be in the log-in queue and in-game.

[Suzina]

I tried waiting for a while and my que number didn't move.

Then I tried relogging a few dozen times, getting different numbers each time (including LOWER numbers in the que), but I couldn't get in. The Que is non-functional.

[Rugongrod]

Exactly how many people in game vs. how many in queue?

[MagicRat]

The response has been huge, which has necessitated some queuing. People in a queue will be let in without having to log out then back in repeatedly. We are also working with our operations team to make sure as many people as possible can both be in the log-in queue and in-game.

I have not read a single report (either here or on Twitter) of someone getting in automatically from the queue without re-logging. It does not seem to be working as intended.

[Goonbag]

The response has been huge, which has necessitated some queuing. People in a queue will be let in without having to log out then back in repeatedly. We are also working with our operations team to make sure as many people as possible can both be in the log-in queue and in-game.

absolutely nobody that has gotten in has said that is the case..

[Anglion]

The response has been huge, which has necessitated some queuing. People in a queue will be let in without having to log out then back in repeatedly. We are also working with our operations team to make sure as many people as possible can both be in the log-in queue and in-game.

Really?

How about this quote from another thread:

"After having relogged multiple times and getting position 1 on this last relog, I can report that I've not gotten into the game after sitting at position 1 for just over 30 mins. If the queue is working (doubtful), that means the queue is moving glacially slow. "

[ThirdBreakfast]

The response has been huge, which has necessitated some queuing. People in a queue will be let in without having to log out then back in repeatedly. We are also working with our operations team to make sure as many people as possible can both be in the log-in queue and in-game.

I waited for an hour and 20 minutes at position 165 in the queue, and it didn't move. I don't think the queue is working.

[dentedarmor]

I sub'd for the first time in many years (65 was level cap) just to play this server. Poor customer support, and then this came out, which we know is not the truth:

The response has been huge, which has necessitated some queuing. People in a queue will be let in without having to log out then back in repeatedly. We are also working with our operations team to make sure as many people as possible can both be in the log-in queue and in-game.

Seriously thinking of doing a chargeback on my card and playing something else. Is this the way the devs run this game now?

[WillOTheWisp]

The response has been huge, which has necessitated some queuing. People in a queue will be let in without having to log out then back in repeatedly. We are also working with our operations team to make sure as many people as possible can both be in the log-in queue and in-game.

The queues are not working.
No one has reported that they are.

I finally got in after relogging about 30 times.
It seemed to be random luck.

[LagunaD2]

Just the usual uninformed, misleading double-talk...

[zantor]

Impressive

Position 4149

[Nonde]

If the queue is working (doubtful) . . .

Extremely doubtful! After sitting at 1418 for 1 hr 35 minutes I tried relogging and got 193 in queue and then 4073 on an immediate relaunch. . . . Odds that 3800ish ppl logged in during that 90 seconds is remote to say the least.

[cdq1958]

Extremely doubtful! After sitting at 1418 for 1 hr 35 minutes I tried relogging and got 193 in queue and then 4073 on an immediate relaunch. . . . Odds that 3800ish ppl logged in during that 90 seconds is remote to say the least.

Queue probably is working, yet remember that there are two streams going on here. First stream is the people getting in. The second is the people trying for the first time and the people relogging, which may result in them getting a different number. Not known is if the number is cached for a period of time before it must be dropped, either by getting in or being out of range, so to speak.

[TheHylianLink98]

People in a queue will be let in without having to log out then back in repeatedly.

Mmm, are you sure about that? I'd double check with an engineer and figure that out. We have someone in another thread claiming that they've had position 1 for over thirty minutes now and I have had position 70 for about 20 minutes with no sign of things moving forward. I got this position after coming back from an hour break and seeing what would happen. I'll let it sit purely for scientific reasons, but I'm fairly certain the queue is broken. Not surprised, when was the last time this game had a queue.


I don't mind queues, broken queues are a problem. I think you are misinformed Cordovan.

[Hurin]

People in a queue will be let in without having to log out then back in repeatedly.

Is this 100.00% certain? Because I have yet to see a single person report that their client ever launched on its own after being in the queue no matter how long they waited. And even when many reported to be very close to the front of the queue. There was even one person who stated he was in "position #1" and yet it still failed to launch even after 30 minutes.

With respect, I'd re-confirm this. All indications are that the only people who appear able to get in are relaunching. Those who wait patiently never get anywhere.

Best Regards,

H

[MarkoftheRealm]

Is this 100% certain. Because I have yet to see a single person report that their client ever launched no matter how long they waited. And even when many reported to be very close to the front of the queue. There was even one person who stated he was in "position #1" and yet it still failed to launch even after 30 minutes.

With respect, I'd re-confirm this. All indications are that the only people who appear able to get in are relaunching. Those who wait patiently never get anywhere.

Best Regards,

H

I'm the person who relogged until I got position 1. I waited 45 mins at the number and nothing changed. Assuming the queue was broken, I've subsequently relogged and tried many more times relogging. Maybe I should have waited longer at position 1, but I just don't think the queue is working properly. I'm about to give up for the day and try again tomorrow. Perhaps they'll have fixed the queue by then or have a second server open.

[slicewalker]

The response has been huge, which has necessitated some queuing. People in a queue will be let in without having to log out then back in repeatedly. We are also working with our operations team to make sure as many people as possible can both be in the log-in queue and in-game.

Total bullcrap been at 446 for over 2 hours not a single log out .

[Nonde]

Queue probably is working . . .

If queuing is working explain how I can be at 1418 for 1h 35 min and someone else can launch and be at 70 - or 1 - and similarly with others who have sat for over an hour at a high number which hasn't updated at all.

[Hurin]

Maybe I should have waited longer at position 1, but I just don't think the queue is working properly.

I think that's a fair assumption considering that you didn't get in after being "position 1" for 45 minutes while others logged in four times in rapid succession and went form 1700, to 800, to 400, to in-game in less than a quarter of the time you spent at "position 1."

I would like to see just one report of someone who saw their queue "position" and then had the game eventually launch without any further action (restarting) on their part.

I'm not pounding on this to be a jerk. A problem can't be resolved if it isn't identified, acknowledged, and understood.

[Paeroka]

1 hour and 20 minutes ago, I tried to log in and got stuck in the queue. A couple minutes later, my husband logged into his account and got into the queue as well. He then - a few minutes ago - started a second launcher and tried to relog a few times. And guess what? He got in. Meanwhile, me and friends (who queued even before we did) are still waiting. If the queue is working, how can this be explained?

[istvana]

Queue was busted. As others have posted the way in is to log out and in repeatedly until you get in. Worked for me while spouse was sitting in the queue not moving for at least an hour *after* I relogged and got in.

Cordovan tries but he simply posted completely inaccurate information.

Many people logged out and back and got in while more patient people that had queued much earlier were still waiting.

[cdq1958]

If queuing is working explain how I can be at 1418 for 1h 35 min and someone else can launch and be at 70 - or 1 - and similarly with others who have sat for over an hour at a high number which hasn't updated at all.

The display isn't accurate. Queueing has two dynamic things going on: 1. people that get in and 2. people who are trying for the first time plus those relogging. That queuing is working is indicated by the fact that people are getting in, even though the display doesn't show it counting down or updating in some other fashion. When your "now serving" number is reached, you get in. If not, you will wait for an unknown period of time. Your "now serving" number also appears to be cached for an indeterminate period, too.

Update: just got in, but it threw a "game down" error first. LOL