Book of Heroes

Feature Request - ban mercs from joining guild raids

juggernaut_money_shot wrote:
Blacklist deadbeat mercs

Postby Juggernaut_Money_Shot » Mon Mar 30, 2015 4:32 am
When will you allow us to ban mercs from joining our raids, or allow us to boot deadbeat mercs who don't hit? Everyone knows how much (NAME OF A DEADBEAT MERC WHICH HAS BEEN REMOVED TO AVOID CHAT RULE BREACH AND TOPIC LOCK) sucks as a merc. He is famous in the game for pissing off every guild he mercs at. Lately, a new player, (NAME OF ANOTHER DEADBEAT MERC WHICH HAS BEEN REMOVED TO AVOID CHAT RULE BREACH AND TOPIC LOCK) from (NAME OF A DEADBEAT MERC'S GUILD WHICH HAS BEEN REMOVED TO AVOID CHAT RULE BREACH AND TOPIC LOCK) has been doing something similar. He joins a raid with 3 alts and then sits at the bottom of the raid until maybe he finds time to hit. He regularly stays at 100rpp during a large chunk of the raid, and often ends raids still at 100rpp. He has never responded when we try to talk to him in chat so probably doesn't even understand English. Hard to tell him we don't like his selfishness when he can't understand us.

Putting a password on a raid, or on a guild is something no one likes. Fizz has lost lots of members because they kept a password on their guild and people don't have time to wait to be accepted when they want to do a quick dump and run. If we password protect raids, no one will join either cause they have no clue who to whisper for the password.

We need a way to manage our guild and raids without impeding the majority of players who play with common decency. You already have a methodology for ignoring players. We want a way for our guild to blacklist players so they can not join our guild or merc our raids. And we would also love a way to boot mercs who don't hit after joining a raid so we can accept a new merc in that space. I don't care if we lose benefit of their kills and we must kill a few more waves after booting them. The will only be booted for not killing to begin with, so this won't be a problem for us. If you want to protect players from unfairly being booted, make a setting so they can't be booted from the raid after they get 10 kills or something like that. At the same time, if they are being rude or abusive in chat, we need a way to boot them from our chat as well, even if they get to keep their rpp and raid rewards.

Bottom line is we need a way to manage our guild and ever since you took away our banhammer, we have been left defenseless against people who don't deserve to be in our guild.

Please let us know how you plan to address this issue that has been a problem for a long time, and has support from many players and guilds in the game.

Thank you.


Now that we have addressed the issue that resulted in the original topic being locked, that of individual deadbeats and their home guilds being named, we can continue.

Now I thought Wyt phrased things very well, tbh. But the response in the original thread of "no, not allowed, list NICE mercs instead.." struck me as wonderfully naive.
The reason being, 99.9% of the mercs out there are of a good quality. Sure, every now and again, one will score low due to circumstances happening, but those are rare occasions for each, and they do not a skunk merc make.
The problem is that 0.1% of mercs who deliberately and repeatedly target other guilds' raids, take up one or more limited places, and deliberately do precisely nothing.
We cannot realistically list all the thousands of good mercs and expect people to refer to that list on every occasion they are asked for a password by someone they do not personally know, keeping the raid otherwise locked, in order to stop this handful of deliberate saboteurs.
  • Any merc not already on the list will struggle to "prove themselves" and get on it. Say someone has struggled to get to PM might, but doesn't have "connections" in any of the guilds that regularly run it. How do they get in when everyone's passworded and won't take a chance on a n00b because they have plenty of regulars?
  • Raids and guilds will be locked by default, reducing mobility and the social aspect of raiding
  • Mercs will have fewer opportunities to join raids, leading to slowed progression and increased antagonism towards the guilds that are staying closed - something that top guilds regularly face already.
  • Passwords, where used, will become quickly known and shared, and therefore redundant, requiring administrative monitoring and updating by each host guild - not something most players are here for.
  • More guilds at high level with 100+ members will suffer attrition as they cannot allow free entry, but require approval on each occasion - as mentioned happening with Fizz in the OP (can I say the guild name here?}
  • Mercs will become less active as it becomes more hassle to be a merc and get into raids
Is it REALLY worth putting so many players through so much hassle to protect a very small number of players who want to deliberately troll and annoy others?

Regards the original thread lock - this seems not to make much sense. On the original thread, Chem edited a subsequent comment post by another user to remove profanity, but left the deadbeat names in the OP, which was the reason given for locking.
As mods and devs have the ability to edit posts in this fashion, why not simply remove the names from the OP and allow the topic to remain unlocked?

This is an issue that constantly resurfaces. Every time it does, everyone agrees that something needs to be done (though a few disagree with the popular blacklist / boot idea). It's constantly in Global and in guild chats as a subject.
Locking a thread is not going to make this go away, it's been an issue ever since limited merc space was introduced, with a small number of individuals behaving poorly - and the vast majority suffering for it whilst the perpetrators have free reign to continue as they are.



Now I'm gonna go find a thread about the weekly quests and double valour so I can say something nice.

Doctor_Love_Money_Shot

Thu Apr 2, 2015 12:57 am
Why did bj have to ruin this post by changing the title so no one knows what it is really about? Put it back heavy handed bj.
Juggernaut_Money_Shot wrote:Why did bj have to ruin this post by changing the title so no one knows what it is really about? Put it back heavy handed bj.


Especially seeing as the new title refers removing mercs from raids, whereas the topic is about preventing them joining in the first place.

If there was a need to change the title - and I don't particularly see that there was - then changing it to something describing a subject other than that which it contains is misleading to say the least.
It also makes finding threads you want to view problematic when they're changed without notice.

CheMClarc

Site AdminThu Apr 2, 2015 11:09 am
DreamingDæmon wrote:

The reason being, 99.9% of the mercs out there are of a good quality. Sure, every now and again, one will score low due to circumstances happening, but those are rare occasions for each, and they do not a skunk merc make.

The problem is that 0.1% of mercs who deliberately and repeatedly target other guilds' raids, take up one or more limited places, and deliberately do precisely nothing.
This is the main reason why you have not seen a feature implemented to remove or prevent players from joining your raid. Password protecting your raids prevents most of the issues you are concerned with. It might not be something that some players are a fan of but it is effective if used. If you do not want to use the feature than you may get players that do not perform to your standards in your raid.

That being said, there is always room for improvement on how to prevent this type of behavior and give Guilds more control in future updates. For the time being, please put your raid schedule in your guild description for players to view and be aware of, post ads during the raids to attract players and password protect them to avoid troublemakers.
CheMClarc wrote:
DreamingDæmon wrote:

The reason being, 99.9% of the mercs out there are of a good quality. Sure, every now and again, one will score low due to circumstances happening, but those are rare occasions for each, and they do not a skunk merc make.

The problem is that 0.1% of mercs who deliberately and repeatedly target other guilds' raids, take up one or more limited places, and deliberately do precisely nothing.
This is the main reason why you have not seen a feature implemented to remove or prevent players from joining your raid. Password protecting your raids prevents most of the issues you are concerned with. It might not be something that some players are a fan of but it is effective if used. If you do not want to use the feature than you may get players that do not perform to your standards in your raid.

That being said, there is always room for improvement on how to prevent this type of behavior and give Guilds more control in future updates. For the time being, please put your raid schedule in your guild description for players to view and be aware of, post ads during the raids to attract players and password protect them to avoid troublemakers.

So basically, you're going to continue to do nothing about the very few, I can count on one or 2 hands, mercs who constantly and regularly do this. Wouldn't it be easier for te Devs to actually, I don't know, maybe listen to who the worst offenders are and actually do something about it? You permasilence people for constantly abiding chat rules, how is constantly abusing guilds( that aren't theirs) not exactly the same thing? It would be nice if you permabanned them from mercing and maybe lifting that ban at a later date to see if they have changed?

Or does that make too much sense...
CheMClarc wrote:
DreamingDæmon wrote:

The reason being, 99.9% of the mercs out there are of a good quality. Sure, every now and again, one will score low due to circumstances happening, but those are rare occasions for each, and they do not a skunk merc make.

The problem is that 0.1% of mercs who deliberately and repeatedly target other guilds' raids, take up one or more limited places, and deliberately do precisely nothing.
This is the main reason why you have not seen a feature implemented to remove or prevent players from joining your raid. Password protecting your raids prevents most of the issues you are concerned with. It might not be something that some players are a fan of but it is effective if used. If you do not want to use the feature than you may get players that do not perform to your standards in your raid.

That being said, there is always room for improvement on how to prevent this type of behavior and give Guilds more control in future updates. For the time being, please put your raid schedule in your guild description for players to view and be aware of, post ads during the raids to attract players and password protect them to avoid troublemakers.


The password system is great for some things - letting guild alts into a raid ahead of a full open, for example. Or for letting in a select few guild friends on a whitelist basis.

But for this scenario, your "solution" punishes the hosting guilds and the thousands of good mercs. Not the handful of trolls who deliberately go out of their way to sabotage other guilds' raids.
It's slow, clumsy, inefficient, restrictive and hurts everyone who abides by the standards of good behaviour. And does nothing to discourage the problem at its root, which means it doesn't go away. And players continue to get frustrated.


That's why most are generally "not a fan" of the password system for the skunk merc scenario.

Famous_Fella_O_Nutella

Thu Apr 2, 2015 6:45 pm
Maybe if we could make like lists? Like friends lists? You raid with people and those that do good you can add to a friends list or call it trusted mercs and maybe when you run raids you can choose to only accept people on your lists?

Illy_the_Red

ModeratorFri Apr 3, 2015 5:31 am
It may just be that Venan doesn't consider it worth the time/money investment to prevent an issue that only occurs with an extremely low number of mercs. I've heard arguments against other features for that reason.

However CheM, surely you must be taking note of how unpopular this behaviour is? Why ignore it? It took an age to finally implement a midweek event after many many requests for it, and I bet the number of people that literally can't hit a weekend event is fairly low. But you did the right thing and implemented something anyway.

Guilds should also perhaps start taking more responsibility for the deadbeats that are giving them a bad name. The most prolific deadbeat (name not given) from (name not given, but everyone knows which it is) is harming them overall. Maybe we should start taking note of certain guilds that have deadbeats and consider them more carefully when we give out passwords. At the moment just throwing slots open is a risk.
Ilyana wrote:
Guilds should also perhaps start taking more responsibility for the deadbeats that are giving them a bad name. The most prolific deadbeat (name not given) from (name not given, but everyone knows which it is) is harming them overall.

Guilds taking responsibility for member actions may soon have to happen anyway. I've talked a couple of people out of deliberately skunking raids of a guild which has a high-profile skunk merc, because I don't think it's fair to hurt a guild because one of its members behaves badly. But I think it's likely to start happening soon where (guild name not given) opens PM and gets 10 mercs who sit on 100 RPP because one of their members (name not given) regularly and deliberately does that to others. That's assuming it doesn't happen already? I don't (won't!) merc with that guild so I don't know what merc participation in their raids is like currently.