Thank you SE!! (DF lockout)

[BobbinT]

I was wondering about how many this fishing issues arise. Didn't really notice many reports in forum about it since there are many more important issue/discussion. I also among many who uses DF several times in daily since it was introduced, and felt their up and downs. Aside from the initial complaint of how long the wait are, SE has provided more and more solution to make DF less painful, even through other means like the recent nexus upgrade system.

So far my only suspect for current penalty is to help SE prolong their MMO live, sort of Dynamis style lockout. I do felt currently that the content so far getting less and less motivated, especially after you reached many goals before the next patch hits. This even includes the recent introduced relic nexus upgrades which in the end feels getting more monotone.

I mean for any of you sounds happy of this implement, are you really getting so pissed and getting way too many so-called DF commence interruption? I do play almost continuously since beta, only taking few break for that XI free login campaign which happened twice. I do too, must have about similar amount of DFing with any of you averagely. So why I don't feel less annoyed as you did? Especially since I main-ed DPS class (BLM & BRD) which should have the most amount of DF queue time. And yes, I do have tank & healer job, but that's only to help players on old content mostly since tank/healer help DF commence faster.

The only time I ever intentionally 'fish' are when someone in LS cry for help, having bad luck with their party and their tank and/or healer leaves. Then I ask them how far they progress then hit join in progress to match their current progress. That's where my truly fault is, which I admit withdrawing for like only several times. And even if I did land on wrong one, I still decide to continue with whatever party I landed on. That I admit my guilt, despite the intention for helping.

The rest, as others have laid out, are only because in middle of doing something that I hope I can finish as quick as possible so that I can hit that commence button, either crafting/RL stuff/others, which is quite unintentional.

So again, with all these arguing, a question rose from me: is this the only reason? because many ppl getting too much commence cancellation? or am I just too patient/ignorant?

Seeing all these debate makes me miss the old 1.0 way of partying and doing dungeons. We shout, we organize, and we bonded. The introduction of DF easiness somehow makes ppl more and more spoiled to the point of having weird debates and weird rule implementation. And most of all, ppl clashing because of it and more drama over nothing.

Should I really be thankful as what this thread should be all about, or I just nod and pass along? It's not like the end of the world.

[LineageRazor]

I know they have a in-progress button but, maybe they should add a in-progress only button as well.

SE's goal is not to give fast runs to impatient people. Their goal is to assist partial parties into becoming full parties, for whatever it is they're trying to get done. When you click that checkbox, you are not telling the game, "I'm impatient or low on time, so gimme a quickie." You are telling the game, "I sympethize with folks who've lost members mid run and would like to lend a hand if there are any out there." If your actual feelings are more in line with the former than the latter, well, sorry, but that wasn't the intent behind the feature, so you'll have to deal.

I think it's funny how many people are getting upset over this new feature. One thing I don't understand is people saying "I don't abuse the DF but what if I miss it three times because I was doing something else?" If you have something else to do shouldn't by all logic do that first?

If you're a job that typically has to wait thirty minutes or more for your queue to pop, you have three options: Do other stuff outside the game while you wait, do other stuff in game while you wait, or stare blankly at the screen, doing nothing, until your eyes explode. If you choose the second or third options, you won't miss your queue, but if you're doing the first option, you could easily miss the queue depending on what you're doing and whether it drowns out the Duty Finder chime noise. And if you miss your queue? Well, that's another half hour wait. Chances are if you picked option one the first time, you'll do the same the second time. And the third time. And if you miss the chime all three times, well, you're done for the day.

That said, I think this will VERY RARELY be a problem. Even if there ARE folks who regularly miss queue three times or more under the current system, once they know about the "three strikes" penalty they're going to be a lot more careful once they've missed a queue or two.

[Saviorlito]

If they give us an option to give the queue-sound a different volume than the rest of the game, that would suffice. Having the entirety of the background sound enabled, hearing every goldspam whisper and so on, isn't really ideal.

System Settings > Sounds > Mute everything but system sounds and raise it to max. Problem solved. I do it all the time while I watch Netflix.

Edit: I also do it for Crafting Macros. Once you hear the item dropped in your bag (system sound) it means the craft is complete, you hear the crafting window open again, Press X twice (controller) wait for the next system sound, then hit your macro (controller). You can craft for HOURS AND HOURS and never have to open the game window. It's pretty neat when I'm walking around the house or watching Netflix or doing other things and can just listen for that sound.

[Eidolon]

Well, this is going to suck when you're trying to ask one of your friends to join the instance after your tank/healer bailed. They'll try once, then give up. =/

Just this week, I was running Brayflox Normal for a friend. Our Healer left us after the third boss for... gods know what reason? And we were left without a healer for the remainder of the dungoun.

We most assuredly we were in the que. It said 'Finding members' at the top-right. Yet no matter how hard my freinds tried to join my que? They kept getting fresh/brand new ones, with the /in progress/ box checked.

Tell me ,how is this fair to them - if they try to que in progress - that they would get these non-progress ones while trying to help me and suffer a detrimental effect if they don't take the one they're not intending?

This is my only concern. I fear it hurts those of us with good linkshell networks of friends who need a replenishment. =/ Even more than the broken/faulty system we have now.

[NyarukoW]

Well, this is going to suck when you're trying to ask one of your friends to join the instance after your tank/healer bailed. They'll try once, then give up. =/
....

How is this related to clicking withdraw or not clicking when the DF pops? They can still join progress. And if they joined the wrong one, they can ask for vote kick or leave and join again and never have to incur a withdraw strike for not commencing with the DF. Seriously this is completely unrelated.

[Eidolon]

How is this related to clicking withdraw or not clicking when the DF pops? They can still join progress. And if they joined the wrong one, they can ask for vote kick or leave and join again and never have to incur a withdraw strike for not commencing with the DF. Seriously this is completely unrelated.

1. There's a 5 minute lockout for votekicking someone from the start of the duty.
2. How rude are you to join someone else's instance and say, "Hey, sorry, this wasn't the duty I wanted - Can you kick me?" and thus penalize these people as a vital role such as this?

It is 100% connected to clicking / not clicking withdraw. Because sometimes we try to 'que fish' because for whatever reason, the que without a single Tank/healer/DPS isn't getting que'd into. And me askin my friends to join is now a liability to them, because if they click wtihdraw, they are now building their own penalty by it.

[DracotheDragon]

a whole 24 hours for saying no 3 times .. i do like this but also dislike this, 3 times is a very short number,

think about it this way lets say you have a long queue and you pop off for the bathroom and it pops (1) ok so lets try again, oh wait i was called away .. the queue hasn't popped i won't be a minute it pops while your gone (2) ok re queue this one seems shorter wait "90K'd" but i'm still logged in (3 logged in DC'ing character didn't accept when it popped) with this short example the 3 strikes rule can be very bad

mayby.. 10 strikes in 24 hours? something still small but enough to account for all the small errors.

or hey maybe a after the 3rd time you get incrusting blocks 3: 5 mins 4: 10 mins 5: 15 mins: etc

[HEC-]

ONLY if they can allow direct invites to the dungeon.

I hope this would never happen! Why? Well - while someone like you might use it for actual benefit of abandoned group (although there will be more partial groups out there which you'll effectivelly put at "disadvantage" by this) what will soon start happening is that group of "friends" will kick strangers before last boss or wanted loot chest and invite one of their own to "help" (themselves to loot or easy run etc.). So - no thank you!

I don't think this system will have a very noticeable effect on my playing habits.

You seems to be missing point here - nobody realy cares about (change of) your playing habits. What do they care though is that you by either stopping playing entirely or by being able to time out / decline duty limited amount of times will stop wasting their time!

[Fornix]

How is this related to clicking withdraw or not clicking when the DF pops? They can still join progress. And if they joined the wrong one, they can ask for vote kick or leave and join again and never have to incur a withdraw strike for not commencing with the DF. Seriously this is completely unrelated.

Because the join in progress toggle means not "join in progress only". But rather it means "join new or in progress".

Whenever FC mates would ask for a tank after theirs ditched them, I would frequently get in the range of 10 ~ 20 new runs prior to getting an ongoing run. Often being the one my guildies were in.

Don't ask me why the join in progress toggle doesn't allow players to join in for only in progress runs. SE logic I guess. Just as much logic as such a penalty as this over missing 3 pops in an entire 24 hours. When it comes to the way the DF functions, there's a lot left to be desired. And these sort of updates aren't making it any better.

Once I've capped all my leveling classes to 50, I'll be letting it pass completely in its current state.

[Noxifer]

is the df lock out for some time or rest of day?

They haven't said anything specific regarding the lock-out, which leads me to believe it'd be the same lockout as the penalty for leaving an instance (i.e. 30 minutes). That's just my guess, though.

a whole 24 hours for saying no 3 times .. i do like this but also dislike this, 3 times is a very short number, [...]
or hey maybe a after the 3rd time you get incrusting blocks 3: 5 mins 4: 10 mins 5: 15 mins: etc

I think I can say with some certainty that it's not going to be a lock-out until the dropout reset. Why? Because the wording was "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". If you get a lock-out for the rest of the day, you're not going to withdraw more than three times because you won't be able to queue up again after that. So the "or more" part wouldn't even have been there.

I like your theory about an increment in duration of lock-out. It would also be an interesting way for them to do it, but I'm still leaning more towards them taking the easiest way out and applying the same lock-out that already exists as a penalty instead of coding in a new one.


And for those of you that worry that the penalty will apply if you withdraw from queueing, the patch notes state that you have to withdraw/time out from the Duty Ready confirmation window (see above). Which means when the queue pops, not when you enter queue.