No combat chocob while queuing? =(

I find it to be highly annoying that you can't fight with your chocobo out while you're in a queue... I get that obviously you can't take him with you into the dungeon or whatever but this seems pretty unecessary! Could it not be implemented where selecting to start the instance will simply auto-dismiss your companion? Or even just make it so you have to dismiss them before it will let you enter - much like you have to change back to the class you queued as if you are currently a different one.

I guess there might be some kind of technical limitation at play here since your companion joins as a party member yet he cannon queue with you like other party members would. That is the only reason I could see them making it like this but still I feel like it *could* be fixed! It would be especially nice if you're queueing as DPS you could grind fates AND level your chocobo while waiting the 10-20 minutes for the queue...

Here's the thing: as far as ff14 is concerned, your choco companion is no different than if it was a human player. Yoshi-P is aware of the player demand to be able to queue for something while having a chocobo out, but it would require a complete overhaul of parties and the duty finder.

this has been one of the biggest complaints from everyone since it came out. seems like a huge design flaw, don't see how they didn't think this would be a problem lol.

If they count as a player, we should be able to bring them with us into dungeons.

Yeah this is the reason my chocobo never leaves the stables. I would love to have him help out spiritbonding while waiting for dungeons but don't think it will happen.

Quote:

---

Originally Posted by LystAP

If they count as a player, we should be able to bring them with us into dungeons.

---

all i want is Chocobo's Mysterious Dungeon, a randomized dungeon where it's 4 people and their chocobos

You wouldn't need to do a *complete* overhaul of the system to make it work. It would just need to be changed so that it handles chocobos differently than it does players within a party. In programming each object, be it a player or NPC or box or whatever, is usually a part of one or more 'classes'. Right now it seems that chocobos do not have a unique class in terms of their treatment by the duty finder system. If you add a unique class for them to belong to that is ignored by the duty finder system in terms of matching that would fix one problem. Then just add a line or two of code that checks if any party members belong to the chocobo class and if so dismiss them from the parties of any participants before beginning the instance...

Of course in a game like this you get tons of interaction across processes and such there could be other intervening factors preventing a simple fix like this.

The companion is just broken and half-assed, and is apparently has been too low on the priority list for ever, because it's been one of the biggest gripes since the beginning and it's still not fixed. Someone in another chocobo-related thread put it best: it's like an unofficial mod that uses some components in a way they were not meant to be used to add something to the game that it didn't have. Except, y'know, it's completely official and actually implemented. /thumbsup

It's been this way since 2.0s beta at least. We've gotten dev responses on it and it's always been said it's a problem with the way DF, parties, and companions work.

If the Chocobo is counted as a player it probably got a specific job/class. So why can't they make the duty finder ignore and kick those with that job?

But then again i got no idea how they have actually designed this mess.

Quote:

---

Originally Posted by Icepick823

Here's the thing: as far as ff14 is concerned, your choco companion is no different than if it was a human player. Yoshi-P is aware of the player demand to be able to queue for something while having a chocobo out, but it would require a complete overhaul of parties and the duty finder.

---

The have marked the chocobo somehow because you can not enter dungeons with them. (For Programmers - lets call it the Chocobo is flagged)
They do not need to change anything and just need to use the same "marker" for the dungeonfinder. The dungeonfinder should not request the players in group, but the flagged players too, its just a small infomration ONCE send... Easiest way may be to give the chocobo a "job" named Cocobo, that way they even can use the job flagging for the requesting issue...

Chocobo is treated as a party member AND a minion. It violates functionality AND fun.