becaues you never know when someone is gonna drop from a dungeon and you want to be the first one in to that inprogress group.At the same time, why was the person doing the withdrawing making love to the queue button? It's obvious the queue is trying to pair them with a fresh group. Instead of queueing up 5 times per minute, they could have just waited a few minutes then tried again to give the DF time to ship that party off with another player. Who's to say another player in the needed role wasn't queued but during one of those times when spammy got paired with the same group, the second player got diverted off to the next group waiting in line?
Omg i have to look at my screen.... what ever shall i do... its the end of hte world god help us all!
Blind entering would only put a player in in-progress parties if the player had checked the box in DF (as it does now). You'll never have to worry about skipping bosses/loot if you don't have it checked.The other method of *blind entering* is not a good one *in my opinion*. I never liked this in WoW, and you can often times skip a boss you might have either wanted loot or philo tomes from. This also can happen when queuing as a full group keep in mind, and could screw a lot of people (including DD/heals) out of gear.
Personally, I think it's the best solution.
I think there should be a penalty for withdrawing. Nothing too harsh, like 2-5 minutes with no DF use for withdrawing 3 times in a row, and each subsequent withdrawal accumulates more total time per week or something. So first offense is say 5 minutes. Withdraws 3 more times = second offense: 10 minutes. Third 15, etc. It would deter "in progress fishing" and it's not much of a penalty. If they get in and leave duty it gives them the 30 minute wait, which is a far steeper penalty. Just a quick thought, kinda just popped in my head seeing this thread.
The join in progress button is there so if a duty gets partially abandoned for whatever reason the people who started the duty aren't completely screwed out of completing it, not so "I can get a quick run to get X gear or tomes with little to no effort."
-You're assuming that that is only 1 person spamming the cue box. It could actually be multiple people. Multiple People who if 'forced' to join somehow (either blind cues or by being temporary unable to recue for 5-10 mins etc) would have allowed that party (and probably a couple others as well), to enter the instance, at least, judging from this SS, 7ish minutes faster. (IN a WP run, that's half the dungeon if speeding running for an idea of 'what's my time worth')right but thats not doing anything to you...... you dont have to click commence every time that pops.... and if that person wasnt queueing you still would be waiting all that time for someone looking for a full party anyways. So nothing changes except a little bit of spam of the window popping up.
-If it IS one person, you and I both know, that was not the intent of 'Join Party in Progress'. But even so, until that ONE person stops holding that group hostage, not only can they not enter...but a willing party member who'd fill that slot ALSO can't join. Again, wasting not only the people cued for that instance's time...but people waiting to cue.
But to be clear, judging from how it 'works' for Tanks esp. to keep spamming until they get what they want, that was NOT 1 person cueing, but rather at least a handful spamming and declining. So yes, safeguards that would ensure that people 'take the cue they get', would make it so less people wait. And would also shorten cue times. Because it took these 'withdrawl ppl' at least 7 minutes to cue...multiply that out by every instance, on every world and you start having lots of people waiting for cues that are basically made longer for the convience of a few.
And again, I cannot stress this enough: 'Join in Progress' isn't a speed/skip button. It's an 'Sure I can help you button'. It was put in game as a way to help out a stranded party, NOT as a means to speed run to the loot/tomes/reward.
I don't agree with 'punishment' systems either...but it really is the only way to get through to the types of players who abuse the 'Join in Progress' feature this way. Afterall, they don't see anyone else's time, progress or loot as valuable, so the only way to get through to them is to make it less enticing to spam the cues until they get what they want. Make it take them LONGER to re-cue than it would take on ave to run the whole instance, and they'll just take what they get
Yes for 10mins or longer every time it goes into commence mode.
What's so hard to understand? Yes both can take just as long but one makes it so you have to keep checking. For something that can take nearly an hour at times, it's a major inconvenience.
Last edited by Doo; 01-15-2014 at 03:29 AM.
That is true, I was thinking a total blind enter without the option. If it were still an option then you are right this would be a comparable/good solution. The penalty method on a number of withdrawals would work similar, but still let people know if they are joining an in progress or not. I kinda looked at that as a win, as well as encouraging people looking for in progress groups to stagger their queues, instead of click off and on constantly.
Except that of the 40+ in 20-25 minutes (no, that's not even an overstatement) windows that popped last night before I got my CT run, around 1/3 of them lasted longer than your 10 seconds. So now what? Even with waiting a little time before changing class and accepting the dungeon, I wouldn't have been able to do anything during these 20-25 minutes. Am I still not negatively impacted by this behaviour?
The conspiracy deepens.
3 Lalafel
Same server, same FC.
Angiline
Cichard
Mailstrum
All believe that one person's time is worth more than 23 peoples time.
According to the TOS there is no rule about showing up at your house and poking you in the eye with a spork. Still does not make it ok.
Does SE actually have to explicitly say something isnt ok before you will realize you were wrong? Can you imagine how long the TOS would be if they had to allow for every possible occurrence of douchbaggery?
Edit
Haha was doing just that!
if the queue lasts longer then 10seconds then thats not someone looking for an inprogress group. the whole point of doing that is to get in fast waiting 10+s before dropping would defeat the whole purpose of doing it. no you are not negatively impacted you still can craft or gather or what ever before you have to commence there is a 30second window for a reason.Except that of the 40+ in 20-25 minutes (no, that's not even an overstatement) windows that popped last night before I got my CT run, around 1/3 of them lasted longer than your 10 seconds. So now what? Even with waiting a little time before changing class and accepting the dungeon, I wouldn't have been able to do anything during these 20-25 minutes. Am I still not negatively impacted by this behaviour?
What law explicitly says, someone from the internet may not poke you in the eye with a spork?
This, could be applied to the situation of DF-ditching as it disrupts the game experience of other players, and disrupts the the instance servers normal functions.From the FINAL FANTASY XIV User Agreement
3.2 Disruption. You may not in any way disrupt or interfere with the Game experience of other players, including the disruption of Square Enix's computers and servers.
Also, according the the forum rules: http://support.na.square-enix.com/ru...la=1&tag=forum
There is nothing explicitly against linking the Lodestone Character sheet, that is linked to the user name of a player participating in a discussion on the lodestone forums.
Last edited by Kazamoto; 01-15-2014 at 03:47 AM.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.