Chocobo during Queue - "Difficult"

[Gesser]

@Rjain, I don't appreciate the sarcastic remark.

I didn't say it would be easy, I'm curious how legitimately difficult it is.

@ArashiDaigon, under my suggestion the system wouldn't have to differentiate between PC & Companion as party makeup (and changes to) would have no effect on the 'solo queue' check/flag.

Under my proposal, you could freely move to & from parties, companions included, it would still retain your solo-queue status.

[ArashiDaigon]

@ArashiDaigon, under my suggestion the system wouldn't have to differentiate between PC & Companion as party makeup (and changes to) would have no effect on the 'solo queue' check/flag.

Under my proposal, you could freely move to & from parties, companions included, it would still retain your solo-queue status.

In theory. However, let's say you input said code like you suggested. The program would then have to say ok, disband/reform for what? It would look and see PC(Chocobo). So it would disband the chocobo, then when you have "completed" dungeon, you'd be back at the spot and chocobo reform. Now... when it reforms, will it use a gysal green again, cause with the coding to "reform" party it may.

Now, let's take same code. You are no longer soloing but in an actual party. You wanted to form with say a friend, so you are duo partnered. If you use said coding, this may cause you to go in solo, and cause your duo partner to go into another queue instead of you being in the same system. As your duo partner is registered under (PC).

So then you'd have to input a different strand to differentiate between said sources and such, while also tying in the structure you have now. In other words, something that seems soooo simple and very easy can be longer than anticipated, not to mention could potentially cause another code strand to break, or not do it's intended effect.