Solution to all the problems with this game

[Wishangel]

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.

[DefendPopPunk]

Oh snap ya'll, programmers up in here

edit: ehhh, the mountUp() function is confusing because you don't leave queue when you get on a mount. Should be something like what Brianmj put lol. Same goes for mountChocobo()

[Wishangel]

Oh snap ya'll, programmers up in here

edit: ehhh, the mountUp() function is confusing because you don't leave queue when you get on a mount. Should be something like what Brianmj put lol. Same goes for mountChocobo()

You're right. you leave queue when you summon the chocobo to fight alongside yourself, rather than when you mount yourself up. I'll compose an edit lol.

[Brianmj]

All replies must be in C++. And eww, camel case

or

void call_companion(){
if(player.status == IN_QUEUE){
player.companion = AS_PET;
player.summon_companion();}
else
player.summon_companion();
}

[Mugiawara]

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.

[Wishangel]

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.

[LaralnKornera]

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.

[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

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