Server Issues and Limitations

[Sorel]

"WE ARE BEING PATIENT! NOW TELL US ALREADY!"

I lold

Thank you, thank you! I'll be in town all week. /em rimshot

We know they are working on the server issues.
We want them to keep on working on the server issues.
We will be patient as they are working on the server issues.
But at the same time, we'd also like them to tell us what those server issues actually are.

The impatience doesn't stem from them not fixing it, it stems from them not telling us what they are fixing.

It's like being delayed on a airplane, and the pilot saying :

"We're going to be delayed because the plane is having issues taking off. Once we fix those issues we'll be up in the air."

versus

"We're going to be delayed because our communications computer is having trouble maintaining contact with the tower. As soon as we get a team here to swap it out, we'll be ready for take off."

The first response will likely piss people off, the second response less so.

[Aldora]

Thank you, thank you! I'll be in town all week. /em rimshot

We know they are working on the server issues.
We want them to keep on working on the server issues.
We will be patient as they are working on the server issues.
But at the same time, we'd also like them to tell us what those server issues actually are.

The impatience doesn't stem from them not fixing it, it stems from them not telling us what they are fixing.

It's like being delayed on a airplane, and the pilot saying :

"We're going to be delayed because the plane is having issues taking off. Once we fix those issues we'll be up in the air."

versus

"We're going to be delayed because our communications computer is having trouble maintaining contact with the tower. As soon as we get a team here to swap it out, we'll be ready for take off."

The first response will likely piss people off, the second response less so.

Now, please read your 2nd response again and be completely honest when i ask this... Would you really want to know that the communications computer is having trouble maintaining contact with the tower when you are sitting inside a plane? I sure as hell wouldn't... (Because i'm comparing that situation with playing a game. You are already in it...) There are somethings that are better of on a "need to know"-basis. When the issue is resolved and we have arrived safely at our destination, THEN they can tell me that the problem was caused by the communications computer not being able to maintain contact with the tower.

The same goes for the server issues as well. We don't need to know "exactly" what the "server related issues" are. That they acknowledge them and are doing their best to fix it would be sufficient enough. Same goes for the timeline as well. If SE would give a serious response that they are fixing the server issues and that it will take another 6 to 12 months, all "hell" would break lose for (probably) the majority of the "demanding" player base.

Improving the server stability and performance with each update is all i would ask for. If the game is running as smoothly as a baby's bottom when the PS3 version is released, i'd be a happy camper.

[Sorel]

Now, please read your 2nd response again and be completely honest when i ask this... Would you really want to know that the communications computer is having trouble maintaining contact with the tower when you are sitting inside a plane?

I would. And when I was on that plane that was delayed for 40 minutes from Boston to Florida, everyone aboard appreciated the candor of the pilot. And when we saw the maintenance guys come onboard and go into the cockpit, no one freaked out about it because they new what was going on on why they were there.

More information is always better than less information. We're not children. We're adults. I think we can handle it.

[tachikoma]

I'll be 100% satisfied if these issues are all fixed by PS3.

[Delsus]

I would. And when I was on that plane that was delayed for 40 minutes from Boston to Florida, everyone aboard appreciated the candor of the pilot. And when we saw the maintenance guys come onboard and go into the cockpit, no one freaked out about it because they new what was going on on why they were there.

More information is always better than less information. We're not children. We're adults. I think we can handle it.

Pilot "This is your captain speaking, we apologise but we are due to arrive at *insert destination* 40 minuets late but we seem to have lost all but one engine, it seems to be caused by a fuel leak."

As if that wouldnt cause a panic thousands of miles in the air.

Now tell me would you understand if SE said "we apologise for the bad latency issues, we have has a consultant in and have been advised that we should change the priorities on all out routers because they arent load balancing enough, Also they have suggested that we reconfigure all routers to use OSPF.

We were told that spanning tree was not functioning correctly which alos impieded the performance of out network.

That is just a small amount jargon that would be in a letter they would tell us. if you know what OSPF, Spanning tree and the specific reasons priorities matter and how routers perform load balancing then its ok, but this kind of letter would go into that much technical detail only a few players will understand because you have to be educated in routing and switching to know what there talking about.

If you havent been educated in networking (to a level that you would get a job in the field) you will not understand any of it and wont care about it, this letter will be addressed at the minority of the playerbase and therefore probably is not worth the time to write.

And on the rough timeline comment, it has been done before and people rage when it doesnt come, example Yoshi-P says he will try to release a letter every 2 weeks (which is rough) and people start raging when it doesnt come out exactly 2 weeks to the day since the last letter, which will happen with these problems if they say "we aim to have the server issues sorted out by december" the word aim means its when they want it done by and makes a rough timeline, however some people will read it as "we will have the server issues sorted out by december" and will rage on the 31st december when they are not done.

[RopeyDonkey]

...if they say "we aim to have the server issues sorted out by december" the word aim means its when they want it done by and makes a rough timeline, however some people will read it as "we will have the server issues sorted out by december" and will rage on the 31st december when they are not done...

OR, they could come up with a timeframe and, um, stick to it? I work as a product manager for a UK based software dev firm - the business is all about deadlines and sticking to them. They should hopefully have identified all of the key issues/bugs/features and have a decent timeline up for when they should be resolved by etc etc. If they want to err on the side of caution, then stick a date in the letter 4 weeks after the intended completion date perhaps, but they *should have a date* for fundamental fixes like this. If they don't... the game is probably doomed

(note: I really don't want the game to fail!)

[Delsus]

OR, they could come up with a timeframe and, um, stick to it? I work as a product manager for a UK based software dev firm - the business is all about deadlines and sticking to them. They should hopefully have identified all of the key issues/bugs/features and have a decent timeline up for when they should be resolved by etc etc. If they want to err on the side of caution, then stick a date in the letter 4 weeks after the intended completion date perhaps, but they *should have a date* for fundamental fixes like this. If they don't... the game is probably doomed

(note: I really don't want the game to fail!)

The deadlines for patches for a game are never set in stone because it doesnt matter as much as making software for a company if its delayed. yes working for a software dev firm delayed work will cost contracts, but delaying patches for a game will not.