F... Crappy chicken leg!
Just log (i was in work) and what i saw?
I have no words... I can`t be 24h online... This is ridiculous
F... Crappy chicken leg!
Just log (i was in work) and what i saw?
I have no words... I can`t be 24h online... This is ridiculous
I don't even understand why they have a separate 1017 message instead of adding people to the queue.
Is it because the queue is so long that waiting for it to end is meaningless?
I don't expect the login issues to be fixed over one maintenance if they don't allow people to dissipate across the new servers. From what I know they can't easily raise the amount of concurrent connections. Maybe they end up splitting the most crowded areas as they had to do with 1.0
[ AMD Phenom II X4 970BE@4GHz | 12GB DDR3-RAM@CL7 | nVidia GeForce 260GTX OC | Crucial m4 SSD ]
Just spit balling, but fixing the duty finder may fix the 1017 problem because every time you search for a duty finder and find a party, all of you join 1 server in order to complete the duty. If that's done on a large scale hundreds of people are constantly joining different servers and reaching the caps. I could be wrong.
We won't have any more problems and here's why:
The main issue was not that the servers were full, the main issue was that the duty finder is DISTRIBUTED across all the servers,and if there's too many players, not only can you have over the max players on a server at once (5000) with everyone firing off duties, the server may go WAY over 5000 if more then a few groups of 4-12 players are in a duty in different parts of the world and land on the same server.
The login restrictions is NOT because everyone is on the same server. It's so that we aren't getting error 90,000 EXITING and entering DUTIES. Error 90,000 is because the server is full when you're coming off / going to ANOTHER server from/to a duty and trying to RECONNECT to yours. the emergency maintenance was (i imagine) to implement a system where when you're in a duty, your spot BACK to your own server is reserved - since you got the lucky dice throw and were one of the players playing.
1017 World is full Error, is more of Multitudes of people trying to login in at the same time, add that with the Duty finder issues, and you get the 1017 Error. It doesn't mean the world is "really" filled, but it could be. Most of the issues regarding 1017 is Concurrent users. I hope this will fix that issue.I don't even understand why they have a separate 1017 message instead of adding people to the queue.
Is it because the queue is so long that waiting for it to end is meaningless?
I don't expect the login issues to be fixed over one maintenance if they don't allow people to dissipate across the new servers. From what I know they can't easily raise the amount of concurrent connections. Maybe they end up splitting the most crowded areas as they had to do with 1.0
Everyone says this game is GREAT when they can get in. If they did not put login restrictions in place, BEYOND THE 5000 player limit, the GAME ITSELF would be completely unplayable for those that were in, because of the way the load is distributed. This is not clearly explained by SE devs, but it's the main reason. The inability to get in right now is artificial and FAR more severe then you imagine. I bet it's less then 1/3 the total players that are normally allowed.
"To resolve this issue, we will be performing maintenance from September 3, 2013, at 5:00 p.m. to September 4, 2013, at 3:00 a.m (PDT), for the purpose of increasing the number of available Worlds, reducing stress on the Duty Finder servers, and increasing the number of concurrent logins allowed for each server."
Looks like they are increasing capacity.
You are correct. See my post for a technical explanation. The restrictions exist so that the game is actually playable.1017 World is full Error, is more of Multitudes of people trying to login in at the same time, add that with the Duty finder issues, and you get the 1017 Error. It doesn't mean the world is "really" filled, but it could be. Most of the issues regarding 1017 is Concurrent users. I hope this will fix that issue.
I know what the error means1017 World is full Error, is more of Multitudes of people trying to login in at the same time, add that with the Duty finder issues, and you get the 1017 Error. It doesn't mean the world is "really" filled, but it could be. Most of the issues regarding 1017 is Concurrent users. I hope this will fix that issue.
There is also another one that means exactly the same, but puts you in a queue - which brings the question why they bother with 1017 instead of putting me into a queue and let me wait it out instead of hammering the servers trying to get into the queue.
[ AMD Phenom II X4 970BE@4GHz | 12GB DDR3-RAM@CL7 | nVidia GeForce 260GTX OC | Crucial m4 SSD ]
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.