Join 2,358+ Players and socialize together

Join the Community Today

Come hang out with us on the Minecraft Addicts Forums — it's the perfect place to chat, trade cool stuff, and connect with awesome builders just like you! Let's plan epic builds, create amazing worlds together, and then show off your masterpieces to everyone! Plus, we’re all about having fun, so feel free to talk about anything under the sun—games, hobbies, favorite snacks, you name it! Can't wait for you to join and share all the Minecraft magic!

Register Account Login Join our Discord

anti griefing suggestion

Status
Not open for further replies.

TautWOLF

Active member
Joined
Jan 1, 2011
Messages
44
hey umm you guys know how everybody is complaigning that there getting stuff stolen from them by there chests well why not make it so when they put there chest down its automatically set to private instead of public that way the griefing from chests would stop and if they want a chest set to public they have to set it eh sound good? is it possable?
 
I like the idea...this would make it

(default) set chest down makes it owned by user that sets it down and private to that user.

want to let others use it? type in the command.

I like it just not sure how easy it would be to implement.

thanks for the heads up any one else's thoughts?
 
is there still a 20 chest limit for lwc? If so, is there any way to increase it?

I know i'm past 20 chests which makes me feel vulnerable.
 
I think it is default to public because there are spots where people want it to be public however those are used less often. Maybe a good a good idea.
 
@ricoc0op i dont think there ever was a limit on the chests.

Also i love the sound of this idea, public chests arent used as much and if they are required you could simply type /lwc r chest then its public again.
 
I'm not sure if this would be easily done atm. When I did some testing with lwc before, I don't think it's possible to go from 'private' to 'password' protection (shared) or vice-versa. As far as I understand, 'public' means 'no lwc protection yet' so the user can choose to have it either 'private' or 'password.' If there is already lwc protection (like auto-private), I don't think 'password' would be available as an option any more.

It may have changed since I played around with it though...
 
Thanks for the suggestion TautWOLF, unfortunately the plugin does not currently support changing the default mode. When you create a chest, it is not considered LWC Public either... it's simply a chest until you use the LWC command (Public/Private/Password).

The only way to have LWC protect chests automatically would be to have the plugin resident at all times to check for chest creation (rather than called with a command), so if the plugin does go that route, it may be buggy for quite some time before they get it right.

To answer your question ricoc0op, I don't believe we have configured a chest protection limit in the new version. I'll look around to make sure we're not overlooking a default value somewhere.
 
Status
Not open for further replies.
Back
Top