Obviously griefing can stop with good op's, so get some and stop whineing. But when people hack through spawn jails when you're away, or other stuff like that, it's big. The best way to do this is having admin blocks kick people when they are walked inside. It is possible and simple as water changes physics, so obviously this would be a good route.
I like this. Simple and effective. Youre not supposed to be inside any brick at all really, more so admin bricks.
I think ( cant remember if it was said or not) that having the ability to have ownership would work the best. Or the admin has to trust someone to have the ability to remove or add blocks.
Or you could have a list of people who joined the server and when and what they did. Also there would be an ability to select a name and click Ban
So if i joined a server at 3 PM today and made a house consisting of 100 blocks, it would say:
Menen 3:00 PM Thursday, August 27th 2009 +100
If a greifer named Greiflover joined a server at 4 Pm Yesterday and deleted 100 blocks it would say :
Greiflover 4:00 PM Wednesday, August 26th 2009 -100
It would be an easy way to keep track of who joins when.
Rollback Post to RevisionRollBack
Quote from Kilgallon »
Quote from MomizerRox »
Quote from ZarroTsu »
Creepa stole ma bike. [SSSS]
Sooo... when's the next seecret Friday update topic going up? =[
That wouldn't be too hard, but stoping griefing works better than banning griefers. I think we should head at that. Simple and effective in prevention will work better. There will be nothing to worry about on the next update. Notch will make hacks optional. I still think it would be simple enough to just make being inside admin blocks kick you, but why not?
Why not take GMOD for example? Using Prop Protection works nicely. Wouldnt it be able to work since admin blocks are for admin only? But this would also make things practically permanent. So if people build regular grass it would make them unbreakable. Which would lead to some problems.
Although I don't know what "GMOD" is, it's a major ****ing waste to make it so only op's and the person who placed to delete blocks. (what I got from your post) What kind of game would it be? Single player with a chat >.>
Ops can designate an entire stucture to become unchangeable after the creator is done by placing a block in one corner, and another in the opposite corner by typing "/secure" or something like that. It would make a 3d box around the selection invincible (or at least everything but air) so it doesn't get griefed. From what I've seen between the WoM /fill code, and a /dense command the either comes default on JTE's server or was editted in, it seems possible.
Also, to add onto katnipz /fz, perhaps it would /banip or /ban the person if they left while frozen. Or at least keep the names in frozen.txt and keep them frozen until they return and someone un-freezes them.
That would be good on it's own and part of the /banhammer command, to bad not everyone has a Mac x.x;
I lol'd.
Then it won't mac ban them.
_______
Anyways, the build/destroy rate is not really going to be that much of a help.
What about those people who make basements to their houses, or castle, hmm?
Their build:Destruct rate would be more on the destroy rate, hmm, would you banhammer an innocent dwarf ( underground castle, ftw ) .
Or an op that makes a sector ( Secret underground op city that only trusted people, or hackers can get into other than ops ) it is a large underground/water box that takes a lot of excavating to make.
I say take down the build/destroy rate idea, or at least mark it down.
how about /suspicious [insertname] and after that if they do more than 90% destroying they are frozen until an admin unfreezes them so they can check they haven't been griefing
I want to support freeze, but the problem is it would definitely need something else.
Being sneaky would be nice.
rouge = red rogue = a deceitful and unreliable scoundrel
I don't think you're referring to 'rouge ops' in a trans-language way as to say 'communist ops' so spell it right >:sad.gif:
edit
We have /kick, /ban, /banip, so we should also have /freeze (or /fz) and /freezeip, and add another text file. It allows you to 'ban' someone from ever being able to do something, but they can also make an appeal. The only kind of griefing they can then do is spamming chat which doesn't work very well and will be caught easily in the logs :smile.gif:
Rollback Post to RevisionRollBack
"I want to see forum posts saying "how do i kill dragon" with replies reading "lol"."
---> vede claimed Notch said this (and it is awesome).
3: Map backup on login
This one is most likely one someone should be able to turn off, as it's not that practical for everyone, and even more so if the greifer has been there for a while, but as a not to hard to program 3rd party tool that someone can use to undo a "shock griefer" who caused a lot of damage, it should be quite useful, also useful in servers that were empty but not taken down, if 2 people went on to this empty server and messed up everything, just load the point they joined... not the most practical, but again a tool someone can consider to write up if they have a use for it, it's better then a tool that tracks every move someone made.
I have this on my server, edited into cmss. It's quite effective, actually. If anyone is interested in it, send me a msg and I'll give you the details.
Sand, gravel, water, lava, air...
Or you could have a list of people who joined the server and when and what they did. Also there would be an ability to select a name and click Ban
So if i joined a server at 3 PM today and made a house consisting of 100 blocks, it would say:
Menen 3:00 PM Thursday, August 27th 2009 +100
If a greifer named Greiflover joined a server at 4 Pm Yesterday and deleted 100 blocks it would say :
Greiflover 4:00 PM Wednesday, August 26th 2009 -100
It would be an easy way to keep track of who joins when.
[simg]http://img850.imageshack.us/img850/4148/mysigv2.png[/simg]
it's shorter then /banip AND it lets you talk to them before you ban them
Also, to add onto katnipz /fz, perhaps it would /banip or /ban the person if they left while frozen. Or at least keep the names in frozen.txt and keep them frozen until they return and someone un-freezes them.
I lol'd.
Then it won't mac ban them.
_______
Anyways, the build/destroy rate is not really going to be that much of a help.
What about those people who make basements to their houses, or castle, hmm?
Their build:Destruct rate would be more on the destroy rate, hmm, would you banhammer an innocent dwarf ( underground castle, ftw ) .
Or an op that makes a sector ( Secret underground op city that only trusted people, or hackers can get into other than ops ) it is a large underground/water box that takes a lot of excavating to make.
I say take down the build/destroy rate idea, or at least mark it down.
Being sneaky would be nice.
rouge = red
rogue = a deceitful and unreliable scoundrel
I don't think you're referring to 'rouge ops' in a trans-language way as to say 'communist ops' so spell it right >:sad.gif:
edit
We have /kick, /ban, /banip, so we should also have /freeze (or /fz) and /freezeip, and add another text file. It allows you to 'ban' someone from ever being able to do something, but they can also make an appeal. The only kind of griefing they can then do is spamming chat which doesn't work very well and will be caught easily in the logs :smile.gif:
---> vede claimed Notch said this (and it is awesome).
I have this on my server, edited into cmss. It's quite effective, actually. If anyone is interested in it, send me a msg and I'll give you the details.