No seriously, you really need to stop them. All of the servers look like wastelands. On the Reddit server where I hang out and am an op, every second person coming in is a griefer. I ban 10 an hour sometimes. And despite that I have created several very well liked large projects only to have them die in hours, and I doubt I will be creating any more because it just isn't worth it. Griefers are ruining the game.
Ideas:
"/noalter username" - A way to flag people to disallow them to change anything...better than banning because they can appeal or whatever, and (this is important) the ability for a server owner to set it for everyone BY DEFAULT, unless an OP changes it. That way he can leave and know all of his stuff will still be there.
Warnings - Anybody who comes in and deletes more then x number of blocks that are not ground blocks gets an auto-boot, the noalter flag set, or at least warns any admins present.
Block Protection - set certain blocks to be non-deletable
Traps - Any blocks set with a flag will, when deleted, auto ban (or auto noalter) a user. Certain works seem to be a magnet for griefers.
Any other ideas. Something must be done, and it should be made top priority. This is far more important then new block types.
"Warnings: What if they are simply deleting a piece of their building/mural?"
Good point. Maybe some kind of weighting system is in order, or time/weighting system. If you kill x blocks in the first y minutes that you are there. There are issues with that approach as well though.
"Traps: What if someone accidentaly deletes a block which is flagged?"
How often do you accidentally delete blocks, especially blocks that are part of a large project? But yes, you do have a point, it does happen. That's why a "noalter" flag would be good, because they can appeal. And I agree it isn't the best of my suggestions, but I am throwing stuff out there.
"Vote to: Mute (chat), and Kick would be handy!"
How would you tabulate it, and what are the voting rules. All people on the server? All the people currently active? All talking? Would it be simple majority? Could it be gamed by a lot of griefers coming in at the same time? It might take a while too, which would be bad. Just some thoughts.
Something like block protection would be nice, by which I mean it should disallow other players to remove or build near your blocks (unless he's been added to your "buddy list" or something like that).
A flagging system could work too, so players will need to acquire certain flags to do various tasks (must like what's been said above).
Not trying to troll, just pointing things out here. A non-deletable block could also be placed by a griefer remember. All these things can be placed by griefers... there by making them basically useless.
@vote feature: good idea but we would need a system that labels people as afk and excludes them from voting after x seconds of complete inactivity. Also we all have to remember this is just a java game made by, and correct me if I'm wrong, a single person. So options are sort of limited. I'm sure he's feeling very overwhelmed.
@ninti's /noalter option: I have actually started a thread on that type of option, if you'd like, you can continue to discuss that option there.
Rollback Post to RevisionRollBack
B^lxxD^ lyfe
My Darwin fish evolved and ate your jesus fish.
No real suggestions, but just wanted to back up the idea that stopping griefers is a top priority.
I've stopped playing on public servers, I just run one on a machine at home and give the link to mates I know. So far no griefing, and loads of stuff has been built.
this would require an extra piece of data to be attached to every block, which may be bad, but...
can you assign blocks that players create to [playername] and make them nondeletable by everyone except [playername] (and OPs)? ground blocks would be assigned as such.
this would however allow griefers to place their own blocks next to yours and muck up your plans, so perhaps set a flag to the OP when blocks by two different players are placed within 2 blocks of eachother (so griefer cant build things around where you are and prevent you from expanding). Two players who are working on a project together could simply type something like /allow [player2] that will allow that players blocks to be near theirs without sending a warning to the OP (both players would have to type the command)
if you want to ban/flag people for deleting non-ground blocks, just send the flag after say, 7 nonground blocks destroyed. 7 blocks isnt much damage, and its enough of a buffer to save most people who rapidly start clicking thinking they are in build mode.
Rollback Post to RevisionRollBack
Eighth Blocks. Plox. It would make me so very happy. (click it!)
That means a griefer could easily just fill the rest of the map with non-deletable blocks.
such a gigantic undertaking would be noticed, but at the very least it would stop destruction. because rebuilding takes so much more time than just deleting some griefers filler blocks. OPs could have the ability to set players blocks to ground status and allow everyone to delete them.
keep up the argument though, the only way to win this battle is to think like a griefer and exploit every exploitable flaw in our plans...
Rollback Post to RevisionRollBack
Eighth Blocks. Plox. It would make me so very happy. (click it!)
I like the idea of OP-only indestructable blocks.
Perhaps they could also have the option to give the ability to friends, too.
Or, maybe a system could be set so you can only destroy your own blocks, the exception being the OP, of course.
And the ground blocks that are already there could be anyone's turf.
Be wicked hard to code, though, I suppose...but hey, if they could get multiplayer, they could do this.
Also, maybe, if you try to delete another player's block, it would pop up and identify whose it is.
So you could say in open chat, "Hey, username, can I delete this block right here? It's blocking me." "sure, go ahead"
A very easy way to fix the problems of greifers using the same blocks?
a Tier system: Ops>Members>Visitors So that you can build and such as a visitor, but tell you are set by an op to be a member, you can not construct such things as trap blocks. Other then being able to do that, members got no other powers.
Rollback Post to RevisionRollBack
<TrueWolves> That's what I meant Iguana, I'm like an Extra+, to just fill in tiny cracks... right?
<Iguana> YUS. <Iguana> BUT WE NEED YOU
<Iguana> You are like...Billy Mays Mighty Putty. (trademarked)
IRC quote on the Minecraft Machinima
True wolves, a great suggestion with the exception that op's will be swamped with thaving to type things like /member everytime someone wants to build on their public server. If this can be overcome then the tier system sounds perfect.
Rollback Post to RevisionRollBack
B^lxxD^ lyfe
My Darwin fish evolved and ate your jesus fish.
Visitors AND members can build, just that only members can set blocks that could be a problem, such as the trap and indestructible blocks, plus blocks laid by members could not be destroyed by visitors as a settable option for the server, other then that visitors is a lot like how non ops are now.
Rollback Post to RevisionRollBack
<TrueWolves> That's what I meant Iguana, I'm like an Extra+, to just fill in tiny cracks... right?
<Iguana> YUS. <Iguana> BUT WE NEED YOU
<Iguana> You are like...Billy Mays Mighty Putty. (trademarked)
IRC quote on the Minecraft Machinima
*if* it were possible to identify blocks by who built them (im just assuming this is possible, not sure if its feasible...)
then, given the tier system... visitors could also have all of their blocks deleted when they disconnect, unless they ask an OP to save it for them before they leave? thus, griefers building filler blocks can just get booted or the OP could just use /deleteblocks [griefer] or something
Rollback Post to RevisionRollBack
Eighth Blocks. Plox. It would make me so very happy. (click it!)
Good suggestions, but a lot of these are going to be difficult to apply to stuff that is carved out of the ground (e.g. tunnels, underground bases), which seem to be the biggest griefing target by far. It only takes a little bit of block deleting to flood an entire undergrond base complex.
Personally I think the griefing will go down quite a bit once the game goes pay to play.
It will, but anyway to help now is a plus, though I must say, for carved out things, traps and a few others become either harder to work with or just less likely to work...
Rollback Post to RevisionRollBack
<TrueWolves> That's what I meant Iguana, I'm like an Extra+, to just fill in tiny cracks... right?
<Iguana> YUS. <Iguana> BUT WE NEED YOU
<Iguana> You are like...Billy Mays Mighty Putty. (trademarked)
IRC quote on the Minecraft Machinima
solis: Actually, I think the blocks should just stay there automatically, with the option of removal being left to choice. It'd be incredibly annoying for a whole bunch of people to build a massive fortress/structure, and then they suddenly leave without saving. Their part of the structure instantly disappears? No, that'd be unfair to everyone else.
could be very costly to implement code and efficiency wise, but heres a stab at it:
players who are digging underground:
if player deletes a block whose z coord is below the z coord of the surface block directly above it, it is an underground block. if player deletes an underground block, set all blocks touching that block to [playername], unless one of those blocks is already assigned to something other than the ground.
i also wish that water was a little more limited. can the cursor turn red or something if there's water or lava behind the block its pointing at? this would provide some safety check when building underground, unless water was reprogrammed to not infinitely copy itself (i.e., if it could "drain")
however, with "draining" water you have the chance of a griefer creating a large underground cave and draining all the water from the surface of the level. [admittedly, super cool, but, bad for gameplay]
Rollback Post to RevisionRollBack
Eighth Blocks. Plox. It would make me so very happy. (click it!)
Ideas:
"/noalter username" - A way to flag people to disallow them to change anything...better than banning because they can appeal or whatever, and (this is important) the ability for a server owner to set it for everyone BY DEFAULT, unless an OP changes it. That way he can leave and know all of his stuff will still be there.
Warnings - Anybody who comes in and deletes more then x number of blocks that are not ground blocks gets an auto-boot, the noalter flag set, or at least warns any admins present.
Block Protection - set certain blocks to be non-deletable
Traps - Any blocks set with a flag will, when deleted, auto ban (or auto noalter) a user. Certain works seem to be a magnet for griefers.
Any other ideas. Something must be done, and it should be made top priority. This is far more important then new block types.
Warnings: What if they are simply deleting a piece of their building/mural?
Traps: What if someone accidentaly deletes a block which is flagged?
I'm a pigman!
Follow me on Twitter! https://twitter.com/MikeLouisseize
Vote to: Mute (chat), and Kick would be handy!
Perhaps make these options and their variables a server selectable setting.
Good point. Maybe some kind of weighting system is in order, or time/weighting system. If you kill x blocks in the first y minutes that you are there. There are issues with that approach as well though.
"Traps: What if someone accidentaly deletes a block which is flagged?"
How often do you accidentally delete blocks, especially blocks that are part of a large project? But yes, you do have a point, it does happen. That's why a "noalter" flag would be good, because they can appeal. And I agree it isn't the best of my suggestions, but I am throwing stuff out there.
"Vote to: Mute (chat), and Kick would be handy!"
How would you tabulate it, and what are the voting rules. All people on the server? All the people currently active? All talking? Would it be simple majority? Could it be gamed by a lot of griefers coming in at the same time? It might take a while too, which would be bad. Just some thoughts.
A flagging system could work too, so players will need to acquire certain flags to do various tasks (must like what's been said above).
@vote feature: good idea but we would need a system that labels people as afk and excludes them from voting after x seconds of complete inactivity. Also we all have to remember this is just a java game made by, and correct me if I'm wrong, a single person. So options are sort of limited. I'm sure he's feeling very overwhelmed.
@ninti's /noalter option: I have actually started a thread on that type of option, if you'd like, you can continue to discuss that option there.
My Darwin fish evolved and ate your jesus fish.
Support The Pirate Bay!
I've stopped playing on public servers, I just run one on a machine at home and give the link to mates I know. So far no griefing, and loads of stuff has been built.
I'm a pigman!
Follow me on Twitter! https://twitter.com/MikeLouisseize
can you assign blocks that players create to [playername] and make them nondeletable by everyone except [playername] (and OPs)? ground blocks would be assigned as such.
this would however allow griefers to place their own blocks next to yours and muck up your plans, so perhaps set a flag to the OP when blocks by two different players are placed within 2 blocks of eachother (so griefer cant build things around where you are and prevent you from expanding). Two players who are working on a project together could simply type something like /allow [player2] that will allow that players blocks to be near theirs without sending a warning to the OP (both players would have to type the command)
if you want to ban/flag people for deleting non-ground blocks, just send the flag after say, 7 nonground blocks destroyed. 7 blocks isnt much damage, and its enough of a buffer to save most people who rapidly start clicking thinking they are in build mode.
I'm a pigman!
Follow me on Twitter! https://twitter.com/MikeLouisseize
such a gigantic undertaking would be noticed, but at the very least it would stop destruction. because rebuilding takes so much more time than just deleting some griefers filler blocks. OPs could have the ability to set players blocks to ground status and allow everyone to delete them.
keep up the argument though, the only way to win this battle is to think like a griefer and exploit every exploitable flaw in our plans...
Perhaps they could also have the option to give the ability to friends, too.
Or, maybe a system could be set so you can only destroy your own blocks, the exception being the OP, of course.
And the ground blocks that are already there could be anyone's turf.
Be wicked hard to code, though, I suppose...but hey, if they could get multiplayer, they could do this.
Also, maybe, if you try to delete another player's block, it would pop up and identify whose it is.
So you could say in open chat, "Hey, username, can I delete this block right here? It's blocking me." "sure, go ahead"
a Tier system: Ops>Members>Visitors So that you can build and such as a visitor, but tell you are set by an op to be a member, you can not construct such things as trap blocks. Other then being able to do that, members got no other powers.
<Iguana> YUS. <Iguana> BUT WE NEED YOU
<Iguana> You are like...Billy Mays Mighty Putty. (trademarked)
IRC quote on the Minecraft Machinima
My Darwin fish evolved and ate your jesus fish.
Support The Pirate Bay!
<Iguana> YUS. <Iguana> BUT WE NEED YOU
<Iguana> You are like...Billy Mays Mighty Putty. (trademarked)
IRC quote on the Minecraft Machinima
then, given the tier system... visitors could also have all of their blocks deleted when they disconnect, unless they ask an OP to save it for them before they leave? thus, griefers building filler blocks can just get booted or the OP could just use /deleteblocks [griefer] or something
Personally I think the griefing will go down quite a bit once the game goes pay to play.
<Iguana> YUS. <Iguana> BUT WE NEED YOU
<Iguana> You are like...Billy Mays Mighty Putty. (trademarked)
IRC quote on the Minecraft Machinima
could be very costly to implement code and efficiency wise, but heres a stab at it:
players who are digging underground:
if player deletes a block whose z coord is below the z coord of the surface block directly above it, it is an underground block. if player deletes an underground block, set all blocks touching that block to [playername], unless one of those blocks is already assigned to something other than the ground.
i also wish that water was a little more limited. can the cursor turn red or something if there's water or lava behind the block its pointing at? this would provide some safety check when building underground, unless water was reprogrammed to not infinitely copy itself (i.e., if it could "drain")
however, with "draining" water you have the chance of a griefer creating a large underground cave and draining all the water from the surface of the level. [admittedly, super cool, but, bad for gameplay]