Dungeon penalty shouldn't count for queuing something solo

[Valkyrie_Lenneth]

Worse, assuming they even get a replacement. I still remember the time we had to kick a tank in the 77 dungeon last xpac, and despite asking NN plus several LS for a replacement tank and being told by several that they'd queued, the game refused to put any of them in our party - apparently, something can cause DF groups to completely close off to replacements without warning, and it's not even clear what it is.



That's the only part of the problem that's really SE's; in WoW, despite the fact that the penalty is even more stringent (see below, and it also used to not even tick down unless you stayed logged in the whole time, at that), there is a lot more that you can do that doesn't go through the queuing system (especially since stuff where you have to travel to the instance isn't affected, whereas in XIV it is because that interfaces through the DF system as well, but we'll set that aside).

If XIV had more repeatable open world content you probably wouldn't see so many threads like this (frankly, the open world goes criminally under used after MSQ, and I even say this as an inveterate DoH who insists on going around gathering her own materials 98% of the time instead of buying them off the MB).



Yep. As somebody who actually LIKED the Oculus in Wrath of the Lich King, it's very very clear to me that such a penalty is a sad necessity (and may not even be enough, given how many people apparently ditch certain Alliance Raids on sight).



This is also risky in a couple regards (not sure if it's entirely TOS kosher, but more importantly, it raises the risk that if done too often, SE might have to do what Blizzard did - which is apply the 30 minute penalty to people that are vote kicked rather than leave voluntarily, and which massively empowers griefers in WoW so I doubt it would be much better here).



It's 10m idle till you get dismissed from the instance automatically, but part of the problem is that we have a playerbase rabid about saving seconds, let alone minutes, so some people are probably legitimately afraid to even ask if they can afk a moment.

I miss the olden days when people didn't constantly worry so much over small amounts of time (heck, I still remember that time in Shadow Labyrinth in Burning Crusade where the tank had to suddenly tell us she needed to AFK to, of all things, change a personal care item. Things were INCREDIBLY laid back back them. We need these days back, badly).

I'm much more open to waiting if someone actually says something, 5 minutes isn't a deal breaker for me. But communication is important.

[Limecat]

I like how everyone is completely ignoring both the topic title and OP specifically requesting that the lockout not apply to just unsynced solo queuing, and acting like a full removal of the penalty is on the table.

[NekoMataMata]

So you want the game just to crash your client and lock you out completely instead?

You abandoned a "duty", so your punishment is to be locked out of "duty finder", not other activities. You don't want to be charged with tax evasion because of speeding, right? Also, the punishment aspect is probably not even the main purpose anyway, the goal is to prevent "exploitation" so people don't just drop whenever they get something they don't want in a roulette.

And just like every other "laws", it's there to act as a deterrent. As long as it deter majority of people from exploiting, then it does its job even if there are always gonna be some people willing to break or get around it. If your argument is "unless it absolutely stop every single instance of violation it serves no purpose" then we should also get rid of the law of most country base on the same logic.

Basically. The penalty is so light right now. Especially for those of us that play AIN classes. As a healer main I can literally eat a 30 minute timer and be queued back into a different duty within minutes after my lockout finishes. It doesn't exactly help when I can be productive in-game still.

Most non-mmo games that have queues lock you out of the game on that account as punishment and why shouldn't they?

[Iscah]

Worse, assuming they even get a replacement. I still remember the time we had to kick a tank in the 77 dungeon last xpac, and despite asking NN plus several LS for a replacement tank and being told by several that they'd queued, the game refused to put any of them in our party - apparently, something can cause DF groups to completely close off to replacements without warning, and it's not even clear what it is.

Necessary check – is it possible that you hadn't actually pressed the inexplicably manual "find new party member" button?

Also the other player has to have "join party in progress" switched on. Another thing that should be on by default.

[RitsukoSonoda]

Meh... My goldfish set the TV in it's bowl on fire even though it was underwater and I was still able to take care of that and complete the duty. Get some better RL skills :P

[Amarande]

Necessary check – is it possible that you hadn't actually pressed the inexplicably manual "find new party member" button?

Also the other player has to have "join party in progress" switched on. Another thing that should be on by default.

It was indeed showing that it was looking for members on our end, and while it's possible that one or two potential replacements forgot to check "party in progress" I'd be pretty sure at least a few of the several (including some Mentors) who said they'd tried remembered to.

It seems like it's in fact possible for a DF group to become locked to new members without any kind of indication that this is the case. I have seen other similar anecdotes, but under different circumstances (the most notable being a group unable to get a replacement after someone ditched while still in the "starting pen" circle at the beginning of the instance), and I'm not sure anyone has yet ascertained what if anything triggers it, or if it's in fact a random bug.

[TaleraRistain]

I like how everyone is completely ignoring both the topic title and OP specifically requesting that the lockout not apply to just unsynced solo queuing, and acting like a full removal of the penalty is on the table.

Because they're not talking about that. You can drop out whenever you want if you queue something unsynced solo and you don't get a penalty. I've done it multiple times realizing I had queued up the wrong version of something working on ARR relics.

They're talking about queuing solo in DF to get matched with others and having to leave which yes you do and should get a penalty in those cases.

[Raven2014]

Basically. The penalty is so light right now.

Like I said the punishment wasn't the point, the point was a deterrent. I'm someone who play on multiple alt, and it's still good enough to stop me from leaving as often as I would without it.

It's not a hard in your face stop, it's just one of those thing to encourage or discourage certain behavior.

Most non-mmo games that have queues lock you out of the game on that account as punishment and why shouldn't they?

Easy answer: 'cause FF14 is not most other MMO, that's why I play it instead of those MMO.

[Deceptus]

I like how everyone is completely ignoring both the topic title and OP specifically requesting that the lockout not apply to just unsynced solo queuing, and acting like a full removal of the penalty is on the table.

That would require a bit of logic and the ability to bend a bit but those don't exist in today's society.

I agree with OP. Unsync is for personal use in dungeons. The penalty shouldn't apply to it.

[Absimiliard]

What's the point in the penalty if it doesn't lock you out of all queueable content? It's intended as a punishment, essentially the equivalent of being grounded. Being able to ditch on a group then turn right around and do a couple unsynced runs until your timer falls off defeats the entire point.