Blockland Forums > Suggestions & Requests
New brick ownership level: Static (=Public, no need)
Demian:
We could really use a new brick ownership level that allows everyone to build on the bricks but nobody is allowed to paint, hammer, or wrench the bricks. Not even the host. This type of ownership would allows us to build terrains and environments without worrying about anyone messing with them.
For example I am currently building a full 1:1 scale Bedroom. I would load that save with the static ownership. That would allow everyone to build on the Bedroom bricks like terrain or interior but nobody could mess with the bricks by painting, hammering, or wrenching. Preventing the host from doing this makes it easier for the host build himself. The host doesn't need to worry about using the Destructo wand or painting/wrenching.
When saving bricks the static bricks should not be saved. There is no need to save them anyways since those bricks cannot be modified in any way.
Edit: No need. What I described here is the "public" ownership level: http://forum.blockland.us/index.php?topic=204315.msg5648648#msg5648648
gr8dayseth:
That's actually a good idea. :o
Lugnut:
so like public except totally unmodifiable?
the current public bricks are only destructable via d-wand.
no one (not even the host) can do any of the other stuff, and the only way to change them to not-public to modify them is to use a tool like my ownershipper, and it's not exactly popular.
Demian:
--- Quote from: Lugnut on August 12, 2012, 04:05:58 PM ---so like public except totally unmodifiable?
the current public bricks are only destructable via d-wand.
no one (not even the host) can do any of the other stuff, and the only way to change them to not-public to modify them is to use a tool like my ownershipper, and it's not exactly popular.
--- End quote ---
Oh! I didn't know that. Is there a way to disable the destructo wanding on those bricks?
Lugnut:
Do this in console: serverCmdDPB(){}
temporarily removes the ability to destructo wand the bricks.
However, I don't know what all goes into that command, and until I do, I can't reconstruct it - therefore repairing it.
so basically temporarily permanently until you reboot the server.