Cannot re-queue on Duty Finder for 15 minutes?

[Bluevann]

Ok, first off I want to apologize in case this was discussed elsewhere, I DID search for this issue on the forum but couldn't find anything about it even with specific keywords, so I decided to take it on a new thread.

I decided to spiritbond some gear on my tank that I didn't want anymore to turn into materia. I quickly get invited to Tam Tara deepcroft, but within a few seconds I learn that the miqo'te conjurer in our group is a cure bot set up by one of our DPSs. I never adopted 3rd party tools and the last thing I want is to support those who do, I left duty thinking I could queue again and find a more honest and efficient group. But when I am back in Gridania and open up Duty Finder I find all the possible duties locked, and the window saying this:

You are unable to undertake any duties at this time.
Time remaining until Duty Finder is available: 15 m.

I would just like to know when and why was this implemented? While after all I don't mind having to wait for 15 minutes, I feel kind of punished for not accepting to tag along with a botter. Could there be a way to avoid this treatment for special cases such as mine? But really I'm just curious to know what this feature is supposed to help with.

[Kaela]

Yep this is happens if you are the first to leave a group.

Edit: Adding this in because, while I agree it does suck. It happens. I wouldn't would of wanted to party with someone who was botting either. Though I honestly hope you reported them, that would make that 15 minutes wasted more worth it in my opinion.

[Bluevann]

I wouldn't would of wanted to party with someone who was botting either. Though I honestly hope you reported them, that would make that 15 minutes wasted more worth it in my opinion.

Believe me, I really would've liked to report it. Unfortunately though dungeons cross servers, and I cannot report a player if I can't specify the server they're on. I even tried to look the bot up on the Lodestone, but there are several miqo'te with that name, and I don't want to risk reporting an honest player >_<

[Kaela]

Believe me, I really would've liked to report it. Unfortunately though dungeons cross servers, and I cannot report a player if I can't specify the server they're on. I even tried to look the bot up on the Lodestone, but there are several miqo'te with that name, and I don't want to risk reporting an honest player >_<

You can still report them. I did it once for a jerk I had in DF. I just put the name of the person who did it. Explained to them what happened and mentioned it was in DF and didn't know what world they were from and let them take it from there. They got their own logs to look back at this stuff I am sure. They gotta.

Which it is sad, you don't know what world a person is from. It would make things so much easier. However, the reason they probably don't do it so it doesn't cause fights between non-legacy and legacy as it did in Beta. I honestly dunno.

[Mishakai]

You can still report them. I did it once for a jerk I had in DF. I just put the name of the person who did it. Explained to them what happened and mentioned it was in DF and didn't know what world they were from and let them take it from there. They got their own logs to look back at this stuff I am sure. They gotta.

Which it is sad, you don't know what world a person is from. It would make things so much easier. However, the reason they probably don't do it so it doesn't cause fights between non-legacy and legacy as it did in Beta. I honestly dunno.

Write the name down then do a lodestone search. That usually narrows it down a lot.

[Kaela]

Write the name down then do a lodestone search. That usually narrows it down a lot.

I agree. This is something I really didn't think of due to what happened. I was just upset at the time to be honest and felt it important to report what happened.

[Eztam]

Believe me, I really would've liked to report it. Unfortunately though dungeons cross servers, and I cannot report a player if I can't specify the server they're on. I even tried to look the bot up on the Lodestone, but there are several miqo'te with that name, and I don't want to risk reporting an honest player >_<

You could have just searched both the main and bot names in lodestone....find the one with same server as the main guy and report.

[Raskbuck]

I would just like to know when and why was this implemented? While after all I don't mind having to wait for 15 minutes, I feel kind of punished for not accepting to tag along with a botter. Could there be a way to avoid this treatment for special cases such as mine? But really I'm just curious to know what this feature is supposed to help with.

Fortunately, that penalty only applies to the first person that leaves the instance; meaning that if someone else leaves before you, you would be able to leave and re-queue right away. I'm sorry to hear about the experience you went through. We can only hope you won't find another player that uses bots through the Duty Finder.

[EgweneALvere]

The first person to leave duty finder before the instance is finished gets the 15 minute lock out. As far as I remember its has always been this way. SE has it in there to discourage people from leaving instances early. I know it sucks in your case but I would have left too had I become aware someone in my DF party was botting.

[Alhanelem]

It's been in the game since ARR went into beta; It is designed to discourage people from bailing out of a run in the middle. The people after the first aren't penalized because they've been screwed over by the first person to leave in most cases, particularly the primal fights.