Glorious Alpha Two Testers!
Alpha Two Phase II testing is currently taking place 5+ days each week. More information about testing schedule can be found here
If you have Alpha Two, you can download the game launcher here, and we encourage you to join us on our Official Discord Server for the most up to date testing news.
Alpha Two Phase II testing is currently taking place 5+ days each week. More information about testing schedule can be found here
If you have Alpha Two, you can download the game launcher here, and we encourage you to join us on our Official Discord Server for the most up to date testing news.
525 error
NicAtNight
Member, Alpha One, Alpha Two, Early Alpha Two
Hey Intrepid Staff!
Hope everyone is hitting the ground running after the holidays! I've noticed several people from my guild after this most recent patch today now experiencing the 525 error, the majority of them having fallen through the world and now cannot log back into their character. While the root cause analysis will likely take some time, is it feasible during the next downtime to do a review of current character locations and see if anyone on the z or y axis are where they shouldn't be and teleport them back to Lionshold? Hate to see half our guild having to walk away from this phase because they are now experiencing this error. This seems like a data integration issue that might be fixed with a query or two
For some of you out there who might be experiencing this, we have had limited but some luck with creating a new character, returning to the character screen and then logging in again.. not a 100% fix but still something.
Hope everyone is hitting the ground running after the holidays! I've noticed several people from my guild after this most recent patch today now experiencing the 525 error, the majority of them having fallen through the world and now cannot log back into their character. While the root cause analysis will likely take some time, is it feasible during the next downtime to do a review of current character locations and see if anyone on the z or y axis are where they shouldn't be and teleport them back to Lionshold? Hate to see half our guild having to walk away from this phase because they are now experiencing this error. This seems like a data integration issue that might be fixed with a query or two
For some of you out there who might be experiencing this, we have had limited but some luck with creating a new character, returning to the character screen and then logging in again.. not a 100% fix but still something.
1