A party member has withdrawn...

[NeruMew]

Put that person into the equation and they're taking up a spot from somebody who would start arguement works both ways. Justify away.... Oh look it's a healer trying to jusitfy it one of the most frequent guilty parties...

BURN THE HEALERS!!!!

/petition to remove the role of the game, and while they are at it tanks too... DDs for the win! (juggly and bouncy!)


On a more serious note, it may or may not, more likely it does, because that person is taking up the space of someone who does wanna join, im pretty sure more than one alliance gets stuck at this at the same time, at the least, and if this was the case at the very least one of them could be already inside.

Anyway. Pics or it didn't happen! (prove your point, winkwinkwankwank!)

[flamds1]

BURN THE HEALERS!!!!

/petition to remove the role of the game, and while they are at it tanks too... DDs for the win! (juggly and bouncy!)


On a more serious note, it may or may not, more likely it does, because that person is taking up the space of someone who doesnt wanna join, im pretty sure more than one alliance gets stuck at this at the same time, at the least, and if this was the case at the very least one of them could be already inside.

Anyway. Pics or it didn't happen! (prove your point, winkwinkwankwank!)

Nonsensical rebuttal just as I expected and you just completely invalidated you arguement previously.


only way to solve the problem is to remove the option to simultaneously queue for inprogress and new start instances. It would eliminate the df spamming entirely for new parties and people who want spam in progress can do so to their hearts content without interrupting groups trying to start since people spamming for inprogress have no intention of joining a new start.

[necrosis]

only way to solve the problem is to remove the option to simultaneously queue for inprogress and new start instances

And then no one would queue to make new runs so there are runs to join 'in progress' if a slot opens. Its a huge catch 22.

[flamds1]

And then no one would queue to make new runs so there are runs to join 'in progress' if a slot opens. Its a huge catch 22.

Really? so everyone who shows up in a new party is queueing for in progress?

[necrosis]

Really? so everyone who shows up in a new party is queuing for in progress?

And if you could just join 'in progress' matches and not be classified as an ass would you do it? I am sure most would. Most don't want to waste time killing mobs they don't get stuff from. But they don't constantly withdraw because they have enough decency in them not to do it. Remove the 'I will look like a dick if i do it' and more people will do it.

Look what SE had to do to get people to 'help' with level ~15 dungeons because no one wanted to do them anymore because they were all 50. Give people the option to not do something and take an easier path and they will.

Besides the last thing this game needs is more ways to segregate people.

[NeruMew]

Nonsensical rebuttal just as I expected and you just completely invalidated you arguement previously.


only way to solve the problem is to remove the option to simultaneously queue for inprogress and new start instances. It would eliminate the df spamming entirely for new parties and people who want spam in progress can do so to their hearts content without interrupting groups trying to start since people spamming for inprogress have no intention of joining a new start.

That would work too, that way, people who wanna join a duty already started would have to eat hours ques because a whole bunch of ppl are gonna try to also leech that easy win, while people who doesn't care will get their group formed, though, it will take longer since the choice to join already started might be more obvious to some others that couldnt bother to be annoying and spam the queue button in search for a group already in progress.


However, what arguement is that which I completely invalidated?

edit: *I see I made a typo so I'll correct that as well on the previous post (I hope that was not it, since obviously it's a typoe because otherwise it would make no sense, and you would be a complete moron for falling for it)*