Duty commencement

Small suggestion, take away the option to withdraw once a party is formed for any dungeon or raid, i am sick to death of being in queues for 40mins+ as a TANK and people withdrawing as the parties are formed.

For example today, i was in a queue for Syrcus tower as my Warrior for 1 hour 22mins, and the party was formed, i counted, 23 times, and someone always withdrew, not sure if they do this deliberately, but it happens a lot...too much.

If you can't take away the withdraw option then make a time lockout, for example, if they withdraw once a party is formed, first time is 5mins, then 10mins, 20mins, 30mins and so on.

Constant withdrawals like that give me heart palpitations. Wait time last night for CT was 1.5+ hours. When it popped I nearly jumped out of my chair. Then came the withdrawals... Then pops... Etc..surprised I didn't have a heart attack.

yes, lets just not give players the option to not do a dungeon. been afk for 30 minutes? doesnt matter, youre still doing the dungeon anyways.
imagine doing a 4- man, and 5 minutes into queue, thet tank's child falls and has to be taken to the emergency room. now youve got an afk tank, that has to be kicked and replaced, all because someone was so butthurt about being inconvenienced that they didnt let people not eneter the dungeon.

and a lockout for withdrawing? lets punish people because they didnt criple you inside the dungeon.

I can understand that, i have a child myself who is accident prone, but this is why i suggested the temporary lockout aswell, if your in the queue for a 4-man dungeon, your max waiting time even as a DD class would be around 10-15mins, that's time plenty enough to make sure everything is ok, you have the time to wait, however, with 8-man or raids, after waiting for so long then someone withdrawing JUST as the window pops, it is disheartening and puts you off queuing 1 hour + for that again.

If the dungeon has started and you need to do something IRL, that's fine, you can usually say "bla bla bla, 2 mins, sorry" but after queuing for so long and the duty is about to commence then it's agitating, the lockout could be a big help, and as i said it could be short times, and if people withdraw for something like as you said, to help their child, then really, 5 mins is enough time to sort their child out, comfort them, and make sure they are ok, otherwise, what's the problem.

Maybe i am butt-hurt, after playing this for so long, and speaking to others, they agree, and after meeting some people and having them admit sometimes when they are bored, they join queues and withdraw just for the heck of it, i know this solution would work, i wouldn't understand the negativity towards this idea, because as i said, if something happens IRL the lockout will be over by the time you get back, then you can queue again.

"thet tank's child falls and has to be taken to the emergency room. now youve got an afk tank, that has to be kicked and replaced,"

I am pretty sure, as a father myself, that if my child had to be taken to an emergency room, that i could not care less, if i was kicked and replaced.

For me that is off limits, sometimes you just are doing important things and can't accept it, even if you were waiting for hours. You could be watching a cutscene or doing a S hunt, man simply live with it, it will not change.

I know that there's indeed some people that like to do the "in progress search", that queue for duties and only enter if it calls for the ones that are already finishing just to get the daily bonuses and things like that.

It's like wanting to delete the private messages just cuz you get spammed by gold sellers. The system is not bad, the people that use it are.

How about Duty Finder automatically withdraws you from queue if you're AFK for x amount of time?

This will of course not solve the countless number of people who withdraw when a hunt pops, but it will purge those who clock out the timer because they went to make pancakes or whatever.

Quote:

---

Originally Posted by Nevaldus

Maybe i am butt-hurt, after playing this for so long, and speaking toothers, they agree, and after meeting some people and having them admit sometimes when they are bored, they join queues and withdraw just for the heck of it, i know this solution would work, i wouldn't understand the negativity towards this idea, because as i said, if something happens IRL the lockout will be over by the time you get back, then you can queue again.

---

dont get me wrong, i hate when im queueing for primals in the hope of newbie myth rewards or getting into st, the withdrawals grinds my gears to no end, but it seems like every suggestion on how to fix it always ends up with a negative effect for the people who have legitimate reasons for withdrawing or for the timer to run out. thats my problem, that theres no way to target just the people causing problems

ill be honest, i overlooked the smaller timed lockouts, and 10 minutes really isnt that bad, unless youre dps, but you can always ask for help with the queue, as i have done when leveling. i could agree with something like that though, hopefully starting out at a smaller number and possibly just for said instance, so you dont waste time waiting for a complete lockout to lift.

Quote:

---

Originally Posted by Nevaldus

I am pretty sure, as a father myself, that if my child had to be taken to an emergency room, that i could not care less, if i was kicked and replaced.

---

the problem isnt for the tank, its for the group that has to kick the tank. queue times are almost non-existent for most content, so there is almost no reason to join in progress, so tanks are a hard role to fill. on a 4-man dungeon, it can cause problems, completely crippling the group once the tank is gone.

Quote:

---

Originally Posted by FaizeD

How about Duty Finder automatically withdraws you from queue if you're AFK for x amount of time?

This will of course not solve the countless number of people who withdraw when a hunt pops, but it will purge those who clock out the timer because they went to make pancakes or whatever.

---

some people(myself included while dps) will queue up, and go afk. ill be on ifunny, or ill be on youtube. that doesnt solve the issue of withdrawals without punishing people who are technically afk, but still within arms reach of a mouse/controller.

One thing I think might be a design flaw (or some kind of flaw) is how you'll get 3/6/14 for example ready up for ST immediately, 15th DPS neverout, it repops immediately and you'd think- ok gonna be 3/6/15 this time because all readied up but one DPS and they're at the back of the line. But nope a new set of players gets in the mix vs. those who just readied up with you and you get something like 2/2/15 -> Withdraw/Timeout. It seems unlikely to me that so often, 23/24 people would ready up, and when it fails because of one person and repops immediately, some of those people why readied up before are now afk or queue fishing for in progress?! It's stupid to make everyone who readies up start over with a new party building up. A friend and I queued for ST yesterday and got a pop in 2 minutes... 1 DPS made it expire... it popped again, 15 DPS's readied up but 2 or 3 Tanks and Healers didn't. Then we had to wait 30 more minutes for a new party when we already had 23 people willing to start to begin with. Primarily to blame is the design where it doesn't keep those who ready up together in the same group and simply replace the non-starters... too many times, each queue pop is like a new roll of the dice.

"Players who select Withdraw from the Duty Ready confirmation window or allow the window to time out without making a selection three times or more in one day, will be temporarily prohibited from registering for duties via the Duty Finder.
This count will reset every day at 9:00 a.m. (PDT)."

Source: http://eu.finalfantasyxiv.com/lodest...441d852#battle


Thank you so much! This was exactly what i wanted.