Results -9 to 0 of 220

Threaded View

  1. #10
    Player
    Giantbane's Avatar
    Join Date
    Aug 2013
    Posts
    1,534
    Character
    Adol Giantbane
    World
    Ultros
    Main Class
    Dark Knight Lv 60
    Quote Originally Posted by LineageRazor View Post
    The solution to this problem is not to to add an "In Progress Only" button. The solution is to make in-progress runs the priority when the "Join In Progress" checkbox is selected. The way it SHOULD work:

    1. Player selects "Join In Progress" checkbox and signs up.
    2. System checks for in-progress runs that require the player's current class. If it finds some, the player is added to the in-progress run that has waited for a member the longest.
    3. If there are no in-progress runs that require the player's current class, it checks for new runs that require the player's current class. If it finds some, the player is added to the new run that has waited for a member the longest.
    4. If there are no eligable runs, the player is added to the wait queue.

    It is frankly astonishing to me that SE did not code it this way; for in-progress runs, the dungeon clock is ticking and empty slots should be filled as a top priority, well beyond new runs. Nevertheless, this does not warrant the addition of an "In Progress Only" button, it warrants a correction on how duty finder matching works.
    I'm pretty sure it works like this, actually. Often when I get in progress runs, the queue pop is *instant*, there is literally no down time, I just hit queue and it pops. Even when I'm queuing as a tank, the matchmaker never pops that fast for a fresh run. If you're getting in a situation where you're trying to join a friend's group, it may be that the matchmaker has already offered that in progress run to another person in the queue, and won't offer it again until that person drops the queue. During that time, it will still pop fresh instances for those in the front of the line.

    In progress only is a more elegant solution than this 3 withdraws in a day penalty because it gets all of the major offenders (in progress queue fishers) and puts them in their own matchmaking pool away from everyone else. And it doesn't really reward them as they will be stuck queuing against each other for probably longer than it would have taken for them to just join a fresh run.

    Although, even with an in progress only option, I still think there should be a withdrawl penalty, but I think it should be a much shorter time span (1-3hrs) and for a shorter duration (10-15min).
    (0)
    Last edited by Giantbane; 10-29-2014 at 07:35 AM.

Tags for this Thread