Be Wiser! DF commence withdraw penalty affects your party.

[BobbinT]

(For ppl who feels TLDR, just skip the to red-bolded parts)

Not long after patch went life, I got myself 2 penalties so far.

First one, LS mate suddenly invited and then asking me and one other tank to help him clear his Qarn HM. Short story, after we've done, the guy quickly register for Satasha HM and we both didn't even know he wanna do that next. And having a tank in our party makes it pops quite instantly.

Unfortunately, the tank want to take a break and pressed Withdraw button. What I didn't realize after is that I do planned to do this Snowcloak dungeon that I just unlocked before that LS mate inviting me. And without me realizing, I got withdraw penalty for 30 minutes. And since I don't feel I made any mistake, I'm immediately upset for getting unfair punishment. So I threw several tickets to GM to pent my frustation. And after I cooled off, I resume my gaming.

The second case, was on my fault entirely and has been discussed alot on other threads. While waiting for DF for roulette extreme, I continue doing main story and commence window popped while I'm in CS. Tried to spam conversation very quickly and I still couldn't make it since it was really that long. Strike 2.

Now, I won't mention anything interest from 2nd case since it's quite clear. But on that 1st case, at least there's 2 point I learn:
- As a party leader, you have to be responsible and take concern from all your party member. Can't just carelessly registering DF while not everyone agrees. Once commence pops, you're either in or make the whole party locked out.
- As party member, any of you can withdraw that DF, but it will cost the entire party getting penalties. Either you have no choice but to jump to the wagon, or you bailing out and make all of you suffer time wasted.

There's this also 3rd case that can led to another troll problematic, which happens to me time to time. Fortunately this hasn't happened post 2.4 yet. Well... sort of.

When 2.3 introduced hunts, whenever there's a hunt NM pops, lots of ppl gonna come to the zone and shouted for invites.

Now there's a time when I was in Central Shroud minding my own business when suddenly a shout of rank A NM being found and invites shouts start to scroll my chat log. I then immediately shouted mine and not long after, someone invited me.

But when this party reaches 4 member, a DF suddenly registered and Tamtara commence window popped. Being confused, I immediately withdraw and leave this party and resume shouting for invite. Alas, the same guy reinviting me again over and over. And the trouble is: I have to manually cancel his invite if someone else could invite me. In the end, I only got the lowest reward of that hunt.

(Now, you should have realize that if this happens in 2.4 and I pressed that withdraw, I just got myself another trouble without me realizing it quickly.)

I then proceed to vent my annoyance to this unknown guy, and he responded about how he was quite new player and unable to do that old content because he can't find any ppl willing to help him entering it and DFing for hours without able to get in. And sure did, when I checked his status, he was only level 15 on his 1st class.

Although I do understand his frustration, he was doing this on a bad timing and frankly, his way of ninja-inviting me were kinda rude. Now, with new penalty we had, this could become very problematic. And like I said, Ii do had this similar things time to time. Even my 1st case I told above are also ninja-inviting, but being LS mate, I didn't really thought that much. This made me realize:
You can't just ninja-invite someone without asking their permission 1st. If that someone suffer a penalty because of you, expect perma-/blist coming your way.

Unfortunately, as unfair as it seems, you have no choice for time being to follow SE play rule for now. So, in general advice: Be wise! Be responsible on what you did and understand the consequences.

On last note, this only happen on non full pre-made party. I don't know if this could affect a full pre-made parties since this would really sucks if the same rule applies. lol

**********

Added comment about full pre-made parties. Short answer: it's safe. ^^

I guess this only happen if the party is not full, since I didn't get any penalty when in a Ramuh Extreme party and someone was afk.

[Amenian]

This is a perfect example of how good intentions often lead to unintended consequences.

[NyarukoW]

Click commence and take the 30 minute penalty for leaving. It is a temporary workaround.

Bottom line, people need to communicate. Ask if people are ready queue. Do a ready check at very least before you queue.

[Fyce]

1st case: Well, thank you for the info. I guess it's that way to prevent an uncomplete party to still fish for "in-progress" tags... Still, it's a bit harsh.

2nd case: You said it, it was your fault, and that's right. Nothing to add.

3rd case: I'm pretty sure that you can immediatly report the party leader to the GMs. They probably don't have the power to remove a strike from your account for the day, but at least, if enough trolls are getting reported and get a tell from a GM, the practice will stop.
For the exceptional case of a new player trying to do a specific dungeon, I'm pretty sure the GMs can take action accordingly.

[Fornix]

The entire system is just messed up. Hopefully they'll just come back on this choice and remove it soon. Simply add a join in party only filter instead to stop the need for people fishing in progress queues instead.

[BobbinT]

3rd case: I'm pretty sure that you can immediatly report the party leader to the GMs. They probably don't have the power to remove a strike from your account for the day, but at elast, if enough trolls are getting reported and get a tell from a GM, the practice will stop.
For the exceptional case of a new player trying to do a specific dungeon, I'm pretty sure the GMs can take action accordingly.

I actually kinda pity the guy at the time, although I admit was being a bit upset. Think that one was not a serious case to be reported. It does happened in 2.3.

[Fyce]

I actually kinda pity the guy at the time, although I admit was being a bit upset. Think that one was not a serious case to be reported. It does happened in 2.3.

Indeed, use your personnal judgment on the situation before taking action.
But if now, in 2.4, someone would troll like that, I belive that reporting him/her is the best solution.

[Shougun]

Allow players to accept duty within a CS, add an accept/deny for joining a queue (would you like to join John Bobbit for the battle against Mordor? If you answer no it will prevent the queue from starting for the party and inform the leader who said no), remove the penalty for complete non-pvp pre-mades, leave it for alone otherwise.. imo.

[Grey_Cain]

Ergh. I wouldn't have expected it to be party-wide just because one person decides to be a troll. Now I'm gonna be even more paranoid around groups. This sounds like something that shouldn't have needed a fix by simply not making the penalty party-wide.

[Hulan]

My assumption - and I'm sure it's a good one that most people would agree with - is that this mechanism was designed to deter in-progress hunting. Since you cannot join in-progress with a party, I see no reason why they couldn't keep the system as is to serve its purpose while removing it from pre-made party queues. This leaves only the vanishingly small number of people withdrawing as a party to troll individuals, but I suspect the number of occurrences of such an activity is negligible.