Because no where in the notes it says increasing world capacity. Or having free transfers to get the noobs off of our legacy servers.
Printable View
Because no where in the notes it says increasing world capacity. Or having free transfers to get the noobs off of our legacy servers.
Fact is we probably will but it will eventually be gone for good. The thing is we definitely won't be waiting for ridiculous amounts of time anymore if we do still have 1017.
The times will be drastically cut.
Dude.......
I'm sure "some" not alot just "some" people will still hit 1017, because it's a popular game. BUT:
That's the biggest concern as people at the same time keep logging in which does cause " the world is full" error.Quote:
Increasing the number of concurrent logins allowed for each server.
You are asking a bit too much. You can't expect everyone not being able to login in to everyone able to login over 1 maint.
Like I said, some WILL hit it, but they shouldn't be taking to long to get in. If everyone can, then props to SE for getting all of the problems sorted out over 1 maint. =). If not, don't fume over it, as long as MOST are logging in, then I consider that a success not fail.
[Details]
- Addition of new Worlds
- Implementation of countermeasures to handle the influx of concurrent user counts as a result of split processing the duty finder
Umm, seems to me they're addressing the issue by adding worlds and adding the ability for more concurrent connections... About the only thing you got right was the world transfer bit...
Pssst, its not server capacity thats the issue. Might want to learn some things, before calling others noobs.
The servers hold 5k theyd need to hold 15k for there to be no 1017. If there is even one 1017 after maintenance its a fail.
Not only will you have the 1017 after maintenance but you will have an additional error code, that they will have to figure out.
I should hope there's a queue if anything. 1017 is something they cause by restricting logins, which includes sitting in a queue apparently.
If 1017 is still occurring after these upgrades, I'd have to agree that it's a fail. I expect a queue....even if it's 10000 people in front of me.
I'm hopeful, but concerned.
F... Crappy chicken leg!
Just log (i was in work) and what i saw?
http://img198.imageshack.us/img198/8823/9ba6.jpg
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
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.
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.
I know what the error means ;)
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.
I imagine that login retrictions will be fixed by next week. A few things will happen.
They will block character creation on existing full worlds. So you will have friends who are not connected and want to play with each other. They then will open new worlds, so those people who are locked out, and thier friends in the congested worlds will likely bolt to the new server. This is more true for the FC and people who didn't have EA. Though we couldn't play, at least you could create your character.
Even if this helps another 30-40% of people to login to their respective servers, it will diminish the need for AFKers to stay logged in which will also help with congestion.
I'm afraid they will add too many worlds, and when the initial hype (the first month) is over, their won't be enough population. A problem to be solved later I suppose.
Confirming that we totally needed another thread in which the OP either did not/cannot read or comprehend SE's rather plainly worded announcement, so other people like the OP can proceed to complain.
Discussing how terrible it is that SE isn't increasing existing world capacity when they have explicitly stated they are is like complaining how the Patriots won the Superbowl last year when they didn't.
Who wants to bet we still have 50 different threads on one topic after maintenance?
Well the " Increased the amount of Concurrent logins" sounds to me like " they are increasing server capacity " but who knows :P. I'm sure it's part of the package deal. They know what they are dealing with " they even said 300k concurrent connections. I'm am 90% sure they will increase server capacity as well.
A Queue is only a temporary measure, yes it works.. but you will probably be waiting for 3 hours ( if your like 2000 in queue :P). They are tackling the problem at it's source, which I'm with SE. I do hope they put in a queue, but a queue won't solve the problem, it's a band-aid fix
I'm a tech myself =), good to see some people know what they are talking about!
Ye have little faith...I bet it will be about completely fixed ;) *crosses fingers*
The log in restrictions were placed because of the duty finder errors. There has never been a problem with how many people the actual server can handle. The 1017 error is caused by the soft cap they implemented because the duty finder servers could not handle all the strain. In other words the servers population amount was never the actual problem. If they can fix the poorly designed duty finder/class quests then they can lift the invisible server cap(1017).
I got 1017 since 3 hours lol. No hope to finally beat big boss 1017 after maintainance...
If they manage to increase concurrent server connections without compromising server stability, that's great. From my (limited) networking knowledge though, you can't push the limit endlessly, you will run into bottlenecks on either the network or the CPU side, even if you have a server cluster per server. I remember in beta they said they had to limit the connections because at some point various systems started to malfunction - monster AI stopped working, quests didn't progress, etc etc.
And I'm pretty sure the 300 000 concurrent connections are across all servers, not one.
Who wants to bet even more subs will be lost if they don't fix it for good.
The streets of Balmung are choked with AFKers and the crowds at FATEs are getting really thin. A simple AFK timer would've smoothed this launch over so, so much.
Hopefully the server expansion gives people less reason to idle all day and night, but the fact that they went into launch lacking such a common sense industry standard spooks me.
sigh... OP: I really wish people would stop saying there not expanding old worlds. Yoshi-P sent out a letter last night (look on twitter) cant link sorry on my phone. but he outright says it will expand capacity of all worlds... you are going off old info, please look into all given information on a situation before coming here and QQ'ing.
Just gonna leave this here
You should read the director/producers sticky posts at the top of this board for the full facts. :oQuote:
Originally Posted by Naoki_Yoshida
This is the part that has me pissed off after everything is said and done. Instead of SE setting up too many servers so the problem would be theres at a later time to sell those servers off once they are no longer needed...instead they put the problem on the player base....which in my opinion from someone who works in business it's just bad Customer Service start to finish.
There are many companies that if placed in the same situation would have buckled from the problems these last few weeks....the one thing going for this company is its brand name which a lot of people have faith in (I dont know why after there last 12 years of business) and will carry them through this.
Really depends on how they coded the use of the servers. Seeing as the duty finder is a seperate server/set of servers they are dealing with a complex issue where one server load affects another. It could be as simple as adding some hardware and zoning the game in certain ways to increase capacity. But there is always a limit on how far they can push it. Mainly because in an MMO, everyone could just decide to sit in Gridania. That is a problem because you have to prepare for the unknown.
And yes, 300,000 concurrent is all servers. If you logged in 300,000 onto one server, it would create a black hole and destroy the entire planet, and destabilize our entire solar system.
BTW: totally agreeing with you ;)
SE can't start charging monthly fees until everyone can play the game as intended. So if it doesn't cure the problem don't expect any monthly fees anytime soon. SE can't afford to run all these servers for free, considering the financial burden of remaking the game it will be a long while before a profit is appears
I'm sure there still will be 1017. I'm just hoping its not basically at all times except like 2am to 6am like right now. Expecting a miracle fix is expecting too much, but that's what forums are for I guess. You can't really do anything if the worlds are really full.
I hope the stuff like lobby errors and unable to find worlds will stop though. Those are infuriating. And we really shouldn't have to spam 0, we really should be able to just queue up, even if it is an hour long queue. But it sounds like they aren't working on AFK timers and queues at least till after this maintenance is done, so we'll see. So, for now, I'm hoping the only struggle will be a few minutes of 0 spam. Of course if people think that is "unacceptable" that's your right.
It has been said many times and I will also say it again here, the server cap is 5K players per server, but we have never had the actual cap at 5k. At start it was kept lower (no one knows the number, but it was monitored and adjusted on each server 24/7), and would increase to 5k over time as the player base gets spread out over the world as they level at different paces, and times.
When the Duty Finder server went up in smoke (figuratively) and they found out that the duty finder can only handle X number of players, so they set each servers cap at X/25 (25 servers in the data center) and this has been our cap since then and will continue to be until after the maintenance starting in 8hrs to expand the DF into multiple servers and also add some new worlds. This very strict limit is what started 1017, and 1017 should be resolved when the cap goes up (why they didnt waste time to implement something now to fix 1017 as it is essentially a temporary band-aid fix for the DF as I understand it).
When they set their concurrent logins it was about 4k per server (and this killed the DF) and there was a line waiting to get on at that point (i.e. was not 5k per server) and this was before the strict restrictions we have now. I would not be surprised if right now we are only letting 2500 or less on each server right now.
EDIT: I will also add that until it is clear that the changes have resolved the login 1017 may still be around due to AFK players who do not trust the fix worked and do not want to deal with 1017 when they want to play, this is assuming they do not add some type of AFK kick, which I do not expect them to add.