Where is penalty count?

[Sove92]

i got locked out 2 days in a row because I was viewing cut scene's when it popped 3 times each day and clicked 'wait' and it ran out. really annoying that they expect you to stand around waiting for a pop and not do other quests while you are waiting, and then if you commence while in the middle of a cut scene it makes you restart the entire thing when you go back? and the cut scene's are not short!

If you are still on the same job, you can just accept the duty. Once you are back, you can continue the quest, the cutscene will restart from the beginning.

Also, the penalty will not lead to actual service suspensions, only prevents joining duties for 30 minutes just like leaving a duty first does, once you have withdrawn a third time in a day. The system exists to discourage fishing for in-prog duties, which was a major annoyance to everybody else in the queues, when the fishers always withdraw if the duty pop is not an in-prog.

[CaptainLagbeard]

You have to manually keep count of them, but it should get cleared after 24 hours of the warning, or alongside the daily reset. Not entirely sure which.

You won't get into any trouble if you do hit 3 warnings, you're just locked out of the Duty Finder for their duration.

[Lazera]

I know this is an old thread but I wanted to remark as I had a different situation.

I joined The Tower at Paradigm's Breach when it first launched. I managed to make it in but my internet was being crappy that day, or the servers were having disconnection issues. This happened twice and each time, I logged back in dead. The raid had been going on for about 12 minutes at this point, so I figured 12 minutes have passed, I should be ok to leave. With that said, due to the prior disconnects and reconnects, I was logged into the raid for less than that time. Regardless, I left. Despite this being my first infraction, I suffered a 30 minute penalty. While many say that it's a 3 strike rule, my experience says it only needs to happen once, unless the servers track your disconnects and count them towards the amount of strikes that you have.

If this is true, then being penalized for getting disconnected is a very stupid system to have in place.

[Aurida]

Despite this being my first infraction, I suffered a 30 minute penalty.

Yes, the three strikes is a tally specifically for not accepting queues. If you leave a duty once it's started, you get a 30 minute duty finder lockout that's separate from that tally completely, with the exception of if you're not the first one to leave- if someone's previously left, or been vote dismissed, you can leave without penalty. Since you were the first one to leave the duty, you got hit with the 30 minutes.

The penalty count for not accepting duty pops is separate from the one for abandoning a duty in progress, though.

[Menriq]

I know this is an old thread but I wanted to remark as I had a different situation.

I joined The Tower at Paradigm's Breach when it first launched. I managed to make it in but my internet was being crappy that day, or the servers were having disconnection issues. This happened twice and each time, I logged back in dead. The raid had been going on for about 12 minutes at this point, so I figured 12 minutes have passed, I should be ok to leave. With that said, due to the prior disconnects and reconnects, I was logged into the raid for less than that time. Regardless, I left. Despite this being my first infraction, I suffered a 30 minute penalty. While many say that it's a 3 strike rule, my experience says it only needs to happen once, unless the servers track your disconnects and count them towards the amount of strikes that you have.

If this is true, then being penalized for getting disconnected is a very stupid system to have in place.

This a different. Your penalty is because you left a fully filled duty before it was complete.

[CaptainLagbeard]

I know this is an old thread but I wanted to remark as I had a different situation.

I joined The Tower at Paradigm's Breach when it first launched. I managed to make it in but my internet was being crappy that day, or the servers were having disconnection issues. This happened twice and each time, I logged back in dead. The raid had been going on for about 12 minutes at this point, so I figured 12 minutes have passed, I should be ok to leave. With that said, due to the prior disconnects and reconnects, I was logged into the raid for less than that time. Regardless, I left. Despite this being my first infraction, I suffered a 30 minute penalty. While many say that it's a 3 strike rule, my experience says it only needs to happen once, unless the servers track your disconnects and count them towards the amount of strikes that you have.

If this is true, then being penalized for getting disconnected is a very stupid system to have in place.

You get a separate penalty for leaving a duty while the party is full. That one lasts 30 minutes.

I do believe you still get a strike from it as well, and if you get the full 3 strikes, it's a 24 hour block from the Duty Finder.

[Aurida]

You get a separate penalty for leaving a duty while the party is full. That one lasts 30 minutes.

I do believe you still get a strike from it as well, and if you get the full 3 strikes, it's a 24 hour block from the Duty Finder.

No, that's not true. I think that one was wishful thinking from people angry that mentors in mentor roulette would leave synced EXs, but you can leave duties all you want if you're fine with the 30 minutes