30 replies to this topic

[Kairi]

I've done it too and it doesn't work! 

[Garm]

opening a ticket doesn't really work either, they ask you to log out, log in, clear cache and cookies, then try again. They will then apologize and "they are aware of the problem and are working on it"

[Gigi71]

The more tickets they get, the more likely they are to actually work on it.

[TaraBing]

MORE NEWS YOU CAN USE ! ! !

 

Just when you thought it was safe to capture your advent GOODIE CODES...

 

This is what happened to me today when I tried to obtain my advent code for the Day of the 9th in the 19:50 hour:minute CT US time.  (01:50 server time for Day of the 10th) 

 

 

 

I actually was logged in (per my notes above), but it took me to the forums login-page anyway.

 

* * *

 

Ruh-oh - so what happens when I try to capture the code for the Day of the 10th just a couple minutes later?

 

 

So, what you're really trying to say here is - THERE IS NO CHANCE ?

 

Yes, there is no chance to capture your advent codes... AT THIS HOUR.

 

Evidently, there is a "lame-duck" period of hours where the LOGIN ERROR occurs not allowing capture of the recently ended day and this time also coincides with the inability to capture the same-day NTH Advent day of the server in the wee hours of the morning.

 

I get everybody's frustration now that I think I see what might be happening?  Until it gets fixed, my only suggestion would be to not wait too late (or start too early) in the day to capture your Advent codes.

 

What times should you go?

• I've gotten the codes as early as 5AM and as late as 5:55PM CT US times.
• That translates to between 11AM and 11:55PM Game Server time.

 

Best of lucky captures to everyone...

 

-TB

 

.

 

ps: IF YOU WITNESSED OTHER UNSUCCESSFUL TIMES (or SUCCESSFUL TIMES OUTSIDE OF THE SUGGESTION WINDOW) PLEASE POST THEM BELOW.

 

State both your Local Time, your (Local Timezone) - and if you know the Server GMT Timezone

 

Examples:

 

 Successful capture at 3:03AM CT (Central US) - Server Time 9:03AM GMT

 

 Unsuccessful capture at 7:50PM CT (Central US) - Server Time 1:50AM GMT

 

.

 

 

 

[TaraBing]

Day 11 unsuccessful capture at 1:10AM CT (Central US) - Server Time 7:10AM GMT

 

Day 11 successful capture at 3:32AM CT (Central US) - Server Time 9:32AM GMT

 

Nailing down the window a littler tighter on when it works and when it does not.

 

 

-TB

 

.

[TaraBing]

Day12 unsuccessful capture at 8:00PM CT (Central US) - Server Time 2:00AM Day 13.  -  Asks me to LOG IN but I am already logged in.

 

Day 12 was already captured and redeemed, the error message should have been smart enough to have read one of several different possible messages including but not limited too...

 

• "This Day is no longer available."
• "This Day was already redeemed."
• "This Day refuses to deal with you."  Okay that was a joke, but it should not have said, "Please log in."  That just confounds people.

 

 

-TB

 

PS: Server Time has crossed over into Day 13 (now at 2AM at this point), and Day 13 was not available either.  That message read: DVD NOT AVAILABLE   Hello lame-duck period.

 

 

.

[Becky Lynch]

The more tickets they get, the more likely they are to actually work on it.

I know just how frustrating it is and we did have some problems like this last year. I am so sorry that you all are having these issues but Gigi71 is correct. The more tickets support receives the more data they can collect to try and address the issues.

[Vamprilla]

yeah happened to me the 5th and now the tirteenth. all account other days worked find. say login to sever try again

[TaraBing]

Timer on advent calendar is a great idea... countdown for the active day.

 

Beyond that, there is a genuine problem where redemption is not possible for some (or all) players during a certain time of day.  It appears to be when the server resets into the next day (12:00 AM GMT), and the problem lingers for at least 7 hours where nobody can get the current day goodies.

 

The latest into the next day recorded as unsuccessful was at least until 7:10 AM GMT.

 

The earliest successful capture was conducted at 9:03 AM GMT.

 

So... just based on my findings (nobody else, yet contributed times to this board),

 

It is possible successful captures were conducted earlier than 9:03AM GMT, but not likely they were done before 7:10AM GMT.

 

 

-TB

 

.

[CaptC]

I suggest that each ticket have:

 

- screenshot of the failure

- local time of day

- your GMT 

 

It is clearly a clock time issue.  I would bet money that it is checking time more than once... and that some of the clock checks are using server time, and others are using local time, giving inconsistent results.

 

Someone on the same time as the server probably has no problem.

Edited by CaptC, 14 December 2016 - 13:09 PM.

[Garm]

I suggest that each ticket have:

 

- screenshot of the failure

- local time of day

- your GMT 

 

It is clearly a clock time issue.  I would bet money that it is checking time more than once... and that some of the clock checks are using server time, and others are using local time, giving inconsistent results.

 

Someone on the same time as the server probably has no problem.

I've already told them this and they asked for the html code so I did send it to them via email, the support ticket system doesn't like some types of files it would seem