1 strike for missing a duty? >.> Seems Harsh Yoshi

So I noticed today that after missing a duty once, I got locked out to do duties for 30 minutes. I thought there was a 3 strike rule. When did they change this?

Also, this applied when my leader queued us, but someone was on the wrong job, then all of us could not queue back in. >.>

This does not seem right and is more of a nuisance. Did SE have official word on why they did this? How has the community responded to this. Did the community ask for this? It would seem that there are tons of people queuing for things. Why punish so severely SE?

It should still be 3 strikes. Perhaps someone in your group had their 3rd strike and you couldn't queue because of them?

For clarification: when you say "all of us could not queue back in" , do you mean together as a party or individually?

By Missing a Duty, you mean not pressing 'Commence' when a Duty queue pops?
If so, there's still no penalty for that, at least not the first time, I've never done it more than once in any given day though.

If there is a 3 strike rule, maybe one of the party had already had 2 strikes, and the third was applied to the whole party?

Its 30 min lock out regardless of strike count, 3 strikes nets you a days ban from using the que system. Its to stop people constantly leaving dungeons and requing to get better groups hence the 30min lock out timer.

Quote:

---

Originally Posted by ScarletDawn

Its 30 min lock out regardless of strike count

---

Yes, when you leave a dungeon. But the OP was about missing a queue, not having left a dungeon. For that the three strike system should still be in place.

As i rememeber it is 3. 3 strikes of either running the timer out or hitting cancel when it pops.

Hard to tell without more details. If you got kicked or missed a couple roulettes earlier in the day it might have counted.. not sure. I've never hit the debuff and I've missed a few timers.

You get 30 minute debuff when you leave a duty in progress.
You get a 24 hour debuff when you have accumulated 3 strikes.
Missing a duty queue pop will net you 1 strike.
Missing a duty queue pop in a party (somebody else in your party) will still net you and everybody else in the party a strike.
Accumulated strikes will reset daily.

Should always do ready check before queuing up for dungeons in a party.

Quote:

---

Originally Posted by Fhaerron

Missing a duty queue pop in a party (somebody else in your party) will still net you and everybody else in the party a strike.

---

Is this really confirmed? I thought only the person who failed to confirm would get the strike.

Quote:

---

Originally Posted by Taika

It should still be 3 strikes. Perhaps someone in your group had their 3rd strike and you couldn't queue because of them?

---

I would say it's this. It's been a 3-strike system for a long time. You wouldn't be individually locked out from a single withdrawal.

Quote:

---

Originally Posted by JohnSpawnVFX

Is this really confirmed? I thought only the person who failed to confirm would get the strike.

---

Unless it was changed recently, I do remember in SB I got a strike when somebody in the party was AFK.
That's why we do ready check before queuing up.

Quote:

---

Originally Posted by JohnSpawnVFX

Is this really confirmed? I thought only the person who failed to confirm would get the strike.

---

It’s the whole party that gets the strike, I’ve seen it many times.

Yes. If anyone you are currently partied with misses queue, you get the strike as well. Note that this only applies when signing up for duty as a partial party - if you are grouped with four (for a Light party instance) or eight (for a Full party instance) and someone misses, no one gets a strike.

Basically, as long as you're not inconveniencing a stranger you or your group were matched with, you're fine. If a stranger is inconvenienced, everyone in the party that did the inconveniencing gets a strike.

Bottom line, as was said, don't queue as a partial party unless you're sure everyone in your partial party is ready. And if you check first, and they miss anyway, chew 'em out good. XD

I can confirm this that missing 3 duty commence is not 24 hours. How? I was with 2 others trying to queue for a roulette and the leader was not reading chat. Someone said he needed to go afk and queued up anyway. Then again. The leader had already 1 strike and hit the 3 strike causing a 30min timer.

The thing is if you miss enough to get another queue timer, it goes up to 24 hours.

Quote:

---

Originally Posted by ScarletDawn

Its 30 min lock out regardless of strike count, 3 strikes nets you a days ban from using the que system. Its to stop people constantly leaving dungeons and requing to get better groups hence the 30min lock out timer.

---

Missing a queue 3 times every 24 hours gives you the 30m wait. Missing it once every 24 hours does not. There is no full day ban from Duty Finder present in this game as far as I'm aware: just the 30 minute penalty for too many withdraws and the 30 minute penalty from leaving a duty.

I think they should add to this. If someone misses a queue, they should be logged out when on a congested server. If they're not present for a queue (which is a long 45s timer), they are taking a spot someone could be actively playing in.

What's happening (and has for years) is DPS have a long queue. They queue up and it can take up to 10 minutes to get in. They go afk waiting for the queue to pop. AFK isn't playing. They could be doing something while waiting, but instead they're taking up space. Space someone could be using, someone that might be playing a healer that makes the queues for other active DPS to queue faster for. So not only is this person inconveniencing 3 people, but another trying to login.

Quote:

---

Originally Posted by Kaethra

I think they should add to this. If someone misses a queue, they should be logged out when on a congested server. If they're not present for a queue (which is a long 45s timer), they are taking a spot someone could be actively playing in.

What's happening (and has for years) is DPS have a long queue. They queue up and it can take up to 10 minutes to get in. They go afk waiting for the queue to pop. AFK isn't playing. They could be doing something while waiting, but instead they're taking up space. Space someone could be using, someone that might be playing a healer that makes the queues for other active DPS to queue faster for. So not only is this person inconveniencing 3 people, but another trying to login.

---

It can easily take longer than 45 seconds to go to the bathroom, which I consider likely to be the most common reason for missed queues. Forced logout seems a bit harsh for that.

Quote:

---

Originally Posted by LineageRazor

It can easily take longer than 45 seconds to go to the bathroom, which I consider likely to be the most common reason for missed queues. Forced logout seems a bit harsh for that.

---

Queue when you're done? That's what I've been doing in that situation.

Quote:

---

Originally Posted by Kaethra

Queue when you're done? That's what I've been doing in that situation.

---

When you are so absorbed with what other players are doing that you deny them natural human needs.

Sometimes the bathroom need hits you randomly and you may have been in queue for a bit already, most times you get back before any queue pop, once in awhile you might miss it.

Having to use the bathroom while waiting for queues does not need a punishment lol...

Quote:

---

Originally Posted by Miste

When you are so absorbed with what other players are doing that you deny them natural human needs.

Sometimes the bathroom need hits you randomly and you may have been in queue for a bit already, most times you get back before any queue pop, once in awhile you might miss it.

Having to use the bathroom while waiting for queues does not need a punishment lol...

---

The need always hits me AS the queue pops! Never fails. >.<

Quote:

---

Originally Posted by Miste

Having to use the bathroom while waiting for queues does not need a punishment lol...

---

You do not get punished until the third strike. If you consistently hit three or more strikes a day, that is your problem.

Quote:

---

Originally Posted by einwol

So I noticed today that after missing a duty once, I got locked out to do duties for 30 minutes. I thought there was a 3 strike rule. When did they change this?

Also, this applied when my leader queued us, but someone was on the wrong job, then all of us could not queue back in. >.>

This does not seem right and is more of a nuisance. Did SE have official word on why they did this? How has the community responded to this. Did the community ask for this? It would seem that there are tons of people queuing for things. Why punish so severely SE?

---

It's 3 within 24 hours. So you missed 2 more within the past 24 hours as well.

Quote:

---

Originally Posted by Mholito

You do not get punished until the third strike. If you consistently hit three or more strikes a day, that is your problem.

---

I know of the current system in place already, but the chances you'll have to go to the bathroom and miss it that many times is abnormal so it isn't harsh or anything.

The person I replied to wanted MORE punishment than we have right now for missing a queue pop. So no, we don't need more punishment for simply missing a queue.

Read first. Reply Second.

I've backed out of duties way more than 3 times in a single day.

Does the 24 hour lockout still exist?
I've never seen it, despite fulfilling the supposed conditions for it.

Quote:

---

Originally Posted by Tranquilmelody7

I've backed out of duties way more than 3 times in a single day.

Does the 24 hour lockout still exist?
I've never seen it, despite fulfilling the supposed conditions for it.

---

It doesn't, just misinformation. Past the 3 strikes, you just keep getting the 30minute penalty automatically any failed queues after that.

This is the first i ever heard about a so called 24 hour lockout. Perhaps someone is taking wishfull thinking in some forum post for reality. Or someone only half reading the punishments

Idk what 24hr lockout anyone is talking about here as I have never seen such a thing.

If a queue pops, and either the timer counts to 0 or you withdraw, it counts towards the 3 strikes. On the third strike, you automatically take a 30min penalty including any additional que misses for the next 24 hours.

Leaving a dungeon while the party is full, will also net you a 30m penalty if it includes anyone from Duty Finder.

Leaving a dungeon, if the party is not a full party, will NOT give you a penalty.

If you are kicked from a party in a dungeon, you do NOT get a penalty.

If you are kicked from a party, in the overworld, you cannot rejoin it in party finder.

Only rules that have ever been in play since ARR / Heavensward to my knowledge.

Not sure how hard it is to do, for SE, but a notification on my phone through their companion app when a duty pops would be stellar - sometimes I head downstairs to grab a drink and leave with "estimated 20 minutes" and come back with failed to commence a duty message lol.

I've never received the 3 strike penalty though (and I've missed a few due to bathroom/door/etc, it's obvious when you miss it.. making it is easy to avoid getting the punishment). . . So it's hard for me to say it's harsh. 1 missed attempt would be harsh but as other people pointed out that's most likely not what happened (other person got 3 strikes and held the group back).

If you miss the que pop 3 times you get a 30min penalty. This does not apply if you are in a light/full party queing for a light/full party duty.
If you leave a duty with the party/alliance full you get a 30min penalty. There is no penalty for leaving when the party/alliance is not full.
There is no 24hr penalty.

Is pretty simple guys

Quote:

---

Originally Posted by Shougun

Not sure how hard it is to do, for SE, but a notification on my phone through their companion app when a duty pops would be stellar - sometimes I head downstairs to grab a drink and leave with "estimated 20 minutes" and come back with failed to commence a duty message lol.

I've never received the 3 strike penalty though (and I've missed a few due to bathroom/door/etc, it's obvious when you miss it.. making it is easy to avoid getting the punishment). . . So it's hard for me to say it's harsh. 1 missed attempt would be harsh but as other people pointed out that's most likely not what happened (other person got 3 strikes and held the group back).

---

This would be great, and also give a good reason for more people to use the app. Maybe even (though that's probably too complicated to be able to be implemented) allow you to accept the queue and warn the rest of the party that you're still AFK. While there's potential for this to be abused, people would still be able to freely kick the abuser after a certain time.

Quote:

---

Originally Posted by Miste

When you are so absorbed with what other players are doing that you deny them natural human needs.

Sometimes the bathroom need hits you randomly and you may have been in queue for a bit already, most times you get back before any queue pop, once in awhile you might miss it.

Having to use the bathroom while waiting for queues does not need a punishment lol...

---

Then click Withdraw, then requeue when you get back. I do this myself.

But you know what? I withdraw my idea. Lets keep the 30 minute lockout instead. Its far more than the queue is currently to relogin. Good job your idea is great.

Quote:

---

Originally Posted by LineageRazor

It can easily take longer than 45 seconds to go to the bathroom, which I consider likely to be the most common reason for missed queues. Forced logout seems a bit harsh for that.

---

Can also stuck in cut scene or other Quest dialogue when queuing with a different job.
So I am with you big no to that suggestion

Quote:

---

Originally Posted by JohnSpawnVFX

Is this really confirmed? I thought only the person who failed to confirm would get the strike.

---

Pretty sure it is the whole group - unless it is a full 4 person or 8 person pre-formed, in which case there is no penalty.

There is also no penalty for withdrawing for the queue prior to the duty pop, regardless of whether you are solo or with a group.

Quote:

---

Originally Posted by Kaethra

Then click Withdraw, then requeue when you get back. I do this myself.

But you know what? I withdraw my idea. Lets keep the 30 minute lockout instead. Its far more than the queue is currently to relogin. Good job your idea is great.

---

Your sarcasm aside, I think you're kinda missing the point still. What people are trying to point out is that a forced logout on a crowded server for missing a single queue pop is an unreasonably harsh punishment because there are so many legitimate reasons someone might miss a queue pop while actively playing. Going to the bathroom for a minute, being stuck in combat while trying to change back to the job you queued as, being in a cutscene you don't want to skip because you can't abandon quest to simply rewatch it (Several ShB MSQ cutscenes), just to name a few. Most of those situations come up when queue times are long and players are actively playing instead of simply sitting around waiting.

As for withdrawing from a queue just to use the bathroom, that could be reasonable if your queue times are short, but it's unreasonable to expect someone to do that if their queue times are already pretty long.

Say someone is 19 minutes into an estimated 21 minute queue - would you expect them to withdraw from a queue and potentially need to wait another 21 minutes just to use the bathroom real quick? It's not their fault they need to use the bathroom. They might not have needed to use the bathroom 19 minutes ago. If the queue pops a little bit earlier than the game estimated and they miss the queue, well that sucks for them but that's how the system is set up. Missing the queue pop is already punishment enough, since they have to start their queue all over again. To kick a player off and force them in to yet another queue just to get back into the game they were playing on top of that would be a terrible user experience. It's unreasonably harsh given the other penalties already in place for this sort of thing.

Gonna be honest - getting a strike for cancelling out of 1 duty should be a thing considering that you can use ACT to see what you will go into for your roulette. I believe it's 3 though, is it not?

Quote:

---

Originally Posted by Machka

Your sarcasm aside, I think you're kinda missing the point still. What people are trying to point out is that a forced logout on a crowded server for missing a single queue pop is an unreasonably harsh punishment because there are so many legitimate reasons someone might miss a queue pop while actively playing. Going to the bathroom for a minute, being stuck in combat while trying to change back to the job you queued as, being in a cutscene you don't want to skip because you can't abandon quest to simply rewatch it (Several ShB MSQ cutscenes), just to name a few. Most of those situations come up when queue times are long and players are actively playing instead of simply sitting around waiting.

As for withdrawing from a queue just to use the bathroom, that could be reasonable if your queue times are short, but it's unreasonable to expect someone to do that if their queue times are already pretty long.

Say someone is 19 minutes into an estimated 21 minute queue - would you expect them to withdraw from a queue and potentially need to wait another 21 minutes just to use the bathroom real quick? It's not their fault they need to use the bathroom. They might not have needed to use the bathroom 19 minutes ago. If the queue pops a little bit earlier than the game estimated and they miss the queue, well that sucks for them but that's how the system is set up. Missing the queue pop is already punishment enough, since they have to start their queue all over again. To kick a player off and force them in to yet another queue just to get back into the game they were playing on top of that would be a terrible user experience. It's unreasonably harsh given the other penalties already in place for this sort of thing.

---

No Sarcasm at all.

Right now, if you miss a queue, lets say you were in for 40 minutes. Queue pops you cannot requeue again for 30 minutes to wait for another 40 minutes. That little bathroom break just cost you 70 minutes. That's how it works now.

My solution was to replace the 30 minute penalty. With a queue to get back in. A queue that is what? 5-10 minute tops? But that compromise was rejected for the status quo. So yes, I decided to stay with the status quo since it is far more restrictive then my suggestion.

And yes I've been in queue for 20 minutes at a time only to withdraw, do what I need to do, and then come back to requeue for another 20 min. Though typically I get what I need to get done before I even initially queue. So its uncommon (though it still happens) that I have to withdraw.

But I say leave it as it is. No one met halfway so I don't see the need to myself. My decision is made. You don't need bother trying to convince me otherwise, save the effort.

One thing I found extremely helpful was investing in a pair of wireless headphones, so I can get up and move around and when the queue finally pops, not miss it.

Quote:

---

Originally Posted by Kaethra

No Sarcasm at all.

---

No sarcasm? Your post was drenched in it. Not that I blame you for it, I was pretty blunt with you anyway, but at least own up to it.

All the system does is move directly to the next person in line, nine times out of ten it pops again immediately with a replacement if someone withdraws. What need is there to punish people further than just the current system we have?? Also just FYI the only reason our current system exists is because of people fishing for in progress duties, not due to people simply missing a queue due to bathroom or other reasons.

Does something totally inconsequential to your own play matter that much??

If you want to withdraw anytime you have to use the bathroom quick or go get a drink for that matter then go for it, more power to you, but like the reason most people don't do that is because it is silly and only achieves to waste more of your own time.

Why remove your queue time for that when you are likely going to make it back to your computer for the queue pop? If you DO happen to miss the queue, well sadly you got bad luck and the punishment is one strike and you also have to wait in the queue line again...but the queue you missed just grabs a new person and the people in queue get their duty. What harm was done??

Quote:

---

Originally Posted by Kaethra

Right now, if you miss a queue, lets say you were in for 40 minutes. Queue pops you cannot requeue again for 30 minutes to wait for another 40 minutes. That little bathroom break just cost you 70 minutes. That's how it works now.

---

That is not how it works now. You have to get 3 strikes of missing a queue pop within 24 hours for it to immediately penalize you for missing a pop. If you read my post replying to that other poster you may have seen that missing 3 queues due to bathroom is highly abnormal and not likely.

Quote:

---

Originally Posted by Kaethra

My solution was to replace the 30 minute penalty. With a queue to get back in. A queue that is what? 5-10 minute tops? But that compromise was rejected for the status quo. So yes, I decided to stay with the status quo since it is far more restrictive then my suggestion.

---

Yeah your solution is to immediately penalize a missed queue, EVEN ONE, and log people out. Some servers are quite full and forcing people back into queue just because they declined ONE single queue is ridiculous.

Quote:

---

Originally Posted by Kaethra

And yes I've been in queue for 20 minutes at a time only to withdraw, do what I need to do, and then come back to requeue for another 20 min. Though typically I get what I need to get done before I even initially queue. So its uncommon (though it still happens) that I have to withdraw.

---

So..you've waited in queue for 20 minutes just to withdraw cause you had to go to the bathroom? I mean...if you want but that is such a waste of time. You likely could have got back and still got your queue, or if you happened to miss it then you simply break even. Sure you get one strike for that day, but most people playing normally won't get 3 strikes.

Quote:

---

Originally Posted by Kaethra

But I say leave it as it is. No one met halfway so I don't see the need to myself. My decision is made. You don't need bother trying to convince me otherwise, save the effort.

---

Like spend some time reading Machka's post really closely, she points out a lot of reasons why someone might decline or miss a queue, being punished immediately for a single missed queue is ridiculous. So yeah, no one is going to "meet you half way" on it.

Quote:

---

Originally Posted by Hash_Browns

Gonna be honest - getting a strike for cancelling out of 1 duty should be a thing considering that you can use ACT to see what you will go into for your roulette. I believe it's 3 though, is it not?

---

Right, let's punish everyone because of just a handful of people. Should we start arresting anyone who owns knives at home? I mean, they can also be used to stab someone.

I do blame the system sometimes. The queue said 15 minutes, I decided to go and grab some water for 2 minutes, came back to the pc and bam, I had 10 seconds left on the timer counting down.