Quote Originally Posted by Kelev View Post
snip
I know this is normal to do and that other games do it as well. Probably doesn't seem to be much of a problem in general.

But if we're complaining so hard about 1.0 spaghetti code and the issues it brings, why isn't this sort of practice better regulated and thought of from the start? Why can't they sort out functions to add as to not break something else in the future? If they want us to congratulate them for McGyvering their way through this, then why not have the same design philosophy as ARR and early Stormblood and not make systems that are going to break their systems and functionality? Why not add stuff that might break something only after you've fixed your stuff? Or you know, work to fix it altogether over the course of the three years it's been so that when you decide to implement new stuff and polish other races it's a lot easier for you?

Just food for thought really. Don't know how bad this could really be. All I know is that the way they have their system right now is indeed very shoddy and all over the place. But it's still workable. And it isn't at all the rocket science they make it out to be.