Locked out of the Duty Finder.

[IceSpear]

This is like a soap drama here XD So funny and it's like next time on "Locked out of the Duty Finder" Get over it. You complain about people queing then withdrawing SE tries to fix it maybe not in the best way, but at lest they listened and tried yet you still complain about it's not good enough. It's like trying to give a child and upgraded bike for their birthday, but it's not a good enough bike for them they want it to be designed especially for them. This is an MMO it's not you who's just playing the game it's thousands of people. Sometimes you're gonna get what you want sometimes you're not gonna get what you want. It's not going to be perfect for everyone it's not going to be the best game in history. I do agree on the part that the time to accept the que isn't long enough for some people and that it should be changed so it's longer, but with the new penalty for not excepting it gets rid of the trolls for the people who have waited like DPS. The way it was before if you were queing for something specifc, but only one tank ques for it they could easily troll you withdrawing then queing again at lest this way it gets rid of that problem all SE need to do is remove it for the premade full party's and leave it for the partially made party and only give the penalty to the person who didn't accept and the solo party. I'd be fine with that.

[Giantbane]

This is like a soap drama here XD So funny and it's like next time on "Locked out of the Duty Finder" Get over it. You complain about people queing then withdrawing SE tries to fix it maybe not in the best way, but at lest they listened and tried yet you still complain about it's not good enough. It's like trying to give a child and upgraded bike for their birthday, but it's not a good enough bike for them they want it to be designed especially for them. This is an MMO it's not you who's just playing the game it's thousands of people. Sometimes you're gonna get what you want sometimes you're not gonna get what you want. It's not going to be perfect for everyone it's not going to be the best game in history. I do agree on the part that the time to accept the que isn't long enough for some people and that it should be changed so it's longer, but with the new penalty for not excepting it gets rid of the trolls for the people who have waited like DPS. The way it was before if you were queing for something specifc, but only one tank ques for it they could easily troll you withdrawing then queing again at lest this way it gets rid of that problem all SE need to do is remove it for the premade full party's and leave it for the partially made party and only give the penalty to the person who didn't accept and the solo party. I'd be fine with that.

So ... SE makes what you believe to be a bad decision you should just accept it or quit without providing feedback or debating the issue at all? yea...

They half assed this. Some people like it now because it's all shiny and new and they haven't gotten hit by it yet. Wonder if they change their tune a month or so from now when they get stuck with it because of a problem with a group queue or they missed a queue for extremely casual content where withdrawls were not an issue (guildhests) and are not locked out of everything.

[Cedane]

I'm still amused people complain its not good enough but I haven't seen a better solution that could satisfy everybody here. I'm still happy with it. Not many withdrawals as they used to be.

[Giantbane]

I'm still amused people complain its not good enough but I haven't seen a better solution that could satisfy everybody here. I'm still happy with it. Not many withdrawals as they used to be.

an amalgamation of other ideas that have been suggested

The best solution is if a person withdraws from a queue, the queue does not break up the whole group and instead finds a replacement for those who timed out. Those who clicked "confirm" would not have to click it again, they would just stay with the confirmation window up. The game would only break up an existing group of people who already clicked "confirm" if it could not find an immediate replacement. Anyone who withdrew would store a list of groups they recently withdrew from and that person would not be added back into any of those same groups.

But that's more work, so it's better to identify where this was a problem. The only places I saw this were CT/ST, expert, and low level. A common theme between all 3 are that the rewards are heavily stacked at the end of the dungeon, this causes people to fish for in progress in those particular dungeons. There are a number of ways to deal with this sort of thing. One option is to just give them what they want and get them away from everyone else by adding in progress only. This way all the in progress fishers will be removed from your queues forever and will never effect you. There is concern that this would add to the queue times because all the tanks or healers would only queue for in progress. But if all the tanks and healers queue for in progress, then they're going to have to wait a long time because there's only so many in progress dungeons that will be available. They might as well just do the dungeon normally since it will be faster as they already have near instant queues. You'll also probably get more people participating due to the in progress option. Some people won't do certain content at all because the rewards are not worth the time invested (low level comes to mind), but you will likely get more tanks and healers looking for "easy" queues which will increase competition. The result is likely a negligible effect on queues in exchange for a flexible system that lets people do what they want.

You could also obscure the in progress value in the same way that CT/ST does by only displaying 0/1 no matter what the actual progress is. A problem that exists is it can be difficult to fill 0/3 in progress dungeons. You're risking joining in progress on a likely dysfunctional group that hasn't made any progress. Those fishing for in progress are looking for 2/3 or 1/3, this would prevent allowing the in progress fishers from being able to fish for those specific dungeons. This prevents that while helping 0/3 groups that need some help. If in progress only was added, I think this should also be added.

Or you could just not display the fact that a dungeon is in progress at all. Although, I would caution against this. Sometimes people will ask their FC/linkshell for help with an in progress dungeon. It's nice to be able to identify that the queue that pops up is actually in progress so you can help those who you want to help. I know some want to be able to invite friends directly to help in progress runs, but I think that's ripe for abuse (voting out your current dungeon group members because you want to invite your friends). So it's nice to have some way to link those who need help with those who want to help without the direct invite option, and I think this accomplishes that.

Even with the above you can still have people trolling the queue because they have nothing better to do. But a shorter withdraw penalty (5-15min) with a shorter reset period (1-3 hrs) would curb most trollish behavior. For the most dedicated trolls it should be easy for SE to identify people who are *constantly* withdrawing and have a GM check their behavior to put them in timeout. This is also a good idea even if you add some way of directly curbing the practice of fishing.

And lets face it, the primary offender here was CT/ST. While other categories can be subject to in progress fishing, the number of people in CT/ST can mean that players even withdrawing for "legitimate" reasons can cause a number of resets for some people. So it would be better to limit the existing 3/day > 30min penalty to just CT/ST to specifically target *that* problem. Someone who got a strike from going to the bathroom during a particularly lengthy guildhest queue (where the queue estimates are often innacurate) doesn't deserve the strike as much as someone who withdraws from an ST queue after a 30sec wait. The system and its punishments should reflect that, it currently doesn't.

Or just break up the penalty enforcement by category. Trials, 24 man raids, pvp, low/high/expert dungeons, that sort of thing. Again, it was particular categories that were problematic. Withdrawing from ST 3x within a day causes you to be locked out of ST/CT for 30min.

Finally, even WITH the current system, the group penalty should only be inflicted on the individual who withdraws. Group trolling is a made up issue. Punishing people to prevent a problem that doesn't exist is stupid. Ready checks only work when the queue starts. Sure everything works fine if the queue is instant after the ready check, but that's not always the case (had to wait 15min to help out someone do Ramuh HM for story with a partial group that had 2 tanks, for instance). Being punished for the mistakes of others is a bad idea that's only going to lead to more animosity between players and this game does NOT need that.

[Laraul]

There is no notification or warning alerting a person that clicking withdraw will impose a penalty. A lot of people may not be aware that a penalty will be imposed if they choose to withdraw. Without informing the user it won't have much impact. It's not like most players withdraw when queuing anyway.

Penalizing an entire group because of one person withdraws is incredibly noxious to the group and anyone else trying to queue for a duty. One person withdraws, up to six others who are ready and willing are locked out, thus requiring six more people to queue to replace them. Bad idea and blatantly unfair to the players who WANT to participate. It's too easy to forget to use /readycheck... not until it's too late. Thus these players are likely to give up altogether.

I can't say I've seen much change myself with the frequency of people withdrawing after the duty finder has popped. People still withdraw all the time.

[MXMoondoggie]

Penalizing an entire group because of one person withdraws is incredibly noxious to the group and anyone else trying to queue for a duty. One person withdraws, up to six others who are ready and willing are locked out, thus requiring six more people to queue to replace them. Bad idea and blatantly unfair to the players who WANT to participate. It's too easy to forget to use /readycheck... not until it's too late. Thus these players are likely to give up altogether.

You have three chances for everyone to be ready and clicking commence unless people have used up their get out of jail free cards already by withdrawing twice in 24 hours in that case why would you even queue with people like that? It's your responsibility to make sure all are present and ready before you begin and if not you only have yourselves to blame. It'll take a while for the new system to bed in and reduce withdrawals but people are already complaining so they are feeling the effects.

[tocsin]

You have three chances for everyone to be ready and clicking commence unless people have used up their get out of jail free cards already by withdrawing twice in 24 hours in that case why would you even queue with people like that?.

I can think of a hundred different reasons, but the primary one would probably be that if you are on a small server, there aren't really a lot of people to queue with, and sometimes the best players have already been in 10 queues previously that day, and its easy to have a withdrawal.

[Jpblade]

yeah thanks for the duty finder penalty. i now am locked out because the group i was in withdrew three times. I wasn't party leader, nor was I the one who withdrew. But, hey, I should still get penalised for other people shouldn't I? I knew this new implementation was screwy to start with, but this is just messed up.

[Razzle]

Been playing since the start and the only time the withraws were frequent enough to proove annoying was on raid 24 man content. Just have the panelty for raid content. Never had fishing in 4man parties really...

[winxbloom61]

well its to late its here and honsetly i hope it hurts square enix and makes some people quit and makes them loes money it was stupid idea on ses part and i hope it hurts them