'' Nooooo, I don't believeee you."Spaghetti code" is a meaningless statement that players just spout off. The reality is we, not being the game's programmers, have ZERO idea what is complex and what is not. The reality of complex large scale coding is that there is often little relationship between what we as customers perceive as easy/difficult and what is actually easy/difficult. Some things which seem insane to us can be rebuilt in an afternoon by one guy, then other things that seem like they should be easy ("iTs JuSt A fEw ExTrA fIeLdS iN tHe DaTaBaSe!1!!!") are insurmountable and would take an entire team a year to fix.
Basically there is no point in being an armchair expert and/or ranting/guessing/pontificating about programming stuff and features, you have to assume that at the level of the actual programmers that they are putting their best foot forward to get stuff done. Issues crop up here and there but in the grand scheme of things there isn't some stream of critical disasters. If the devs say something is difficult, then it's difficult, they aren't lying or covering, thinking that is just being a child.
Lazy devs REEEEEEEEEEE. ''
I think unless you work with the system itself then you should refrain from trying to attribute something such as lying or malice when in reality you have no clue yourself and are just trying to venture into the "Lul lazy" paradigm.
EDIT: To address the comments themselves, it absolutely does exist and when you work with a project which involves multiple working parts and components then this issue is just further exacerbated. So in the sense of whether it will be addressed or not. No, it never will be addressed. The best they will ever be able to do is work actively around stopping this spaghetti code from being too inhibiting on the game features.
Last edited by Kaurhz; 05-02-2022 at 09:24 AM.
I'm still wishing for GNB/DNC/RPR/SGE weapons for the other Ultimates. I don't know if spaghetti code would have anything to do with not bringing these weapons into the fold, but I know some people are still saving their totems for this eventuality![]()
It's not 1.0 spaghetti code.
it's the bones of the 2.0 game, having to replicate data from 1.0, running on a modified FFXV engine that was specifically built to run on the playstation 3.
That's less likely to be a code limitation and more a "the weapon design/modeling team is working on other content right now, and we consider that higher priority." (I would bet, for instance, that right now the weapon design/modeling team is working on hashing out the general aesthetic of this expansion's relic weapons.)
Things like "the server coughs up a hairball and then falls over dead if multiple people open a glamour dresser in the same spot" or "the glamour system breaks entirely if you move a glamour dresser while you're using it"? Those could easily be due to spaghetti code.
Say, for instance, that the cache of glamour items is tied to the record of the in-world object being used, versus the character. There are many reasons this could be the case!
But then if you move the in-world object (i.e., removing it and recreating it elsewhere), the glamour record goes "poof" while being used. That would be Bad. Or you have four people using the same glamour dresser, and as a result of it having 1600 glamour items loaded into the in-memory record of a single object, it exceeds what was ever supposed to be the maximum object record size in memory, and Bad Things Happen.
And "there's no feasible way to change this without cutting out a giant chunk of the zone instance servers to rewrite it" could 1. absolutely be a real problem in trying to implement glamour dressers in the world in general, and 2. could absolutely be the fault of the aforementioned development issues. Be it spaghetti code ("some of this is built on code where no one really knows how it works anymore"), or legacy code that you just can't change because 47 different things depend on it doing things one way, so even if you cut the legacy code out and rewrote it, you'd then have to rewrite the other 46 things as well. Stuff like that.
(The latter isn't technically spaghetti code in the traditional sense, but there's still a fairly large overlap; sometimes the reason you can't cut the thing out and replace it is that because the thing in question is spaghetti code, no one is 100% certain how it works. Thus no one is certain that replacing it with a newer function won't break the other 46 things.)
I aim to make my posts engaging and entertaining, even when you might not agree with me. And failing that, I'll just be very, VERY wordy.Originally Posted by Packetdancer
The healer main's struggle for pants is both real, and unending. Be strong, sister. #GiveUsMorePants2k20 #HealersNotRevealers #RandomOtherSleepDeprivedHashtagsHere
You can't change glams outside of major settlements, due to the terrible code. Yes, it really is the spaghetti code.
Anything is an excuse made up by the devs at this point.Do you think the game is still heavily plagued by spaghetti code?
What are the limitations caused by spaghetti codes that still exist to this day?
Do you think the game will one day be free of spaghetti codes?
Do you think spaghetti code is just an excuse made up by devs and not a real issue?
I wish I had the confidence in talking about things I have no experience in that half the people on the forum do.
WHERE IS THIS KETTLE EVERYONE KEEPS INTRODUCING ME TO?
They have never used the limitations of spaghetti code from 1.0 as an excuse for anything because devs are The Twelve incarnate according to the forums, so don't you dare say they make mistakes.
Reality, though, is they have. Memory limitations too, every time they can.
I wouldn't know. I dont work on the game, Im not employed at SE or part of the FFXIV Dev Team. I dont have access to the Source Code, and I dont know how it all mingles together or perform a handshake with the server itself.Do you think the game is still heavily plagued by spaghetti code?
What are the limitations caused by spaghetti codes that still exist to this day?
Do you think the game will one day be free of spaghetti codes?
Do you think spaghetti code is just an excuse made up by devs and not a real issue?
Cant make claims without being there.
To Question 3, say maybe. This Upgrade might fix some issues in the Code, or just be a Bandaid.... Odds are unless the entire Code gets revamped, I dont think we will ever escape the Spaghetti Code. So my best hope is they can continue to create some of their best work despite the limitations.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.