Broken party finder

Anyone else getting weird lag joining a pf group in duty finder? Apparently getting a que to just farm for dogs has been a chore.:confused:

Yes!!!
Our CWLS party is completely broken right now
It took 5 minutes after clicking "Accept invite" for us to even show in the same party.
Now that we're trying to que it will not work 100% keeps saying withdrawn for the party leader, and on our side nothing ever shows up.

If this is what they were gonna do with server floods or taking some down early (And letting a much less # of servers run the game) they may as well have just taken all of us offline, because we can't do a dang thing ATM

Solo que works but thats lame.

Yeah its been pretty bad. I couldn't even queue for anything yesterday.

I've had delays joining PFs, both normal and cross-world.

One person was unable to disband their own party, with the error saying it failed to cancel party recruitment ...

Putting up a PF causes a noticable delay before succeeding.

Queueing for DF after setting up a farm party has a delay of about 20 seconds and sometimes errors out with these errors:

[22:18]You are unable to accept a new duty. Please try again later.
[22:18]Your registration is withdrawn.
[22:18]One of your party members does not meet the requirements for this duty.

All 3 errors at once, as if it just wants to give me all of these errors at once.

The last farm party I was in had to disband because we just couldn't farm efficiently.

Everyone keeps bringing these issues up in shouts, LS and parties.

It only really seems to be cross world parties. I've setup Faerie only parties, both through the PF and through my FC and had no issue. I've set up cross-world parties both through the PF and through my cross-world linkshell and they have both suffered from these issues.

Been like that for a few days. I assume it's because of the server split.. I hope..

Quote:

---

Originally Posted by Hash_Browns

Been like that for a few days. I assume it's because of the server split.. I hope..

---

I've been speculating about that too, that some sort of prep work for the incoming server split has had an unintended side effect of messing with cross world parties.

Quote:

---

Originally Posted by Hash_Browns

Been like that for a few days. I assume it's because of the server split.. I hope..

---

Been having this issue since Friday evening. I'm thinking it's related to the split as well. Because queuing into duties solo or with people only from your server works fine.

Has anyone tested to see if it might still work fine if you only get players from worlds that will share a data center after the shuffle? I.e.: if PF groups up players that will be on both Aether and Crystal, could something already be marked on the back end that's confusing the system?

Just spitballing ideas to try to narrow down what it is about cross world parties that's causing trouble.

Quote:

---

Originally Posted by Hasrat

Has anyone tested to see if it might still work fine if you only get players from worlds that will share a data center after the shuffle? I.e.: if PF groups up players that will be on both Aether and Crystal, could something already be marked on the back end that's confusing the system?

Just spitballing ideas to try to narrow down what it is about cross world parties that's causing trouble.

---

I'm not sure. Someone on Reddit said their Cactuar/Sargatanas cross-world static was having issues. May be worth testing though. My raid group has a player from Balmung while the rest of us are Cactuar and Jenova.

The delay definitely happens with non-crossworld hunt parties. You set a Party Finder party up or join one, and in many cases the hunt is dead before either anyone joins or before you join it.

It's unlikely it's due to congestion because the bugs occured outside of peak hours when there was almost no Party Finder parties.

I'm sure most of us have assumed it's related to the server split but incase it's not SE need to take note of it. If this bug exists it may not mesh well with the imminent addition of server visit.

We found a way to overcome the inability to queue for A4S was to keep it Undersized but go with the standard formation: 2 tanks, 2 healers, 4 DPS. The moment we arranged our classes this way we could queue successfully almost every time.

There was a period the other day where none of my titles showed up in the title list and I couldn't change my title. This issue persisted after relogging for a bit. Minor as that is, it's another example of the systemic bugs occuring throughout the game the last few days.

Problem with that is a non CW hunt party will still run its recruitment through a Cross World setting so you'd still have the delay. Even though all the members are local still the fact it is posted as cross world is why the delay is there. Not where the members 'actually' come from.

Yes it's been bad for a few days but today specifically, its not usable at all even. 5 minutes after clicking accept to just join the party and too long of a time out after starting the duty = duty doesn't que.

Before today a 20-30 second delay was fine still it was just annoying, now its not usable.

We did get a CWLS party made and qued 2 times today, but after that it went right back to what it's been doing and not que'ing
Agreed on it being pre- DC split related.

Also we tried it in a CW party only containing Crystal people, its the same thing, as expected though.

Well after a unsuccessful day of maybe doing one or two parties through pf I gave up. Hopefully after the maintenance it’ll be working again.

Quote:

---

Originally Posted by UnrealTai

Problem with that is a non CW hunt party will still run its recruitment through a Cross World setting so you'd still have the delay. Even though all the members are local still the fact it is posted as cross world is why the delay is there. Not where the members 'actually' come from.

---

No, hunt parties are automatically set to not recruit from across the DC, meaning they are non-CW parties. A CW party would not assist you in getting credit from a hunt, while regular parties do. My hunt parties are always non-CW and listed exclusively under the current server's tab yet still experience these issues.

Perhaps non-CW parties go through the same server-side processes as CW but I can assure anyone that they are orange home server parties and not blue cross world ones.

Quote:

---

Originally Posted by Hasrat

Has anyone tested to see if it might still work fine if you only get players from worlds that will share a data center after the shuffle? I.e.: if PF groups up players that will be on both Aether and Crystal, could something already be marked on the back end that's confusing the system?

Just spitballing ideas to try to narrow down what it is about cross world parties that's causing trouble.

---

It does not work even when all players in the party are from servers staying on Aether from my experience. My static has 5 from Faerie, 1 from Jenova, 1 from Gilgamesh, and 1 from Midgard. We were not able to queue in after more than half an hour.

These issues borked out so much that my Cross-World Nidhogg EX farming party spent more time trying to ready check / instance queue than actually in the instance farming Nidhogg.

On top of that, at one point one of our party members was removed from the party while in the instance. They weren't included in the party list but they were in the instance with us and we had to have our solo healer focus target him so they could make sure he got heals since AOE heals weren't going to and didn't heal him.

Thankfully he was still able to roll on loot and so did we when he was the first to open the chests.

Yeah that's been annoying the past few days. I hope it was just something they geeked up with the prep for the data center splits and it's fixed after that's in place.

What's really annoying is they didn't SAY anything. No lodestone post or anything here saying "Hey guys, we know PF is jacked right now. Please be patient while we look into it."

wonderingif it has anything to do with the huge population running golden saucer. the car event also started about the same time PF got clogged