No idea what that was but they need just let us friggin' queue with the Chocobo out or even when his summoned and when dungeon starts then he'll disummon.
xDDD!
All they have to do. We've been asking for Chocobo QoL's since the games released.
No idea what that was but they need just let us friggin' queue with the Chocobo out or even when his summoned and when dungeon starts then he'll disummon.
xDDD!
All they have to do. We've been asking for Chocobo QoL's since the games released.
It's such an easy fix too, I'm not joking. Pretty much any developer could make this QoL change in less than 10 minutes.
You are forgetting one fundamental rule of coding. When You add or change anything in one line, it messes with another. Changing a code could break or change anything and when you have a GIANT list of possible locations where code could change, it takes time which equals money.
If code is shit and has no proper software architecture below it, then you might be right. I doubt FF14 is just a bunch of spaghetti codeYou are forgetting one fundamental rule of coding. When You add or change anything in one line, it messes with another. Changing a code could break or change anything and when you have a GIANT list of possible locations where code could change, it takes time which equals money.![]()
You are wrong.
There are many factors involved, like how clear is the code, is it easy to read, find where in the many lines of code is the part about companions.
Then since it considers companion a party member, you would have to find the code section about party members, to see how any changes to chocobo companion would affect that, as well as the code section involving the duty finder.
It could be very simple, or not so simple depending on how it is written.
Companion system object has many complex and memory intensive infrastructure seeing as how its an instance of a party member that gains exp and has its own stats and skill sets. Its also likely a local object running on the client. Once summoned it acts as a special party member flag. The instance que has its own lobby and must check that the party is within specific parameters before entering the lobby, and my guess as to why the companion system cannot be entered into the que lobby is because of the memory dump that needs to occur client side before the instance can begin. In games performance suffers tremendously if you make the client do more than it should, most processes should be done on the server side.There are many factors involved, like how clear is the code, is it easy to read, find where in the many lines of code is the part about companions.
Then since it considers companion a party member, you would have to find the code section about party members, to see how any changes to chocobo companion would affect that, as well as the code section involving the duty finder.
It could be very simple, or not so simple depending on how it is written.
Of course this is all my guess....and no i don't think this is an easy fix.
Tons of MMORPGs have so-called "complex and memory intensive" AI pets -- for example, Ranger/Hunter type classes who perpetually have animal companions with them, even after they enter a dungeon. Heck, even in FFXIV, we have summoners who have AI pets that can enter the dungeon with them. The game demonstrates that it can even check to see if the pet is appropriate for the dungeon's level, and auto-dismiss before you come in, as required. There is no reason a chocobo can't also be auto-dismissed in this fashion, especially when there is no additional level check required before doing so.Companion system object has many complex and memory intensive infrastructure seeing as how its an instance of a party member that gains exp and has its own stats and skill sets. Its also likely a local object running on the client. Once summoned it acts as a special party member flag.
Honestly, what is the worst thing that could happen, if DF didn't flag chocobo companions as fake "party members," and just disregarded them while in a queue? Then, when the DF window pops and tells you the instance is ready, there is an extra line of text in the window that says "Chocobo companions will be dismissed before entering." So, you click OK, and before anything else happens your chocobo is dismissed. Fade to black, allow time to do a chocobo "memory dump" or whatever you call it, then enter the dungeon. Nobody has chocobos in the instance, nobody's game is trying to render a party full of people with chocobos.
If you've played a Tank or Healer, obviously you know it is possible to have essentially an "instant" queue in DF. You could have had a chocobo companion out literally a second ago, and the game did not need to get away for a spa weekend after stressing over the "complex and memory intensive" chocobo.
Regardless of whether it is easy or hard to fix, the fact that it was ever made this way from the start is bad enough. They invented chocobo companions. They invented Duty Finder. They decided it would be okay to implement features that clashed with each other, and couldn't/wouldn't find a way to make them work harmoniously together.
While in a DF queue, I can be running around in the open world and fighting a hunt mark with 20+ other players and their chocobos running around me. I can be doing a leve. I can be another job entirely, with different skills, exp bar, and gear, then switch back when the queue pops. I can even go to the FC house and feed/train my chocobo at the stable, while the game keeps track of its stats and abilities.
Square Enix is perfectly capable of programming a system that can tell the difference between a real player and an AI-controlled NPC. The only mystery, at this point, is if they put all this together completely unaware of the inconvenience it would cause players, or if it was done intentionally as a time sink.
|
![]() |
![]() |
![]() |
|
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.