Griefing, the Hellhole of AoS - How to Stop?

[camper125]

i wish that will happen

[MrHank]

Ive been placing blocks over griefers when I can so they get stuck. Do that once or twice and theyre sure to quit

[ReubenMcHawk]

I've seen several ways to stop griefing, and several votekick improvements, and mostly all of the former are exploitable in one way or another, several of the latter as well.

- Spectator mode for officers - to enter anytime. This way they could see better if someone is griefing, when someone starts to whine about a griefer. This could bring some issues with stealth elements being exposed, but the officers should not use it for their own advantage - they'd be the most trustworthy people of the community.

Already exists, called /invisible.

- Collapse log. When the griefing has already happened, it is hard to tell who did it. Simply pressing some button like home or page up would bring up a text field, which lists all the collapses happened in the server, the creator of them, and the amount of blocks destroyed. If the amount of blocks destroyed is large and just happened, you probably found the criminal.

Not that bad of an idea. Might be a bit cluttered, but it'd actually be pretty useful, considering most people just shout "HACK" or "GRIEF" without using a name.

- Freeze - to prevent griefing without exposing self to enemies. Freezing happens when you press a certain key and point at the griefer, so yeah, he gets frozen. The officer who froze him should also become intact, so he can talk to the griefer and ask what he's doing. The griefer - or a player, if the officer has mistaken - could explain himself during this time. If no proper explanation is given or if it is not valid, a ban should follow. To identify better who's frozen a red circle should appear around the one. Also there should be a button to unfreeze the player - because misunderstandings can happen.

I've actually been thinking about this lately, something like a /togglemove would be pretty cool.

And as for this "officers" idea, I'm 100% against it. The idea of me starting a server and someone else instantly getting admin powers on it just doesn't sit right with me. And to be frank, I don't trust a single person in this community with that kind of power to not abuse it in some form or another. The gbl system as we have it has already been exploited once before, and I'd rather it not happen again on a larger scale.

[SLoW]

Shameless plug coming:

The admin script I created (@Badmin) deals with griefing by attempting to empower users to votekick.

1. If a user attempts a blank votekick (one without a reason specified), it's declined and the user is told to provide a reason.
2. If the user lists "griefing" (of several bastardized variations of it), the kickee is automatically checked for griefing.
3. If the kickee's grief score is above a certain (customizable) threshold, the kickee is automatically warned, kicked, or banned (depeding on the severity of the griefing).
4. On the inverse, if the user HASN'T been griefing, the votekick is automatically cancelled and the kicker is given a reason why.

@Badmin is only in its infancy, but I think the idea behind it is solid. I think if you can get users to consistently votekick griefers and you have a system in place to punish griefers without admin intervention, you can make griefing significantly less rewarding to the trolls.

[knifeymoloko]

Shameless plug coming:

The admin script I created (@Badmin) deals with griefing by attempting to empower users to votekick.

1. If a user attempts a blank votekick (one without a reason specified), it's declined and the user is told to provide a reason.
2. If the user lists "griefing" (of several bastardized variations of it), the kickee is automatically checked for griefing.
3. If the kickee's grief score is above a certain (customizable) threshold, the kickee is automatically warned, kicked, or banned (depeding on the severity of the griefing).
4. On the inverse, if the user HASN'T been griefing, the votekick is automatically cancelled and the kicker is given a reason why.

@Badmin is only in its infancy, but I think the idea behind it is solid. I think if you can get users to consistently votekick griefers and you have a system in place to punish griefers without admin intervention, you can make griefing significantly less rewarding to the trolls.

great script, I have it running and it works very well

[SLoW]

great script, I have it running and it works very well

I'm glad to hear it! I haven't had much time/drive recently to keep working on it, but I have several enhancements in mind that should make matters even easier. :)

[Monsteri]

Oh yeah does sound like a good script indeed. If people keep adding stuff like this.. global moderators will not be needed in one point.

[Tydosius]

ok, i admit, griefing is bad. it ruins hiding (hmmm). so to stop it we need to put an anti-grief system. but then we run into problems:
stop people destroying player placed blocks.
but what about surprise attacks?
only allow people to destroy a few at a time.
but won't griefers hang around waiting to grief the blocks?
if someone else is near the blocks they cannot be destroyed.
what about people trying to do a surprise attack?

you have to look over these problems to create a fully grief-proof system which doesn't also restrict the war-like gameplay.

but i guess you could try making it so player-placed blocks which are near a player (exluding the guy destroying the blocks) respawn. the respawn time can also depend on distance, like instant respawn when it's within 3 blocks, and maybe 5 second respawn when at 8 blocks away. perhaps a 20 second respawn when there is no near player (excluding the guy destroying the blocks). it's fairly grief proof. and griefers will have a hard time destroying your structure when it WON'T GO DOWN.

i'd like to see your ideas.

[Gorman]

^
I believe that SLoW's solution is the best. No system can 100% accurately detect griefers, but a system can decide if it is likely or not, and correlate this with a user saying they are.

[SLoW]

^
I believe that SLoW's solution is the best. No system can 100% accurately detect griefers, but a system can decide if it is likely or not, and correlate this with a user saying they are.

Thanks for the praise Gorman. :) My current solution is by no means perfect, but I think it's a good first step. I firmly believe that if you can create a culture where quick, responsible, and accurate votekicks are encouraged, you can do a lot to curb griefing.

[Defaulter]

Stop griefing?

Well the problem is, griefing is just a form of trolling, and as long as two players are able to interact and effect each other in the game, sumone will find a way to troll the other, via hack/grief/spam etc.

[SLoW]

Stop griefing?

Well the problem is, griefing is just a form of trolling, and as long as two players are able to interact and effect each other in the game, sumone will find a way to troll the other, via hack/grief/spam etc.

You can't eliminate it 100%. There will always be griefing in this game. All we can do it find ways to deal with it that are more effective/efficient.

[demo123]

Hmm the red circle reminds me of xom.But a nice idea indeed.Tough.

[McSplat]

What if there was a script that enabled you to cast away a griefer to an unescapable coordinate on the map until the end of a match or a map reset?
Or a dig restriction?
Or both?

Rules are set like this:

1. Using the spade will not hurt people on your team destroying blocks, since if two people were to dig one after another in the same spot, one would accidentally kill another. It may seem like you could simply say "Well, then that person should be respawned at that same point". After a while of being killed by your teammate by accident, it tends to get annoying.

2. If you think someone is griefing/a "spy", type in /msgtns (short for Message To Not Send) (Username or #) of the griefer/"spy".
This will make it so that when you send a message in general or team chat, that message does not reach the griefer.
This also makes it easy for gathering whoever you can to keep eyes on a suspect.
To disable for one person, type that in again.
To disable for all affected, type in /msgopen (Message Open) (Team chat and PM remains with original functions)

3. Destroying a block on your team leaves you vulnerable for 10 seconds (Number to be defined by admin).
Not from one teammate, but from 3 or 4 or some other random number, depending on the team size and/or number of votes if there is a votekick in progress. If you get shot at by, let's say, 3 people, or grenaded by the said number of people from your team, you will immediately get cast away to an inescapable coordinate on that map. (Logging out and back in won't do any good; the server will remember your IP, and therefore you cannot return back onto the main map until the end of the current game or a map reset.) You can still get votekicked.
Also, switching teams is not going to circumvent anything.
This whole inescapable map coordinate could be switched off by admin's decision, making it similar to that one other script I can't remember the name of.

4. If there is only 1 other person on your team (Or some other low number), and he's griefing, hitting him with 1 shot from any gun at any place on his body will kill him, respawning him on the map NORMALLY, with the exception that the griefer now has the inability to dig for about 2 minutes.
(Unless defined by admin. The inescapable prison, as i'll now call it, could be switched off and replaced with the dig restriction and the requirements could stand in place for the said 2 minute, 5 minute, or whatever number the admin defines it as, dig restriction.)

5. Logic counters.
If something does get griefed, and someone on your team happens to be standing next to the scene of the crime, and you shoot him, a wireframe display will pop out of the last 9 blocks he destroyed for a brief 3 seconds.

Hope this idea helps somewhat. I got most of the concept down by having remembered a few scripts in gameplay and rethinking them. Feel free to add on to it or cut something from it.

P.S.

If there are block spammers, there is no rule set for it, but here is something you may find useful.

1. If there is someone block SPAMMING blocks on your team on your side, stick with votekicking. The other team may not like that one of your members are ADDING blocks to your side of the team.

[SLoW]

1. You can already do this by setting team killing to false in the pyspades config.

2. That sounds like a lot of extra work where a kick would do the job just as easily.

3. What's the point of making you killable by a random amount of teammates and possibly casting you away?

4. You need to think about what players/users consider griefing, and what the game considers griefing. The two are often drastically different, and this type of rule could have unintended consequences. Let's say someone blocks you in, you break those blocks, now you're a griefer. That isn't really fair or helpful.

5. I don't really get what you're suggesting here, but it sounds like it would require client modification.