Up Commencement Time to 60 Seconds

[Barboron]

reasonable ... limits ...

What though? What are the limits? You are only suggesting something that would cause more problems without any solutions. Seriously, if you made a suggestion and it could prove to be more beneficial, by all means it could be nice. But you're suggesting a work around which will appear to cause issues. It's quite obvious what would happen if it was implemented, it would be expected that SE finds a solution to a problem that the community created when it could have been left out entirely to begin with.

There are reasonable limitations already set in place. A 45 second commencement time, penalty for 3 withdrawals after a group is matched, penalty for leaving a duty in progress. There's a lot of ambiguity with your suggestion of pausing the DF while in a cut scene and, to me, it doesn't seem like it is worth putting resources in to finding a solution when the current situation right now appears to provide fewer problems. Simply saying "reasonable ... limits ..." is in no way going to assist anyone's situation. As I said, if you can propose a system which provides fewer issues by also suggestion solutions to possible problems which may arise, by all means suggest it. But your proposal will have to be scrutinised by not just the community, but the development team. It's no use simply taking the first idea and implementing it and stating it will work, not saying you have but more often than not I have seen players suggest a feature and say that it will work rather than it might.

[Giantbane]

snip

find immediate replacements where possible, skipping those who are "busy"
"pausing" for very short periods of time when replacements are not possible, perhaps 5-15s ... maybe 30s at out the outset
limits to how long a person will be allowed to stay in a "busy" state before the queue stops trying to accommodate them
flexibility to the extents on which the system will go to accommodate those who are "busy", ie pausing without replacements only happens for zone loads, but not other "busy" content. It's likely crafting or cutscenes are not started for "needed" classes and such replacements are likely to be found
track recent inputs and be more lenient with people who are "there" as opposed to those who do not have any recent input.

that sort of thing

I said reasonable limits because I'm assuming SE did not hire their programmers straight out of jr. college and could solve problems for themselves.

[Kogasan]

I seriously think that they need to add more time to commencement because u shouldn't be penalized when a duty pops in the middle of you zoning into another area I've had a duty pop alot when I was zoning into like say mordona and by the time I fully zoned in I was kicked from que either they should add more time to commencement or let us hit the accept button for the que while we are zoning oh and btw I'm not on a PC I'm on a ps3

[Barboron]

snip

I would hope so too and, nothing personally, hopefully they could look for the pros and cons in, not just your ideas, but those of any put forward.

Back to case in point, 45 seconds for a load screen, since you did specifically mention it several times, is just beyond necessary. If someone is having hardware issues that is causing a load screen to be that long, what would they be like in Titan? That's going to hinder the party. I'm not exactly running a modern PC, it would be very low end but it gets the job done, relatively longer load screens than others that I play with but by no means would it be 45 seconds.

As for those crafting, watching cutscenes, if you are too busy to get your stuff done in 45 seconds to press commence, then you're too busy for a dungeon. It's all about priorities. Sure the system isn't optimal for everybody but as of right now, it works and it works well. As much as people love to misuse the word 'broken', this is one of the things that works well. Queues times are not down to SE, it's down to player choice. If a player choose to craft or chooses to watch a cutscene while another players chooses to be available to press commence, fair play to them. Let them enjoy the content they queued for.

As for tracking each individual player's inputs to determine if they are or are no eligible for a pause status on their DF queue is just absurd. This would involve invasive programming to see what inputs a player has on their computer because I commonly tab out for longer periods of time and have my audio running in the background so I can listen for my DF pop, the game could have no inputs for a long time but I am still here. Or yet, I could be afk and using wireless headphones, which I do, to listen for my DF queue. Same issue again, no inputs over an extended period of time but I press commence. Yes, it could go back to what you say and look at a particular player's history of if they do or do not press commence but a player should be ready to press commence anyway, regardless of their history. As a tank, since most things are instant queues, why should I reserve the rights to be afk over anyone else? I say that because of my instant queues, I am more likely to be here, ready to press commence over aDPS who is afk.

[Toodles]

I know plenty of people WELL above the minimum specs for this game who run into the load-screen causing them to miss queues all the time.

That is a problem.

45 seconds isn't enough.

[Ninster]

Just my few cents... is there actually a way to know what story quest objectives will trigger cutscenes when you complete? If not would it be too much trouble to have the game check a player's DF status when a player goes to complete an objective and warn him/her prior to actually advancing with the cutscene?

I myself have never run into the lockout problem and rarely miss commencement times, and I main a DPS job. That being said... I also don't use DF as frequently as other people, so I can't say if my contribution means much. All I can say is plan ahead the best you can and watch the time and party status so you can get a sense of when to expect the commencement window.

[chococo]

Don't start long cutscenes.

How do you know if a cutscene is long before starting?
Genius.

SE sells their story, but do the utmost to make sure you skip it. Just like locking stuff out of duty roulette until you complete it, but that's another topic.

[Tao]

I know plenty of people WELL above the minimum specs for this game who run into the load-screen causing them to miss queues all the time.

That is a problem.

45 seconds isn't enough.

I play on PS4 and even when going to mor dhona I don't have this time of login time so their PC is not well above spec and they should probably buy a SSD and put FF on it they will have like 5s max loading time.

About CS, you need 3 Withdraw in a day to get penalty ... I really think you can cancel your CS after one withdraw so you won't have any chance to be locked out.

I don't understand this thread at least now I don't have more than one or two (for ST) withdraw when seeking.
I'm probably the only one int this topic but thank you SE you have achieved your goal

[Inzoum]

The timer was set at 45 seconds (...) we do not have any plans at the moment to increase this.

What ever happened to "You can craft or level up something else while you wait for Duty Finder to pop"... Have you even tried finishing a 4 star craft, standing back up from crafting pose and switching jobs within the allotted 45 seconds? it's VERY tight. Upping the countdown to 60 seconds is not such a big deal, but it would make a lot of us very relieved.

The current situation means we'd better stick to our job and NOT start anything else while we wait for Duty to be ready.

Basically, we should avoid playing the game while we wait for Duty Finder, in case it pops and we don't have time to finish what we started in the meantime, but we should also avoid NOT playing the game in case it pops while we're not paying attention.

You're suggesting we should stand there doing nothing but stare at the box until it's ready to click.

Quality entertainment.

[IceSpear]

Why is it so hard to just click commence when it pops? I queue as dps, healer, tank and I always click commence, not once ever I had I missed the queue popping since 2.4 went live. And even in the past, I may have missed a queue pop or two in the 6 months prior because I got called to go fix the broken toilet or something and forgot all about the queue. I should have done the nice thing of leaving the queue first, but when an emergency calls, that is priority. So if I get strike I fully deserve it.

So every time I need to go in another room or need to get my dog in I should just leave the que? I don't think so.