Is it maybe time for a full infrastructure rebuild? (Re: Database and netcode issues)

[Callinon]

naming my pc don't work checking if firewall is working and virus protections services or whatever its all point to NTT there was no issues before the move.

Well let's be real there. A whole lot of people had problems with their Canadian ISP too back when they were in Montreal.

At this point I don't know if they've just managed to choose another ISP that can't handle their traffic (maybe it's time to look in to regional data centers) or if their netcode is really just so completely abominable that it can't handle realistic levels of latency and packetloss that might occur over a couple thousand miles of countryside. To be fair, it could easily be both.

[worldofneil]

I think people seem to have forgotten how big the gap was between 1.0 and 2.0.

1.0 was switched off 12 November 2012
2.0 started up on 27 August 2013

There were some brief beta periods where you could play (including beta 4 where any changes you made carried over to the full 2.0 game), but it was essentially 9 months without the game running.

Not 9 months without content, 9 months of no game at all.

Square Enix certainly aren't going to want to shutdown again and I doubt the majority of the players would want them to either.

Sure we all want more flexibility with things, but it's not like they don't give us updates, we're just very demanding and always want more.

[Krotoan]

There's no reason to assume 200 isn't the final number, either. This is a new thing, they had the chance to do it right (having apparently abandoned the armoire), and what they came up with has what is an already low limit and will continue to feel lower as they keep adding more stuff to the game.

What restriction is in place on the backend that would necessitate a 200 limit right now that won't still exist in a year? None of us can answer that question, and until someone can, the idea that the limit is a temporary "new system" thing and not the actual limit is just optimistic speculation. With how restrictive SE is on server resources, I have a hard time finding anything to suggest we'll see that limit change in the medium term.

As your statement is pessimistic doomsaying. I'll walk in hope while you wallow in negativity.

You are correct though, we don't know their developmental decisions or reasons and can either hope or condemn. I DO however know that if you introduce a new feature that uses bandwidth, you do it a bit at a time. It's a bad idea to just open the gates and just hope it doesn't break anything. This is what I base my assessment on.
Lets say the conversion of items to simpler flags of model, color and restrictions instead of tracking stats, soulbinding , and durability reduces the average bandwidth used by each player by 5%. Using this knowledge they may be able to adjust our glamour dresser to have a higher capacity since it uses less bandwidth. Once they know the server can handle it, estimates and projected numbers hold nothing on actual live implementation.

[Fyce]

The game is eventually going to succumb to its own database limitations, and long before its life as an MMO has run its course.

From time to time, I check the forums to see if there's something new.
But it seems that everything is still the same. Mostly nonsense.

[Tridus]

As your statement is pessimistic doomsaying. I'll walk in hope while you wallow in negativity.

Could be. I'd be pretty happy to be wrong in this case.

You are correct though, we don't know their developmental decisions or reasons and can either hope or condemn. I DO however know that if you introduce a new feature that uses bandwidth, you do it a bit at a time. It's a bad idea to just open the gates and just hope it doesn't break anything. This is what I base my assessment on.

If you plan to scale it, you also design it to scale. In this case, the UI doesn't look suitable to holding 3000 items since it'll be a giant collection of icons on display you have to find, rather than a list with text and icons (like the crafting log, which covers a huge amount of recipes if you're an omnicrafter). Maybe it'll work better in practice, we'll see. A search box would certainly be nice.

Lets say the conversion of items to simpler flags of model, color and restrictions instead of tracking stats, soulbinding , and durability reduces the average bandwidth used by each player by 5%. Using this knowledge they may be able to adjust our glamour dresser to have a higher capacity since it uses less bandwidth. Once they know the server can handle it, estimates and projected numbers hold nothing on actual live implementation.

To me, knowing what they've said about how their backend works, this looks like a glamour themed version of the chocobo saddlebags we're also getting. Both of them are restricted availability inventory, in that they're inventory that isn't always accessible and for which the server (and client) doesn't have to keep data loaded all the time.

The primary value in that approach is that when you transfer data to an instance server (because you're doing a roulette or something), none of that data has to go with you. Your saddlebags and glamour closet are both unavailable in that zone, so there's no need to use bandwidth or RAM on them. That means they don't have to worry about the instance server load changing at all, aside from wherever inn rooms are handled, and even then it's only if you specifically interact with it (ditto with housing if there's one you can put in your house, but it's still an on demand load).

They've called out character data transfer requirements more than once as a reason to not expand things like base inventory, and this approach avoids that problem. That doesn't mean they can scale it up infinitely the way WoW's system does (in that it covers basically every item in the game), but if the on demand loading requirements prove to be manageable then there could be room to grow it.

Hey look at that, I ended up talking myself into agreeing with you!

[Krotoan]

Could be. I'd be pretty happy to be wrong in this case.

Sounds like you have hope for this game yet. We'll hope it all turns out for the better together. Meanwhile, happy adventuring. =]

[Balipu]

Hum...its already happening that SE give us no content for 6 month

In what universe? Big numbered patches are 3 and a half months appart. You are cofusing this with World of Warcraft, my friend.

[Vstarstruck]

In what universe? Big numbered patches are 3 and a half months appart. You are cofusing this with World of Warcraft, my friend.

At least try to understand where people are coming from, do you ever talk to others? People been feeling drought for a while. It is not something I personally fully agree with as I do value trying to improve the game.. but..:

Omega: Deltascape is the first section of Omega, the main 8-player raid in Stormblood. Released on July 4, 2017, Deltascape requires players with item level of 295 or higher to enter. Once unlocked, the raid can be queued from the Duty Finder.

Since this they added very little as far as content. The problem with FFXIV is that it struggles to make content last so people get board after a month.

[Valkyrie_Lenneth]

At least try to understand where people are coming from, do you ever talk to others? People been feeling drought for a while. It is not something I personally fully agree with as I do value trying to improve the game.. but..:

Omega: Deltascape is the first section of Omega, the main 8-player raid in Stormblood. Released on July 4, 2017, Deltascape requires players with item level of 295 or higher to enter. Once unlocked, the raid can be queued from the Duty Finder.

Since this they added very little as far as content. The problem with FFXIV is that it struggles to make content last so people get board after a month.

Except the last content patch was in October. 3 months ago. That is not 6 months.

[TaranTatsuuchi]

You're asking for the equivalent of rebuilding a house by pulling out the foundation and replacing it and expecting people to be able to live in it at the same time.

The technical side is the problem. Would you rather they lie? If you think they're lying about the technical side do you think they're just lazy? How many people who work on this game do you think look at it and go.. "eh.. it's good enough. Milk it for money and let it die when people get sick of the lies".

If they're smart about it...

They should be able to work on a separate branch of the codebase and then fork it back in later.
Thus, working on new stuff while not affecting the live branch until they are ready to implement it...