You guys have no idea how much stuff I'd have to go through to get some bricks savable and others not. All of the brick ownership logic is done in script and all of the stuff that makes saving work like getposition and getdatablock is done in code. When a new person joins a server, you'd have to process every brick to figure out if they can save it or not then tell them about it. Or you could transmit the owner's bl_id of each brick and have the clients figure it out, but that takes a lot of bandwidth. Not to mention that this kind of thing is open to an unbelievable number of bugs and workarounds and we'd see tons of blm/rtb style mods that re-implement the saving system just to fix them which is not something I want to re-visit.
Technical issues aside, philosophically it doesn't make sense. You want to cripple the game just to deal with a handful of people who are jerks. But after you do that, they will just find some other way to be jerks and you (me) will have wasted a huge amount of time with very little accomplished. The jerks will always find a way to be jerks. Just ban them. Post your builds in the gallery here or on the rtb forum or on your own website if you want credit and adoration.
To clarify: this is the end of the discussion of this issue. The game is about finding builds online, saving them, and doing what you like with them. I'm not changing it and if you find some crazy way to stop saves from working, I will patch the game in order to fix it (already done it once, please don't waste any more of my time).
-----
On the other issue, I definitely agree that there should be a way to save with brick ownership. Often you have to restart or something when hosting a server and it'd be great to be able to save off the full state of the server.