Hi Admin/Mod,

Today let's discuss /cprivate issue.

I am proposing make the "private" a default. Whatever item like chest, door etc item will automatic be privated.

Becuase most of the item we placed will /cprivate it. Probably only few item will not be private, but sharing. And hardly we'll open for public.

I realize when i create a shop, or new house etc....those chest near to 20-30. and each of it need to type /cprivate and punch. It's kinda a hassle. Therefore I request to make it default.

If it's default, no one can say their item being stolen. Because all are auto private. Those non-private chest the player should aware of when he "/cremove" it.

Oh....and remember dont down vote me, I am a nice player <object class="emojione" data="https://resources.enjin.com/1489581540/themes/core/images/emojione/svg/1f600.svg?0" type="image/svg+xml" standby=":d">:d</object>. Just wanna propose something

The biggest reason that I say no to such a suggestion is the issue that admins and mods already have to remove cprivated chests of other members. If every chest or door was cprivated it would fill the server with blocks that only the original owner or admins could remove. I could see some potential in people also using these to deliberately get in the way of other people the extra time required to cprivate stops people from spamming private chests.

The guest world is already filled with cprivate structures made out of chests and furnaces and I'd hate to see this start happening on the main server when we already have regions.

Regions protect most chests and shops just require a bit more time to set up to be automatic since they have to be semi-public zones.

There is a way to /cprivate many chests at once. First type /lwc mode persist. Then /cprivate. This will make it so until you turn off the persist mode, every chest you hit will be privated. So you can just punch like 30 chests and done. Hope this helps.

Wow baconbits, I had no idea! Thanks <object class="emojione" data="https://resources.enjin.com/1489581540/themes/core/images/emojione/svg/1f600.svg?0" type="image/svg+xml" standby=":d">:d</object>

yea....bad idea for default...the biggest issue is if you set it to always cprivate, there is the potential that the chest will not register to the user as placed..and thus, you just made a cprivate chest that you cant access yourself.

mrbaconbitts, I dont get the procedure. Can you kindly elaborate more? i would like to learn it. Thanks

Um.....Yeah, Cryston just remind me of "region protection".... <object class="emojione" data="https://resources.enjin.com/1489581540/themes/core/images/emojione/svg/1f600.svg?0" type="image/svg+xml" standby=":d">:d</object>

Thanks.