Author Topic: Brick Ownership + Updates  (Read 1246 times)

Two questions.
A: Sometimes public bricks, when built on top of, turn my bricks to public, but NOT ALWAYS. Sometimes they're fine! I have one save where I built on public bricks, but my bricks are still my bricks. However, once I actually complete the garage I've been building, it turns public. So, why are they not always turning my bricks public? Is there a way to keep it from happening? I'd like to be able to have people build on public bricks and not lose all their build to the perms system being stupid when it comes to public bricks.
B: Is this game ever going to be updated? Has anyone heard anything from the developer, whether it's "it's done, I'm finished" or "I'm taking a long break" or "Help I am about to be hit by a bus"?

Why is there no (obvious) edit button? I meant to say "I'm done, IT'S finished" so it wasn't quite as redundant

B: Badspot is still doing fixes now and then. The last update was about a month and a half ago. And apparently there's a hat update coming "who knows when".

Okay, good, now I know. I'd like the next update to be right now and fix the stupid perms bug.

Sometimes public bricks, when built on top of, turn my bricks to public, but NOT ALWAYS. Sometimes they're fine! I have one save where I built on public bricks, but my bricks are still my bricks. However, once I actually complete the garage I've been building, it turns public. So, why are they not always turning my bricks public? Is there a way to keep it from happening? I'd like to be able to have people build on public bricks and not lose all their build to the perms system being stupid when it comes to public bricks.
Still need an answer to this. Should I put it as a bug report? Is there a way around it?

I suspect that you'll keep ownership if you build on public bricks with a baseplate touching them, to separate your build
otherwise you'd need a custom saving addon to do it

This is because of the bullstuff way ownership is saved. Only bricks that are on the ground have their ownership written to the save file, the others are supposed to inherit it from the brick stacks.

If you're working with friends and you own all baseplates, all bricks will be yours after loading. If your friends also own some baseplates and the builds are connected, prepare for total randomness in who owns which brick.

Badspot could fix this, but he doesn't want to.

I was testing with some of the saving mechanics, and it would be possible to save every brick's ownership and work with the loading system
it would just about double the number of lines in each save file, but I doubt it'd be of too much detriment

I was testing with some of the saving mechanics, and it would be possible to save every brick's ownership and work with the loading system
it would just about double the number of lines in each save file, but I doubt it'd be of too much detriment

You can optimize that quite a bit. Instead of saving ownership per brick, you save bricks per owner. First write a line with the bl_id (like GROUP 1163) and then write all bricks of this group. This would allow backwards compatiblity with old saves and actually make the file size smaller.


On a local server, there's nothing stopping you from doing that right now as an add-on. However, on other servers the client doesn't actually know who owns which bricks. Sending all ownership with commandtoclient would be inefficient and take forever, as you have to convert all data to text.

The best solution is badspot implementing proper ownership saving in the engine.

would the default loading system interpret it correctly if you literally just wrote group 6887? I thought it figured it out based off of already planted bricks and as a tag on the line under a brick

would the default loading system interpret it correctly if you literally just wrote group 6887? I thought it figured it out based off of already planted bricks and as a tag on the line under a brick

No. I'm assuming badspot still wants to improve the game and will modify the default scripts if necessary.