Solution to all the problems with this game

[Rikkustrife]

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 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.

[WingsofWar]

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,...

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.

[Wishangel]

You must realize my solution involves creating an independent function whose only purpose is to merely prompt the user if they would like to continue with the action of summoning a companion before completing said action, so it shouldn't interfere with other processes, though it is still possible that it could if the player is in queue.

[WingsofWar]

You must realize my solution involves creating an independent function whose only purpose is to merely prompt the user if they would like to continue with the action of summoning a companion before completing said action, so it shouldn't interfere with other processes, though it is still possible that it could if the player is in queue.

Yeah sure i get your original post. A prompt would clearly solve the issue of removing us automatically from a DF que once we summon a companion and save us headaches by missing our que windows for a later one, and would be easy to implement IMO. However in the case of having a companion out while in que for an instance is a separate entity as i mentioned which i believe what Mugiawara was eluding to.

[Grotesque]

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 code

[TomTom1968]

Not being able to queue for dungeons while I have my Choccobo out and leaving a queue as soon as I mount my Choccobo is something I never understood why they designed it this way initially. And I understand even less why, after one Year of FF14, this problem of inconvenience still exists. Same goes for switching character while being registered with a specific role to a Dungeon. Why on Earth can’t we have Freedom while we wait?

Let us use our Choccobos and just disband them when the group is ready. Let us call our Choccobos while we wait for a dungeon and disband them when the dungeon is about to start. Let us change to whatever job we want and when the dungeon starts, auto-force us into the job we registered with and get rid of the cooldowns as well when a dungeon starts so we can start directly using all skills at our disposal.

The waiting times could be eased up a lot by allowing us to do more things while we wait. Heck, I would even start some leves here and there while waiting and lose one of them if the dungeon starts in the middle of doing it. Let it be our choice and not the mandatory settings of your program code.

We hear quite often about engine limitations and PS3 roadblocks but this is something I do not quite understand why they can’t change it in one of the minor QoL patches.

[Magis]

void callCompanion(){
if (player.status == inQueue)
displayWarning();
else {
summonCompanion();
}
}

void displayWarning(){
cout << "Are you sure you want to mount up and LEAVE the QUEUE you've been waiting "<< timeInQueue << " hours for?" << endl;
etc etc.
}

seriously fix this lol! I'm tired of accidentally leaving queue after waiting for half an hour.

Seeing as the game most likely uses lua for it's game scripts it's probably

--Do the good thing
function callChampion()
    if (player.status == inQueue) then
        displayWarning();
    else
        summonChampion();
    end
end

[Sadana]

Wishful thinking... it would be kind of cool if they had some sort of separation between 'summon/invite to party' and 'invite to DF queue'. This way you could summon your bird without it affecting DF queue or invite people to hunt parties with some sort of prompt of 'invite to queue?' 'yes/no'. If half the party is whisked away into the DF, it doesn't do anything but have them leave party (new party leader, etc.) This would also mean you could invite someone to queue with you in your party without having to leave the DF queue and start over (Like when you need only one more tank, ask a friend to use the DF since you don't want to be put at the end of the line again, and they get dropped into a completely different party.) Ah well...

[DefendPopPunk]

You must realize my solution involves creating an independent function whose only purpose is to merely prompt the user if they would like to continue with the action of summoning a companion before completing said action, so it shouldn't interfere with other processes, though it is still possible that it could if the player is in queue.

Yeah I think a lot of people missed this. lol.

[Mardel]

Yeah I think a lot of people missed this. lol.

Yeah, I was looking at the function he posted and was wondering why he got bashed for saying it's not an easy fix when his fix is a completely different fix than what they were thinking of lol.

That moment when you summon your chocobo and lose your 30minute wait lol. D: