Just blame the players for abusing the system that was designed to allow players open for entering a in progress dungeon to help out a party that lost a member for whatever reason, not to fish for your own personal benefit.
I'm still confused as to how Join a party in progress also = new group.
I think the basic fix and function to the issue is right there.
Marked the only true part. Everything else is on your mind.
Somehow people start creating ideals and rules in their minds and wants to force everyone else to follow it.
this is a cause and effect situation. the effect is people fishing which is annoying, yes. but the cause is CT itself. the raid came out at a time that is less than optimal. personally, my main is almost full 90 while my back-up (and only other job) uses CT for gear. after finding out which piece drops by which boss, i then cater my run towards that particular goal. i am a fisher but not for a 2/4 or 3/4. the only items i need are from the 1st two bosses and myth tomes are easier to get then candy. moral of the story, not everyone who fishes is looking to swoop in on the last guy. sadly, i only see it getting worse in the future which is why after 2 more weeks or 1 week and 1 lucky coil, i will be able to avoid that entire mess until 2.3!
Player
i don't see how that would limit Fishers in any way, that would actually seem to GREATLY ENCOURAGE it unless there was a lotting restriction on join in progress such as Greed Lot only or something, why should a last minute entry into a dungeon get the same lotting access as those who did all of the legwork to get to AchgeronPlayers can have a multitude of reasons for exclusively joining in-progress, including desiring CT loot near the end of that dungeon. Again, the more appropriate solution in this instance is to delay all loot until the very end; Acheron should reward 4 pieces, instead of having each mini-boss reward 1.
It's not designed for you to only get an in-progress dungeon. It's designed to ALLOW in-progress instance if they come up before a new lease does. Square does not (nor should they) want you to be able to selectively queue for dungeons that are half completed. Do you have any idea what that would do to queue times for CT?If I queue for a dungeon "IN PROGRESS", why the rat should I deal with a dungeon "STARTING NOW, NOT IN PROGRESS"?
Don't blame the players if the system is flawed and doesn't work properly.
If a player checks the "IN PROGRESS" square, put them ONLY in dungeons in progress, or in none at all.
So, different queues. Problem solved.
before anyone gets more warped ideasIt's not designed for you to only get an in-progress dungeon. It's designed to ALLOW in-progress instance if they come up before a new lease does. Square does not (nor should they) want you to be able to selectively queue for dungeons that are half completed. Do you have any idea what that would do to queue times for CT?
What they really want you to do with the in-progress option (9:00-11:00)
all they have to do is put in a 30 or 60 second cooldown on missed or ignored queue pops and it would fix the entire problem.
for people playing normally and something comes up that causes them to have to miss a queue it would be completely negligible
for people that queue 50 times in 5 minutes looking for an almost finished dungeon it would turn that 5 minutes into 25/50 minutes completely destroying the reason they're doing it to begin with
Why do people want to finish dungeons faster by getting last boss ?
Because the game isn't fun and they only want the myth tomes for gear ?
Solution : Make game more fun .
|
![]() |
![]() |
![]() |
|
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.