Suggestion: When Someone Doesn't Meet Requirements of a Duty, Can it PLEASE Say WHO?

Just got a party finder group together for some Ex clears, try to queue, says someone doesn't meet the requirements. I ask around, no one will fess up that they don't have the duty unlocked, party falls apart, the end. Sooooo frustrating. Can we please make it so it at least tells the leader of the group who doesn't have the duty unlocked or doesn't meet the ilvl requirements? This seems like an easy way to troll.

And FYI, it was for Bismarck Ex, so ilvl shouldn't have been an issue unless someone was purposely trolling.

Quote:

---

Originally Posted by Kalsoa

snip.

---

thread on this already.

Quote:

---

Originally Posted by BigRed5392

thread on this already.

---

This is a totally different issue from raising DF requirements, actually.

On that note, I agree. I've had PF's fall apart for the same reason.

I thought it always said who it was who doesn't have access to the duty? I know you can ignore iLv with a full party but if you queue with a 7/8 party, it will still enforce iLv. But as far as my experience goes, it should tell you who it is.

This should be a thing.. when I join coil for khloe.. there is almost always that someone who doesnt meet the requirement by either not unlocking it or getting penalty from leaving duty.. it wasnt intended for them to troll the party, but they are mostly clueless that it's them being the troublemakers while the party doesnt get to know who's the troublemaker is..

Yes the reason people do not speak up because they do not know. It needs to tell who it is and I do not get why it doesn't

Fully support this. I've had PF's fall apart for the same reason and yeah, sometimes they may not even know it's them. This would help everyone involved.

I don't know if they're talking about ilvl requirements and such, but mostly not having the specific duty unlocked... But overall, I do think it should tell who it is and what requirements they don't meet.

If worse comes to worse I would just let the group know that you are going to start kicking and attempting to queue until it goes through and invite everyone back /put PF back up when it does and you find out who is holding it up. That might be enough for the troll to leave on their own if they were doing it on purpose. Wouldn't work very well for xserver but.. yeah.

More clarity on an active DF lockout, perhaps a debuff.

For the specific party member that does not meet the requirements there should be an error notification that pops up when attempting to queue for the instance. If someone truly doesn't know if they meet the requirements you can ask if anyone gets an error message.

Quote:

---

Originally Posted by Blueyes

For the specific party member that does not meet the requirements there should be an error notification that pops up when attempting to queue for the instance. If someone truly doesn't know if they meet the requirements you can ask if anyone gets an error message.

---

The warning message actually appears to that player who doesn't meet the requirement for the said duty.. but the thing is, when they join a pf for said duty and they don't even aware that they got it unlocked, i'm getting doubtful of their reading comprehension.

This happens to my static all the time! We have one member who is a little airheaded (to put it gently) and he never notices that he hasn't unlocked the agreed activity until we get stuck trying to go in, then we have to spend ten minutes teasing him to check. It's not so bad in our case because it's always the same person so we immediately know who to blame and make do the 'walk of shame' to the quest NPC, but if it was a PUG we'd be completely lost. It's always confused me why it doesn't get more specific and instead forces everyone to double check their eligibility just in case it wasn't that one guy. So much easier to remedy when you know right away who it is.

If someone is in a trolling mood, they can join a PF party that has any kind of ilvl requirement for the duty and just strip naked. Boom, instant successful troll. No one knows who is not meeting the requirements and the offender can just play dumb. And with this being cross server now, it's not like you can tell everyone to come to a specific area so you can examine them to make sure someone isn't doing it purposely. Really, all it it needs to change is the error message of 'Someone doesn't meet the requirements of the duty' to 'Player_Name doesn't meet the requirements of this duty.' Even if there is more than one and it only shows one, you can at least make progression towards getting in the duty. As it stands, basically you're screwed until everyone gets frustrated and just leaves. This is especially frustrating for a PF that took a while to fill up like mine did yesterday.

I see a comment saying sometimes the problem person doesn't know it is their fault. How does someone not know they don't qualify?
Doesn't the DF tell us what we can queue for?

You know..
It tells you when you queue for deep on what the problem is.. how come nothing else works like that?

The scenario is like this:
A player makes a party finder for The Final Coil of Bahamut: Turn 4, some players join in and they get themself a full party. Once the party leader tries to queue T13, the party leader will get a red warning message with something like "someone doesn't meet the requirement for this duty" but the thing is, the message doesnt tell the party leader who doesnt meet the requirement.. However that someone who doesnt meet the requirement will get a red warning message saying the player doesn't meet the requirement for the duty.. In an utopia, the player who doesn't meet the requirement should excuse themself and apologize for entering the wrong pf that player doesn't qualify for but in reality, most players don't even notice they are at fault and they ignore the red warning message in their screen simply (in my subjective wordings) because their reading comprehension is questionable once they decide to join up a duty which they havent unlocked to begin with..

The fix should be simple:
1. A warning message should tell the party leader who doesnt meet the requirement so something can be done instead of disbanding or making the party stagnant.
2. The player who has either not unlocked or got themself penalty from leaving a duty shouldn't be able to join in a pf in the first place.

Quote:

---

Originally Posted by lvlagmarink

The scenario is like this:
A player makes a party finder for The Final Coil of Bahamut: Turn 4, some players join in and they get themself a full party. Once the party leader tries to queue T13, the party leader will get a red warning message with something like "someone doesn't meet the requirement for thisduty" but the thing is, the message doesnt tell the party leader who doesnt meet the requirement.. However that someone who doesnt meet the requirement will get a red warning message saying the player doesn't meet the requirement for the duty.. In an utopia, the player who doesn't meet the requirement should excuse themself and apologize for entering the wrong pf that player doesn't qualify for but in reality, most players don't even notice they are at fault and they ignore the red warning message in their screen simply (in my subjective wordings) because their reading comprehension is questionable once they decide to join up a duty which they havent unlocked to begin with..

The fix should be simple:
1. A warning message should tell the party leader who doesnt meet the requirement so something can be done instead of disbanding or making the party stagnant.
2. The player who has either not unlocked or got themself penalty from leaving a duty shouldn't be able to join in a pf in the first place.

---

Maybe to a lot of people the message appears and vanishes too fast? Or simply they do not understand it is blaming them? Still I do not get why it tells you what the problem is being a leader for deep, and nothing else

A lot of people on here talking about players who "don't know" they're the problem, but I've honestly only come across that issue one time in all the PFs I've been in, where the person didn't realize until after we tried to queue that they had a lockout for withdrawing. 99% of the time what I've encountered is people intentionally joining farm parties to try and get their clear. When the party leader tries to queue "Duty Complete" in the Raid Finder, the queue won't go through because someone has bonus. However, since the warning message doesn't tell you who has the bonus (aka who joined a party they know they're not supposed to be in), the party leader is stuck sitting there demanding in chat for the person with bonus to fess up and leave. Most of the time they don't--because they know the party leader doesn't know who is causing the problem, and they're hoping the leader will give up and queue with them anyway so they can get their clear. If the party leader got an exact message on who didn't meet the requirements, they could just remove these offending people, pick up a new person in PF, and move on.

I could see people claiming that this could be abused, with people being singled out and kicked from parties... but if you don't meet the requirements, you don't belong in the party in the first place. Please get on this Square...