Achievement Menu down again (June 20, 2017)
Posted: Mon Jun 19, 2017 9:42 am
Any idea when the Achievement Menu will be available again? It has been unavailable for about a day.
Page 1 of 1
Re: Achievement Menu has been unavailable for about a day
Posted: Mon Jun 19, 2017 9:55 am
With the restart in about an hour, all progress made in achievements should then also be counted and added up so if all goes as planed you wont lose any progress
Re: Achievement Menu has been unavailable for about a day
Posted: Tue Jun 20, 2017 9:49 am
Thank you for the update +Arden
The good news: Restart did resume the Achievements Database (June 19th, 2017)
The bad news: The database is down again (June 20th, 2017)
The good news: Restart did resume the Achievements Database (June 19th, 2017)
The bad news: The database is down again (June 20th, 2017)
Re: Achievement Menu down again (June 20, 2017)
Posted: Tue Jun 20, 2017 3:56 pm
will we still get credit towards achievments for level 6 maps we do while achivments is broken? I know colibri has stated before that achievments are being kept track of while achievement system was down last time but level 6 t-maps is a new addition.
Re: Achievement Menu down again (June 20, 2017)
Posted: Tue Jun 20, 2017 5:32 pm
Achievement tracking was down before the first crash. So my guess is no.
Re: Achievement Menu down again (June 20, 2017)
Posted: Tue Jun 20, 2017 5:47 pm
Yes the system is currently down, I will restart the server tomorrow - and that will get them going again. I'll also add a fix, so hopefully this crashing will stop.
Note that just the "achievement processor" is down, but achievements still get saved - they just don't get processed. As a precaution, i wouldnt want to guarantee that they will be processed post-fix, but from the looks of it it wont be that big of a problem to export&import the unprocessed achievement-related actions. So very likely, all those achievements will still pop up on your account tomorrow.
Level 6 tmap achievement, yes since it has been added, those actions do count toward it, and are likely also pending to be processed.
Note that just the "achievement processor" is down, but achievements still get saved - they just don't get processed. As a precaution, i wouldnt want to guarantee that they will be processed post-fix, but from the looks of it it wont be that big of a problem to export&import the unprocessed achievement-related actions. So very likely, all those achievements will still pop up on your account tomorrow.
Level 6 tmap achievement, yes since it has been added, those actions do count toward it, and are likely also pending to be processed.
Re: Achievement Menu down again (June 20, 2017)
Posted: Tue Jun 20, 2017 6:26 pm
thank you
Re: Achievement Menu down again (June 20, 2017)
Posted: Wed Jun 21, 2017 4:28 pm
We've restarted with a fix that will hopefully stop the achievement system from crashing. I have also imported the previously exported data, and it is now processing. over a few days, you all have made about 1.6 million achievement-related actions (killing mobs, crafting, etc, etc). Those actions are now being processed at 1k per second 
Re: Achievement Menu down again (June 20, 2017)
Posted: Fri Jun 23, 2017 3:54 pm
So far it looks like the achievements are working ok, no more shard crashes or issues with the [ach not showing the menu.
There is however an issue with achievements from the past few minutes being reverted on a regular basis. You probably wont notice it if you go out and kill a lot of mobs, or if you do just one achievement-related-action every 10 minutes. But if you do the timing just right, you'll see the counter from the past approx 30 seconds go back. I have just found the error and it will be fixed in the next restart, most likely earlier next week.
There is however an issue with achievements from the past few minutes being reverted on a regular basis. You probably wont notice it if you go out and kill a lot of mobs, or if you do just one achievement-related-action every 10 minutes. But if you do the timing just right, you'll see the counter from the past approx 30 seconds go back. I have just found the error and it will be fixed in the next restart, most likely earlier next week.