Theoretically largest possible save file?

[Anybody]

If you have planted the maximum amount of bricks how much space would that take up on the disk?

[Ad Bot]

[WALDO]

If you have planted the maximum amount of bricks how much space would that take up on the disk?

Techinally that wouldn't be the largest save file possible. If you had A LOT of events on every single brick you planted and you maxed the brick count with those bricks. Then that would be one of the biggest save files ever and it would probably take a very long time to save or load it.

[Eepos2]

if you can add an unlimited amount of events to a brick there is no largest.

[Pompmaker2]

if you can add an unlimited amount of events to a brick there is no largest.

For some reason this sounds like some saying of wisdom, like "If you keep developing there is no limit" or something like that.

[Anybody]

what if there were no events? what would be the max?

[Peejster]

The thing is, the name of the datablock also matters. Having 100 bricks with the datablock name "A" is obviously going to make a smaller save file than 100 with the datablock name "DatablockBrickMaxSaveSize"

[Anybody]

zestimation for a save with out events and avarage datablock name length?

[Eepos2]

zestimation for a save with out events and avarage datablock name length?

Start a single player game in blockland, with duplicator enabled and place a selection of random bricks and duplicate them over and over until you hit the limit, then save the file and there's your answer.

[Pompmaker2]

Start a single player game in blockland, with duplicator enabled and place a selection of random bricks and duplicate them over and over until you hit the limit, then save the file and there's your answer.

Noobs all over attempt an instance of this with 1x1 spam. It is already being done.
if you were to, say, tolerate the unsightly swarm of red bricks for a few days with a running freebuild server, you could achieve a record.

[Xalos]

Let's put a sanity cap at a block line length of 255. Now, there's a brick limit of about 320K before your client can't keep up, and each brick can theoretically have up to 65535 events (I believe.) Now, let's put another sanity cap on event lengths at 255.

That makes the longest possible save size 255 * 65536 (one extra for the brick itself) * 320000.
That comes out to 5347737600000 bytes / 5222400000 kilobytes / 5100000 megabytes / 4980.5 gigabytes / 4.9 terabytes.

So yeah, Blockland saves can be freaking massive when you apply the worst case scenario.

[Anybody]

Let's put a sanity cap at a block line length of 255. Now, there's a brick limit of about 320K before your client can't keep up, and each brick can theoretically have up to 65535 events (I believe.) Now, let's put another sanity cap on event lengths at 255.

That makes the longest possible save size 255 * 65536 (one extra for the brick itself) * 320000.
That comes out to 5347737600000 bytes / 5222400000 kilobytes / 5100000 megabytes / 4980.5 gigabytes / 4.9 terabytes.

So yeah, Blockland saves can be freaking massive when you apply the worst case scenario.

interesting, thank you

[Greek2me]

Bricks have an artifical event limit of 100, so that's not possible.

[Eepos2]

700MB

[Pompmaker2]

700MB

Tell me more.