Vote to boot from group

[Sehenry03]

This has probably been brought up but here is my opinion on why we REALLY need this:

1) You are running any quest where at some point the whole group has to be present to advance. You happen to get that person who says "Gotta go afk for awhile" and now you get to that point and he doesn't come back. You have 2 options currently...start over or wait and hope he returns. Going AFK is fine as long as you tell us how long and you don't hold the group up =(

2) You have "that guy". Someone just being a total ass in the group and ****ing everyone off. If a majority of the group wants him gone we should be able to boot even in a quest.

3) Raids. Why is it in pug raids there seems to be that one person who won't listen and does his own thing often times causing lots of unneeded issues. Let us boot them plz. I am sick of people in FoT running to the reaver and then spreading the "boom" to everyone else. Listen to directions or let us kick them.

Now I know the biggest drawback to this would be abuse by those who are just jerks or elitists...I don't care if people boot me for stupid reasons I know not to join them anymore and its not a big deal. Being able to get rid of the trouble maker would be a very good option.

[Uska]

No we don't and its been brought up and most are still against it

[songswrath]

The only way i would say yes to this. Is in the case of quests like diplomatic where you can't break the wall till the full group is there. I don't know how many times some pug went afk for over 10 mins <without saying something aka unwanted pikeing> and quest than is needed to be reset. So no i can see too many ppl getting booted cause they "ding". Turning many new players away from game.

[Enoach]

I realize there are quests that require people to gather to move on but...

In the early days the PL had the ability to boot players while in a quest and while it was useful in removing troublemakers from the group it also was abused heavily. It is that abuse that honestly would be the reason I would never support bringing back that feature even with a voting mechanic.

Sorry, Turbine learned while used by mature people this is a good idea, but in the wrong hands it is a nightmare.

[PsychoBlonde]

Yeah, I think this would be a bad idea in general.

A better one would be to give the PL (and the PL only) the ability to right-click on a party member name and "summon" that person. Make it a nice long cooldown so it's really only useful for getting past gather issues when someone has gone afk.

Or just stop putting that annoying mechanic in new quests.

[Uska]

Yeah, I think this would be a bad idea in general.

A better one would be to give the PL (and the PL only) the ability to right-click on a party member name and "summon" that person. Make it a nice long cooldown so it's really only useful for getting past gather issues when someone has gone afk.

Or just stop putting that annoying mechanic in new quests.

Don't really like that as it helps multiboxers

[Calinthus]

Yeah, I think this would be a bad idea in general.

A better one would be to give the PL (and the PL only) the ability to right-click on a party member name and "summon" that person. Make it a nice long cooldown so it's really only useful for getting past gather issues when someone has gone afk.

I second this. Although, I run with alot of people that like to joke around (me included). The down point would be you are just about to finish an objective, and the PL summons you. Then you have to run all the way back, and complete that objective. So, I would have to say, "YES, please."

[Phoenix-daBard]

This has probably been brought up

It has been brought up weekly.

A simple solution: Report the offender if they are AFK piking the quest preventing you from completing then the a GM can remove them.

[Wh070aa]

It has been brought up weekly.

A simple solution: Report the offender if they are AFK piking the quest preventing you from completing then the a GM can remove them.

You realize, that it takes about 2 hours to get GM?

Anyway, cant they remove the "whole party" mechanic? It's annoying and makes the game less enjoyable. Also it kills grouping for many quests.

[Sehenry03]

You realize, that it takes about 2 hours to get GM?

Anyway, cant they remove the "whole party" mechanic? It's annoying and makes the game less enjoyable. Also it kills grouping for many quests.

This.

I hate setting up my LFM for diplo Impunity...jumping in quest...someone clicking to join so I accept. I fight to the scout and I ask the other player to wait 2 min. I get to the scout just in time to see him jump in group. I ask if he can get to me alone and I see his dot moving on the same path I took so I guess he can only to see him die 2 min later.

These types of moments make me hate offering up LFM's but at least they are rare. To bad they happen so often in THAT quest.

[PsychoBlonde]

You realize, that it takes about 2 hours to get GM?

Anyway, cant they remove the "whole party" mechanic? It's annoying and makes the game less enjoyable. Also it kills grouping for many quests.

The GM's don't do this any more, anyway, so waiting for one is futile. You just get a polite message telling you "sorry, we can't mediate party disputes."

[Phoenix-daBard]

You realize, that it takes about 2 hours to get GM?

My average is 20 minutes for a response. Must be my playtime.

[kwyjibo_lol]

1) You are running any quest where at some point the whole group has to be present to advance. You happen to get that person who says "Gotta go afk for awhile" and now you get to that point and he doesn't come back. You have 2 options currently...start over or wait and hope he returns. Going AFK is fine as long as you tell us how long and you don't hold the group up =(

For certain quests with require everyone to assemble in the final room (e.g. Partycrashers) I think that is a reasonable thing to have as computationally it would be easy to work out if someone was not moving or responding to tells whilst the rest of the party are in the final room. Now whilst I think it would be a nice to have and there would be no real way to abuse it per se, I don't think it is quite worth the dev's time.

[Qhualor]

This has probably been brought up but here is my opinion on why we REALLY need this:

1) You are running any quest where at some point the whole group has to be present to advance. You happen to get that person who says "Gotta go afk for awhile" and now you get to that point and he doesn't come back. You have 2 options currently...start over or wait and hope he returns. Going AFK is fine as long as you tell us how long and you don't hold the group up =(

2) You have "that guy". Someone just being a total ass in the group and ****ing everyone off. If a majority of the group wants him gone we should be able to boot even in a quest.

3) Raids. Why is it in pug raids there seems to be that one person who won't listen and does his own thing often times causing lots of unneeded issues. Let us boot them plz. I am sick of people in FoT running to the reaver and then spreading the "boom" to everyone else. Listen to directions or let us kick them.

Now I know the biggest drawback to this would be abuse by those who are just jerks or elitists...I don't care if people boot me for stupid reasons I know not to join them anymore and its not a big deal. Being able to get rid of the trouble maker would be a very good option.

I was hoping this thread would just die out but it keeps coming up.

1. don't design quests where every party member needs to be present to continue the quest. i can see why they were designed this way, but its the wrong way to go about it.

2. /squelch and you don't have to hear him or see his party chat. ignore him while in the quest unless its so bad that you cant handle it anymore and either report him for harassment or recall and reform. a report will make the GM have to research the problem and if he thinks it is bad enough, the griefer can be banned. ive seen a lot of grey lines on the supposed griefer before that majority vote or party leader vote can be abused too easily. the "talk that gets around town" can unfairly cause unnecessary problems for innocent players.

3. every raid leader should be making sure that every person in the group understands their role. i see too many people that assume or don't ask or don't speak up to say they don't know what to do or given a role that they have little to no experience with or something and it all boils down to the player and the raid leader. either the raid leader that pugs needs to be willing to have patience and able to explain what needs to be done or he needs to use the lfm notes and say "know it". this is part of the reason why i and some other players wont join new raids without guildies or lfms that say "all welcome" until we actually do know it. nobody likes to look like a fool or be the one that wiped a raid over something silly. even then, not every raid leader does things exactly the same way every time either.

when i encounter a player that i cant deal with beyond the quest i am running with them, i just simply drop after the quest and remember their name to avoid in the future. i don't think we need to get to the point of actually booting players in quest that can totally **** someone off enough to not log back on again or adding one more reason to not pug. kicking players in quest is just too easily abused.

[Wanesa]

I have an idea. Let the feature "boot" is there, but let it work as remote "recall" with a loong timer. The victin can interrupt it by moving or by doing other actions, like standard recall, so it cannot be abused to boot actively playing players (even currently dead). This boots player from the quest, but not from the party. If the victim is teleported to the public area, the party leader can then boot him from the group. If the victim is teleported to the wilderness area, he cannot be booted from the group and he can still renter the quest and cause -10% XP penatly for everyone in the quest. This should be enough to reduce motivation to abuse this feature.

Dead players have also the timer and then they are ressurected before quest entrance

[Requiro]

/signed for AFKs


Party ability: Vote for kick anyone in party if it's marked as AFK. Require "YES" vote from ALL other players in party. Cooldown: 120 sec.


And additional even better idea: Box Option when you create party, that ANYONE that is marked as AFK will be automatically kicked.

[Uska]

/signed for AFKs


Party ability: Vote for kick anyone in party if it's marked as AFK. Require "YES" vote from ALL other players in party. Cooldown: 120 sec.


And additional even better idea: Box Option when you create party, that ANYONE that is marked as AFK will be automatically kicked.

Umm no

[Requiro]

Umm no

Why? How can you abuse it?

[Uska]

I was hoping this thread would just die out but it keeps coming up.

1. don't design quests where every party member needs to be present to continue the quest. i can see why they were designed this way, but its the wrong way to go about it.

2. /squelch and you don't have to hear him or see his party chat. ignore him while in the quest unless its so bad that you cant handle it anymore and either report him for harassment or recall and reform. a report will make the GM have to research the problem and if he thinks it is bad enough, the griefer can be banned. ive seen a lot of grey lines on the supposed griefer before that majority vote or party leader vote can be abused too easily. the "talk that gets around town" can unfairly cause unnecessary problems for innocent players.

3. every raid leader should be making sure that every person in the group understands their role. i see too many people that assume or don't ask or don't speak up to say they don't know what to do or given a role that they have little to no experience with or something and it all boils down to the player and the raid leader. either the raid leader that pugs needs to be willing to have patience and able to explain what needs to be done or he needs to use the lfm notes and say "know it". this is part of the reason why i and some other players wont join new raids without guildies or lfms that say "all welcome" until we actually do know it. nobody likes to look like a fool or be the one that wiped a raid over something silly. even then, not every raid leader does things exactly the same way every time either.

when i encounter a player that i cant deal with beyond the quest i am running with them, i just simply drop after the quest and remember their name to avoid in the future. i don't think we need to get to the point of actually booting players in quest that can totally **** someone off enough to not log back on again or adding one more reason to not pug. kicking players in quest is just too easily abused.

This