Author Topic: I absolutely hate the save format.  (Read 2585 times)


Look at this.
I either have to go though my entire server and though 100's of peoples builds waiting for them to come online, remove the bricks that are mine and reimburse everyone for the stuff they lost, and/or make an add-on that can change the BL_ID of a brick and then use it on every single messed up brick on the server.


Could Badspot really not save every brick with a BL_ID?
Would that just be too much?

For reference the bricks in the save files look like this:
Quote
1x1 Round" 105.75 -0.75 0.5 2 0 7  0 0 1 1 1
Would it have really broken the game to do this:
Quote
1x1 Round" 105.75 -0.75 0.5 2 0 7  0 0 1 1 1 22749
Come the forget on, this is absurd.


Amen. This massively hindered my very old Mini Empires servers, as when I saved every single brick became mine, even if I selected "Saved Owner" (I used brick terrain)

Zombiedude probably remembers.
« Last Edit: August 11, 2014, 12:11:35 AM by Zanaran2 »

Amen. This massively hindered my very old Mini Empires servers, as when I saved every single brick became mine, even if I selected "Saved Owner" (I used brick terrain)

Zombiedude probably remembers.
To fix this >>
Save the map,
Then save the map with the players builds on.
Load the map
Load the players builds, problem solved.

To fix this >>
Save the map,
Then save the map with the players builds on.
Load the map
Load the players builds, problem solved.
I'm fairly certain that wouldn't work.

1000 lines of the one without the ID is 45KB
1000 lines WITH the ID is 51KB

I tried to get it up to 10,000 for a more likely brick count but it crashed notepad++
and somehow that ended up with 79,402 lines

so for that many without the ID, it was 3,567KB
and with the ID it was 3,878KB

anyway. the point is. that would add a lot of data. but it was actually less than I was expecting when I started doing this so maybe it wouldn't be such a bad idea

that would add a lot of data
Is this sarcasm? I'm only asking because usually you don't say "but" after sarcasm.

I mean, it's 300kb for a massive build.
Like really? Who doesn't have 300kb to spare?

yeah, just do the blid thing and add some compression. then space wont be an issue either and you've solved two problems.

yeah, just do the blid thing and add some compression. then space wont be an issue either and you've solved two problems.
I think the idea behind having BL_ID only saved on baseplates was for compression of a sort.

I did my own test with the extra size, this time on a 10MiB save file (near the brick limit)

Old size: 10252 KiB
New size: 11552 KiB

The extra storage needed is almost irrelevant.
« Last Edit: August 11, 2014, 12:38:29 AM by Pecon »

yes i agree with op, it can't be too much trouble to add the blid for each brick

Is this sarcasm? I'm only asking because usually you don't say "but" after sarcasm.
did you stop reading after that "but" or something? I specifically said it wouldn't be a bad idea

anyway, judging by what pecon said, which I didn't know before, you can fix this issue just by building on baseplates? why wouldn't you do that anyway?

did you stop reading after that "but" or something? I specifically said it wouldn't be a bad idea

anyway, judging by what pecon said, which I didn't know before, you can fix this issue just by building on baseplates? why wouldn't you do that anyway?
The server did not allow people to build on the ground.
Everything was on baseplates.

then I guess I misunderstood what pecon said. unless someone was building on somebody else's baseplate?

then I guess I misunderstood what pecon said. unless someone was building on somebody else's baseplate?
Don't tell me people shouldn't build on each other's bricks.
I assume you're not going there. There's this thing called build trust for a reason.

Don't tell me people shouldn't build on each other's bricks.
I assume you're not going there. There's this thing called build trust for a reason.
well, no. but if they have that sorta trust anyway what does it matter if all of the bricks belonged to one of them?