Quote Originally Posted by Mugiawara View Post
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.
Quote Originally Posted by Wishangel View Post
It's such an easy fix too,...
Quote Originally Posted by Rikkustrife View Post
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.

Of course this is all my guess....and no i don't think this is an easy fix.