Vote to boot from group

[PsychoBlonde]

Unfortunately this is a very old topic. The problem is the extra griefing that this will cause is just not worth the positives of it. Imagine running in a party and every 15 seconds there is a vote for random people in the group without reason. This happens in Battlefield all the time.

Well, one could design it intelligently so that you can turn off that alert if you don't like it, so the party leader would get nothing but automatic "your vote rejected" messages.

Does Battlefield have a "party leader" position?

They could also simply have an activity time-out for quests--if you go 10 minutes without any in-game activity, you auto-recall.

[Sehenry03]

Also one other thing on abuse.

Yes I know abuse can happen in every situation. Someone was talking about Battlefield amongst other things.

We are talking completely different things here.

We are a small community here. Most people have grouped with most other people. I know a few people I personally will never group with again knowingly. Someone abuses this it WILL get around really quick. I am on Sarlona which is one of the bigger servers and I group with lots of the same people all the time. If someone wants to boot me from the group because I am being rude well knock yourself out. Considering how often my groups fill and how fast they fill though you are never gonna get in my group again lol

The point is yes I know it can be abused. So can lots of things. I personally...and this is my personal opinion...think that with a majority needed to boot someone...I don't see it being abused often. I was here when you used to be able to boot and I NEVER saw any issues with it except with total idiots and I know which people to stay away from so I don't care about those. Even new players will quickly learn. I think a majority brings the chance for abuse down to a minimum...and the ability to boot someone for griefing or AFK/Piking is WAY to big of a thing to ignore.

Pikers don't happen often now because I don't let them in my group anymore which is a fix in itself. But occasionaly they make new toons and I don't know them yet so I have to relearn them. This would just make life better I think.

[Oxarhamar]

Well, one could design it intelligently so that you can turn off that alert if you don't like it, so the party leader would get nothing but automatic "your vote rejected" messages.

Does Battlefield have a "party leader" position?

They could also simply have an activity time-out for quests--if you go 10 minutes without any in-game activity, you auto-recall.

/Not signed

To 10 minute inactive auto recall.


We already have AFK auto log off which is avoided by auto running against a wall, I see no difference in the mechanic being avoided with auto running.

Players go legit AFK in (not just poking) the time no reason even when soloing no reason to grief them over pikers.

[Lerincho]

Well, one could design it intelligently so that you can turn off that alert if you don't like it, so the party leader would get nothing but automatic "your vote rejected" messages.

Does Battlefield have a "party leader" position?

They could also simply have an activity time-out for quests--if you go 10 minutes without any in-game activity, you auto-recall.

yes it's called commander and squad leader, so you actually have 3 ways to initiate a vote. server, team and squad.

[Starla70]

This is something I just think is going to cause way more harm then good. I get the idea on the afk issue. However, in a pug, if you have those who feel they know how you need to run your toon, it is going to cause issues. We already have the party leader able to kick that should be enough.

[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]

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

[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]

Why? How can you abuse it?

We had kick from group in the past and it was abused and that's why its gone as it should be. I had it done to me as a joke a few times and saw it done many more. If even one person gets kicked from a group wrongly it would be to many.

[Requiro]

We had kick from group in the past and it was abused and that's why its gone as it should be. I had it done to me as a joke a few times and saw it done many more. If even one person gets kicked from a group wrongly it would be to many.

Do you even read that ideas?

I singed for AFK vote and ONLY AFK will get kicked if EVERYONE will vote yes.

I do not propose "kick at will".

So again - How this can be abuse?

[Uska]

Do you even read that ideas?

I singed for AFK vote and ONLY AFK will get kicked if EVERYONE will vote yes.

I do not propose "kick at will".

So again - How this can be abuse?

Sometimes things come up babies need something or something else the marked as AFK comes up to quick. They just need to remove the gather the whole party thing and then you can finish the current quest and then you can remove the person before the next quest. There is zero chance of me ever agreeing to any remove party member under any circumstance no matter how anyone spins it.

[Requiro]

(...) There is zero chance of me ever agreeing to any remove party member under any circumstance no matter how anyone spins it.

Thanks for clarification.

Anyone else have any suggestion how option to solve intentional AFKs (from my post above):

/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.

can be abuse?

[Uska]

Thanks for clarification.

Anyone else have any suggestion how option to solve intentional AFKs (from my post above):



can be abuse?

Yes read my explanation the afk thing comes up to quick and players have to take care of things if they just remove gather party thing most of the problems would be gone

[Grandern_Marn]

No, don't really need it on all three counts. Been playing for 4 years and predominantly playing pugs, been fine working around any rare instances that come up.

[Wanesa]

Yes read my explanation the afk thing comes up to quick and players have to take care of thing
s if they just remove gather party thing most of the problems would be gone

Rainbow in the dark - A player grabbed the key, then he went AFK for half of hour

[Qhualor]

Rainbow in the dark - A player grabbed the key, then he went AFK for half of hour

that's why some quests have keys and such respawn after a little time. in case someone dies, drops the key and forgets to pick it back up. instead of the group running around looking for it, go back to get the key from its original place. someone goes afk, just go back and get the key. yes, its annoying to do that but its better than recall/reform or standing around for half an hour waiting.

[Requiro]

Yes read my explanation (...)

I read. I know WHY players go AFK. But I ask about abuse.