Server Issues and Limitations

[Thanos]

Storage space reply

OH LOOK THEY KNOW ABOUT THIS CONCERN TOO! I think they are working on another solution for us to store stuff

08-11-2011 07:18 PM #9

Bayohne

• View Profile
• View Forum Posts

Community Rep Join DateMar 2011Posts355

We're currently in the process of devising some type of storage box solution for storing the plethora of event-related items we've been distributing. I don't have a solid time frame to give you, but I'm sure we can all look forward to a place to keep all this stuff!

I'm up to my ears in swimsuits!

(88)

Matt "Bayohne" Hilton - Community Team

[tachikoma]

Storage space reply

OH LOOK THEY KNOW ABOUT THIS CONCERN TOO! I think they are working on another solution for us to store stuff

08-11-2011 07:18 PM #9

Bayohne

• View Profile
• View Forum Posts

Community Rep Join DateMar 2011Posts355

We're currently in the process of devising some type of storage box solution for storing the plethora of event-related items we've been distributing. I don't have a solid time frame to give you, but I'm sure we can all look forward to a place to keep all this stuff!

I'm up to my ears in swimsuits!

(88)

Matt "Bayohne" Hilton - Community Team

Where did I ask for extra storage? Did you even read my post? if you spent half the time analyzing what I posted as you do trying to be an internet tough guy you would have realized I am only interested in "what the server issues are and if they are working on them".

Though your posts are pretty clear they are not ready to touch any of these issues till after battle fixes AKA after 1.21 at the very least. Since we won't get new jobs till after 1.20 (hopefully 1.21) and as you quoted they will look into it maybe after the battle fixes are done.

[Gidonoidon_Sur]

I think we will see things fixed before we get any timeline on where the overall server problems are at/or are progressing to.

[Reinheart]

On JP side server is written サーバー in Japanese and when the JP reps respond saying due to the server it's written as サーバーが...

some people just took the back part of that and turned it into burger written バーガー so now they put it together サーバーガー (Sir Burger)

JP's are eating Sir Burger サーバーガ while waiting for the server サーバー fix or at least once Dev's are ready to give us the roadmap info on the server...

meh doens't come out right when actually trying to explain... ><

[Mikita]

On JP side server is written サーバー in Japanese and when the JP reps respond saying due to the server it's written as サーバーが...

some people just took the back part of that and turned it into burger written バーガー so now they put it together サーバーガー (Sir Burger)

JP's are eating Sir Burger サーバーガ while waiting for the server サーバー fix or at least once Dev's are ready to give us the roadmap info on the server...

meh doens't come out right when actually trying to explain... ><

I think it's cute when people on the Japanese side is talking about "mackerel" issues. ^^

[Belial]

I think the problem with providing information specifically in regard to server issues/crystal tools is that if they start releasing information about what core problems they are encountering, a) it provides an advantage for competition, b) it provides a selling point for other software engine developers to take business from SE, c) the community doesn't really need to know about it... That, and of course industry secrets, etc, etc... The lack of information seems to be more of a business decision, and doesn't really have anything to do with them not wanting to provide the community with more answers.

[Sorel]

I think the problem with providing information specifically in regard to server issues/crystal tools is that if they start releasing information about what core problems they are encountering, a) it provides an advantage for competition, b) it provides a selling point for other software engine developers to take business from SE, c) the community doesn't really need to know about it... That, and of course industry secrets, etc, etc... The lack of information seems to be more of a business decision, and doesn't really have anything to do with them not wanting to provide the community with more answers.

It would be somewhat lame, but I would accept it if they actually came out and said:

"We cannot implement X feature because of various server issues that we cannot discuss due to RMT/security/corporate espionage risks."

But their not even doing that.

And it's not like we are asking for detailed explanations, IP addresses, or blocks of code here. A sentence or two with nouns other than "server" and "issue" would be enough. But they're not even giving us that.

Use your words, SE. We're not kindergarten students or silver-haired grandmothers. If you happen to use a word that we don't understand, we'll Wikipedia it and get the idea.

[Belial]

It would be somewhat lame, but I would accept it if they actually came out and said:

"We cannot implement X feature because of various server issues that we cannot discuss due to RMT/security/corporate espionage risks."

But their not even doing that.

And it's not like we are asking for detailed explanations, IP addresses, or blocks of code here. A sentence or two with nouns other than "server" and "issue" would be enough. But they're not even giving us that.

Use your words, SE. We're not kindergarten students or silver-haired grandmothers. If you happen to use a word that we don't understand, we'll Wikipedia it and get the idea.

It could very well be that they are literally not allowed to discuss anything. It's called confidentiality, and even though I agree that yea, even a simple few sentences would prove useful, it could very well be something that just simply isn't allowed due to trade secrets. It's very similar to how certain court cases are handled. Yea, someone could come out and squeek a bit of information without causing any real harm, however they are not allowed to discuss even the most mundane aspects due to confidentiality.

[Sorel]

It could very well be that they are literally not allowed to discuss anything. It's called confidentiality, and even though I agree that yea, even a simple few sentences would prove useful, it could very well be something that just simply isn't allowed due to trade secrets. It's very similar to how certain court cases are handled. Yea, someone could come out and squeek a bit of information without causing any real harm, however they are not allowed to discuss even the most mundane aspects due to confidentiality.

Reminds me of a quote from a book I once read.

Catch-22 states that agents enforcing Catch-22 need not prove that Catch-22 actually contains whatever provision the accused violator is accused of violating.

[Sorel]

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.

And it's not like we are asking for detailed explanations, IP addresses, or blocks of code here. A sentence or two with nouns other than "server" and "issue" would be enough. But they're not even giving us that.

Use your words, SE. We're not kindergarten students or silver-haired grandmothers. If you happen to use a word that we don't understand, we'll Wikipedia it and get the idea.

Again ... we not asking for every explicit detail of the problem. Just some further explanation other than "server issues".

It's almost like we're back in the old Hiromichi Tanaka days.

Interviewer: Many players have complaints about <<fill in the blank>>. What are your plans to address them?

Tanaka: We cannot say at this time, but please look forward to it!!

Now with Naoki Yoshida at the helm, communication about fixes to current issues and future plans has become much much better, EXCEPT when it comes to the subject of "fixing server issues" ... which BTW is preventing half a dozen other game issues from being resolved.

Seriously, what's up with that??