Massive Amount Of Grief

[Namık]

a corss-ban system: (add ban types other/grief)

if player banned form "3" diffrent server with "grief" mark, said player will be unable to join the servers who ticked the "cross ban" in server settings "anti-grief" section, the reports with "grief" tag requires owner/reporting person to type in explonation and the game captures the server log in that spesific report for later rewiew (it could be nice if reporting person can only take spesific parts of the log like screen capture and attach it instead of entire think), if player thinks he is falsely cross-banned, thats when moderation will manually check the logs attached to player and remove/keep the cross ban.

i don t know how hard it will be to code this, or you guys even consider to code it, but the sheer amount of griefers in multiplayer really bad, i hope this wall of text may help in any way possible.

[Buggy Boy]

Who does the moderation though? I doubt the devs want to get involved with that sort of thing (as if they would have the time, working on the game etc).

I like the idea of the logs being kept if someone is marked as a griefer, as currently I think logs get deleted after each round which makes it very difficult to see exactly who griefed when if the round was ended prematurely (due to griefing, most likely).

Not sure how a cross-server ban would work, either. Servers are not connected to one another as far as I'm aware, and I don't think I would want there to be a connection as that probably introduces too many unknowns and possibilities for errors / problems. A Steam account could be marked as being a bad player, I've seen this in other games where the player's name is marked in a different colour so people know that they did bad stuff (the game can recognise this on a basic level already with the karma system, there could be a way to manually mark a player and their Steam account as well), I think it wears off after a set period, no moderation needed but it gives server owners the choice of whether to allow such people to even join, or maybe apply restrictions such as the player being unable to interact with certain items (e.g. the reactor, pumps, or cabinets - they're basically at the whim of the other players and have to ask for things), except to repair only.

I think if done properly, this concept has legs and could be very workable.

And I agree - the number of griefers is unacceptable and puts many good players off multiplayer mode, which is probably why multiplayer rounds often last so long (because half of the players are totally clueless as to how to play properly, often including the host!)

[sokolov]

Adding crossbans and marking people as griefers would just be more useful to griefers themselves than it would be useful to you. You could also bypass this system using Steam's Family Share.

Griefers can host fake servers and then ♥♥♥♥ you over forever, or you could be falsely flagged by a 11 year old who just started the game and knows nothing about it.

If you want to mentally survive while hosting a public server you gotta get your reddit moderator mentality on instead of just being a passive, boring host that barely is aware of what the crew is doing.
Its YOUR server that you are hosting, so you should act like it instead of having to depend on flawed systems to do stuff for you.

[Namık]

i tough about the "fake servers" that just tags people as griefer, thats why i included " if player thinks he is falsely cross-banned, thats when moderation will manually check the logs" if said players who abuse this system gets punished HEAVLY, i don t think this will be the issue (punishment could be like 2 month multiplayer ban or smt, or just being unable to join "corss-ban" enabled servers) and thats really the only part any moderation required, i doubt it will cause much lift to moderation/devs since like, a logs very obivius (this considering player able to clip a part of logs to report instead of whole think)

for the ones who say "just watch logs and ban them" the issue is... i quite literally saw and played in server who banned at least 28 griefer within 3 hours, the host ended up handing out log permisson to others so we can figure out faster. (there is too many griefer)

[Namık]

by the way the point of this thread is finding ideas to solve this issue, if you guys have idea even if its sounds stupid, plase type it down.

[アンジェル]

Originally posted by Sokolov:

Adding crossbans and marking people as griefers would just be more useful to griefers themselves than it would be useful to you. You could also bypass this system using Steam's Family Share.

Griefers can host fake servers and then ♥♥♥♥ you over forever, or you could be falsely flagged by a 11 year old who just started the game and knows nothing about it.

If you want to mentally survive while hosting a public server you gotta get your reddit moderator mentality on instead of just being a passive, boring host that barely is aware of what the crew is doing.
Its YOUR server that you are hosting, so you should act like it instead of having to depend on flawed systems to do stuff for you.

^that should be marked as topic answer

A cross server ban cannot work for the mentioned reasons. In doubt host your own server and be master of your own.

Or make a cross server banlist in secret without letting it become public.

[Namık]

the issue is, if its not supported by game/code, hosts will be forced to pick names/steamids from that "list" and ban then one by one otherwize they will just change name and join/grief again and list will be SOOOO long, like you will have to spent few hours going trough list before starting the server

[sokolov]

Originally posted by Namık:

the issue is, if its not supported by game/code, hosts will be forced to pick names/steamids from that "list" and ban then one by one otherwize they will just change name and join/grief again and list will be SOOOO long, like you will have to spent few hours going trough list before starting the server

Well, actually, people can share bannedplayers.xml between eachother from Barotrauma/Data/bannedplayers.xml and then put along a banlist together into one single downloadable file if you REALLY want to go through with this, or- you know, just accept the method you have mentioned earlier in the thread as its a much, much better alternative (mentioned below) than having half the playerbase (or more) banned due to you relying on lists made by various people with various preferences.

Originally posted by Namık:

the host ended up handing out log permisson to others so we can figure out faster. (there is too many griefer)

If you have multiple people on watch in your game whom you can trust or are perceptive then they will save you a lot of headache before anything would even happen.

Again, it is YOUR server, YOUR judgement and YOUR rules.
If you don't like how a person acts or plays, you can (or should) get rid of them- there are other servers they can go to or even host their own.
There are a lot of common behaviors that can help you find bad players before they make it with their respawn shuttle to your sub or even respawn.

I know this is harsh but if you always act all friendly and like a pushover to everyone who joins then automatically assume they will sort themselves out while you do nothing but be a Captain on the Helm 24/7 then you're willingfully signing up yourself for a griefing session.

Why would you want to remove live, human moderation and instead rely on unreliable automation that may not always be accurate or could even be exploited to globally remove you from the game? Minecraft is a large example on why such reporting system is a mistake.

[Evil Factory]

a cross-ban system, a cross report system or any type of global system designed to tag bad players will never work, from both a technical and a social standpoint
in both cases it WILL be abused, and the system WILL be used to make the griefing problem even worse, its unsolvable.

[climbingeastofwinter]

The only solution is to just host your own game and self-moderate, and maintain your own banlist.

[Maximum stupidity]

Minecraft server owners allready tried this a decade ago, there is good reason they quickly abandonned the idea.