Whats going on with SE ?

[KaldeaSahaline]

Also enough with the charade about the game code, it won't be fixed, no1 will really accept of not playing for many days for them to fix it, I would like to ppl to be more mindful of what they really want and not simply wanting wishful fantasies, which many ppl have been triying to explain.
Things can be better? sure, but depends if they can be realized or not, if they cannot be it's best to either decide if the game is worth as is or not

What do you mean by "not playing for many days for them to fix it"? Do you think that in order for them to update backend code that it requires the entire live game to be shutdown for the duration? A simple yes or no will suffice.

And how SPECIFICALLY would you suggest they fix these "issues" with dropping content cycles, increasing player subs, or even further micro transactions? Are you going to donate your time and money to SE and fix their issues? Are you willing to redo the game from scratch? You know what's not SE's fault? The fact that you are not wealthy/skilled/capable of making the MMO that you really want on your own. So you come here and demand they change how they choose to run their game because you want something different from what from their side is clearly working... want a PERFECT final fantasy MMO? Maybe try pushing ideas for ff16/17/18/whatever the next mmo they try...

1) Speaking plainly? I'd restructure gearing in its entirety. With how mundane it is, there's absolutely no excuse for it to contain that much data that it's prohibitive to further systems design.

I'm not sure what your background is professionally, but as someone who works (not in game design, but financial system design/implementation) with these types of intricacies I can say there are definitely viable solutions. I'd need to know what their development pipeline/processes look like as well as their architectural specifications to make a more educated guess on an actual solution though.

If I took place in the ARR project, one of the MAJOR milestones I wouldn't have let get lost would be identifying/implementing a long-term solution to transitioning the code-base to a more modern platform. I've seen firsthand what happens with a legacy codebase 20 years down the line and it isn't pretty, or cheap, to rectify.

2) Don't be a petulant child. I'm not here "demanding" anything. I'm offering insight into my opinion on decisions made. You're more than welcome to refute any of my posts with your own insight/examples, but spare me the white knight routine please.

3) Just because something is "clearly" working doesn't mean there aren't GLARING flaws or issues on the horizon. If you don't see them that's fine, but it doesn't mean they aren't there. It also doesn't mean something can't be improved either.

Why are we talking about database issues? The "server limitations" that are mentioned by Square Enix are universally about how much data is transferred to and from the server. It's not a question of being able to store more inventory slots, for instance, it's the ability to process more data per user every time inventory is loaded or updated. Whether the problem is due to initial bad design or something else, solving it is not simple.

We don't need to say it's OK to have these limitations because of their implementation, but we should acknowledge the level of effort that would be required to fix them. They're probably never going to be fixed in this game, so if that's a deal-breaker, maybe play something else?

Because the way they store data has proven problematic to future systems design. Obviously fixing it isn't easy, but it's a necessary evil. It's going to come to a head eventually. They can't delay it indefinitely.

I'd hate to see a game I love become stale because they're hamstrung by a legacy codebase that all the experienced developers have left behind to work on more exciting new ventures and it's too late/late/costly to fix. I'm vocal about it because I don't think it's too late yet.