What is the largest save file you've ever seen somebody have or state they had? what is the largest file you've all ever had in the game? this question applies to all game mode worlds, but vanilla Minecraft only, no mods.
On the spigot forum I've seen somebody say he had a world folder size of 74gb, which to be honest is the largest I've seen somebody claim they had. I know the theoretical maximum is somewhere in the neighborhood of petabytes in size, but nobody really has this because nobody has explored this much of the world or found the time to preload it this much, and the storage for such a thing would be too expensive for most people.
But I'm asking this question because it'll help me determine whether or not I'll have to upgrade my Minecraft server storage at some point in the future. The RAM is fine, the CPU is fine, but the storage concerns me and unless Mojang intend on adding in world border settings in bedrock edition for both legit survival and creative/cheat worlds I'm afraid the unbound world sizes will become a problem in the future.
Not playing on a server presently but on my home system, I have several in the 10-20 gB size. I know the server I mostly played on trimmed his world after I went hunting as many strongholds as I could find, and was out over 10k in all directions. No idea what size he wanted to limit it to. What with 1-2 tB drives being so cheap I can't imagine you would ever fill one up.
My first world is 525 MB for the Overworld only, nearly all within region files (I deleted the Nether and End since I never use them after the "end game"), which has 109595 chunks for an average of about 4.9 KB per chunk (this is a 1.6.4 world so there are less blocks, especially underground, where the new stone types decrease the compression ratio in 1.8+, on the other hand, I've lit up all the caves which increases the complexity of block light data and freshly generated regions are around 10-15% smaller).
Also, one of the posts in the thread you linked to gives a formula for calculating the size of a world:
size in MB = (((n/256) + 1) **2 ) * 4
If I put in 8192 for n (the distance to the world border), which gives an area of 1048576 chunks I get 4356 MB, or about 4.25 KB per chunk, though to be safe I'd go with 5 KB per chunk (you also need to consider the Nether and End, and the fact that a chunk can never be smaller than 4 KB on disk due to the way the game saves them, so even a "void" world will have 4 MB region files, with the End being close to this limit).
Not playing on a server presently but on my home system, I have several in the 10-20 gB size. I know the server I mostly played on trimmed his world after I went hunting as many strongholds as I could find, and was out over 10k in all directions. No idea what size he wanted to limit it to. What with 1-2 tB drives being so cheap I can't imagine you would ever fill one up.
It's not the cost of the storage that is worrisome per se, I know it's unlikely I'd be needing something crazy like a 8 terabyte hard drive, but I'm using a 500gb SSD, of course I don't plan on just using 1 world file in the long run, when the alpha/beta is over and if it will support multiple instances I will use the server software to host about 4 world files tops, but capping the maximum active player count to 7, I could've had more players had I not gone for such a high render distance, being 22 chunks, was 32 chunks, but due to somebody's habit of breeding villagers I had to cut it back a bit to lower the demand.
still 22 chunks is pretty far and it's enough for me and anyone else on the world we're playing on.
2 of the worlds will be survival mode,
and the 2 other ones will be creative.
I could see myself needing about 2 terabytes though, worst case scenario.
I will have to keep an eye on the world folder size and see what happens.
Hello Agtrigormortis, I know this is an old post but I thought I should leave a comment because I have a world bigger than your friend does. For context own a Minecraft server and it's world is around 115GB. If you have any follow-up questions feel free to ask!
Hello Agtrigormortis, I know this is an old post but I thought I should leave a comment because I have a world bigger than your friend does. For context own a Minecraft server and it's world is around 115GB. If you have any follow-up questions feel free to ask!
That person wasn't a friend, I don't know that person on the other forum, I was just mentioning their post for example. Your file size is a lot, 115gb now the largest Minecraft save file I've been made aware of even though the theoretical limit is much larger than 115gb. I suppose you and anyone else you might have on your server have explored a lot.
You could use compression on your storage drive, but it's probably not advised as decompressing eats up the CPU resources.
Thanks for letting me know though, you've alerted me to how big save files can get in real terms. Definitely shouldn't skimp on storage.
I wish bedrock edition had the option to set world border sizes, this way
Hello Agtrigormortis, I know this is an old post but I thought I should leave a comment because I have a world bigger than your friend does. For context own a Minecraft server and it's world is around 115GB. If you have any follow-up questions feel free to ask!
One thing I'm curious about is the size per chunk or region file (fully generated), assuming a modern version, as this enables calculating how large a world with a given size/world border can get (the only figures I have are for vanilla/modded 1.6.4, where my first world is about 5 KB per chunk and modded worlds range up to 8 KB per chunk*, with the biggest factor being the amount of unique blocks; a world with 3 times the ground depth (191 layers) is only slightly larger per chunk than a world with closer to the original depth (more and higher peaks above sea level) but far more block variants; in the same vein the doubling in depth in 1.18 may be less important than new added blocks (in fact, an overall decrease in ores may offset the depth; simply adding the 1.8 stone types to TMCW caused a noticeable increase in save size, likewise, as I light up caves the more complex lightmap decreases compression).
*Up-to date data for my first world and two modded worlds; note that I used MCEdit to get the exact number of chunks (region files may be incomplete, which is why I mentioned fully generated regions unless you have a tool that can report the chunk count):
World1 (vanilla 1.6.4); the average size per chunk is 5115 bytes, or about 80 MB per level 4 map (2048x2048 blocks / 16384 chunks). None of these include other dimensions (only TMCWv5 still has the Nether/End) or files, which are all quite small (level.dat, player data, map data, and structure data, which is separate from regions in 1.6.4; conversely, newer versions save a lot more data in separate files):
TMCWv5 (modded with extensive new world generation and blocks); the average size per chunk is 7879 bytes, or about 123 MB per level 4 map and 50% larger than vanilla:
TripleHeightTerrain (modded with 3 times the ground depth, otherwise vanilla block composition); the average size per chunk is 8573 bytes, or about 134 MB per level 4 map and 67% larger than vanilla (this is still a lot less than a simple multiplication by 3 would give. Note that the overall height limit doesn't matter as only non-empty sections are created and saved, down to a minimum of 4 KB per chunk due to the region file format):
One thing I'm curious about is the size per chunk or region file (fully generated), assuming a modern version, as this enables calculating how large a world with a given size/world border can get (the only figures I have are for vanilla/modded 1.6.4, where my first world is about 5 KB per chunk and modded worlds range up to 8 KB per chunk*, with the biggest factor being the amount of unique blocks; a world with 3 times the ground depth (191 layers) is only slightly larger per chunk than a world with closer to the original depth (more and higher peaks above sea level) but far more block variants; in the same vein the doubling in depth in 1.18 may be less important than new added blocks (in fact, an overall decrease in ores may offset the depth; simply adding the 1.8 stone types to TMCW caused a noticeable increase in save size, likewise, as I light up caves the more complex lightmap decreases compression).
*Up-to date data for my first world and two modded worlds; note that I used MCEdit to get the exact number of chunks (region files may be incomplete, which is why I mentioned fully generated regions unless you have a tool that can report the chunk count):
World1 (vanilla 1.6.4); the average size per chunk is 5115 bytes, or about 80 MB per level 4 map (2048x2048 blocks / 16384 chunks). None of these include other dimensions (only TMCWv5 still has the Nether/End) or files, which are all quite small (level.dat, player data, map data, and structure data, which is separate from regions in 1.6.4; conversely, newer versions save a lot more data in separate files):
TMCWv5 (modded with extensive new world generation and blocks); the average size per chunk is 7879 bytes, or about 123 MB per level 4 map and 50% larger than vanilla:
TripleHeightTerrain (modded with 3 times the ground depth, otherwise vanilla block composition); the average size per chunk is 8573 bytes, or about 134 MB per level 4 map and 67% larger than vanilla (this is still a lot less than a simple multiplication by 3 would give. Note that the overall height limit doesn't matter as only non-empty sections are created and saved, down to a minimum of 4 KB per chunk due to the region file format):
So basically, if I am understanding this correct here, air blocks have negligible affects if any on the overall save file size, but also it comes down to the number of unique blocks as well as any blocks not in the original file for a particular world seed?
Common sense would dictate how much of the world has generated determines the overall size of the file,
and it does because the more chunks are generated the more information that gets added to the region files.
I'm sure player data has affects on this too, including ender chest items per player,
but the majority of the changes to the file size appears to be coming from the region files.
So basically, if I am understanding this correct here, air blocks have negligible affects if any on the overall save file size, but also it comes down to the number of unique blocks as well as any blocks not in the original file for a particular world seed?
Common sense would dictate how much of the world has generated determines the overall size of the file,
and it does because the more chunks are generated the more information that gets added to the region files.
I'm sure player data has affects on this too, including ender chest items per player,
but the majority of the changes to the file size appears to be coming from the region files.
Only air blocks in completely empty, and unallocated, sections do not count; "air" is simply represented by 0, similar to how "stone" is 1, "grass" is 2, and so on, all of which convey the exact same amount of information, and every block has its own associated light level and metadata (they all take up 2.5 bytes per block in memory). What really matters is how easily the data can be compressed; the reason why lighting up caves increases save size, despite mostly only modifying "air" blocks (by setting their block light data to something other than 0), and the number of torches I place being several times less than the amount of ores I remove (replacing them with air) is because it is harder to compress than a light map which is all 0s (which could be compressed to almost nothing in the best case. e.g. "repeat 0 4096 times per section"). Likewise, the 1.8 stone types only change the "metadata" array, making it less compressible than an array of mostly 0s.
This can be best seen by comparing a Superflat world using the "Overworld" preset, with all normal features (including caves and passive mobs spawning during world generation, unique features of TMCW) and one with 256 layers of solid stone) - the latter has far more non-air blocks and is over 3 times deeper (16 sections vs 4-5) but is far less complex so it compresses down to almost nothing; the difference in the sizes of the compressed region files is actually due to the empty space between chunks, which are already compressed so the additional compression has little effect (the Region format is most efficient when chunks are exactly a multiple of 4 KB in size; this is not unlike a file system, which commonly use a sector size of 4 KB, hence the "size on disk" being a multiple of 4 KB, so as far as the disk is concerned it is not wasting any space over individual chunk files (which is what very old versions used but this was highly inefficient due to having to open so many files):
An analysis of the normal region (the other is nothing but stone) and renderings of both and the underground of the normal region (this has more impact than any surface features in this case); despite being 77% air the normal region is 18 times larger when compressed because of all the different blocks it contains (185 variants), and to a lesser extent, entities (entities, including tile entities, do take up more space than a block but are far less common, only 698 compared to 15.24 million non-air blocks, so they probably have no impact at all):
Seed is 3067604371870005932
Center is 256, -256 and radius is 256 blocks (from 0, -512 to 511, -1)
Showing up to 10 results for each category. Locations are the center unless noted.
Locations of ravine cave systems:
1. 376 -248
Locations of random cave systems:
1. 88 -488
Locations of largest caves by volume:
1. 424 37 -184 (type: 2, length: 395, width: 30, volume: 107415)
2. 440 33 -200 (type: 1, length: 216, width: 23, volume: 31297)
3. 440 29 -488 (type: 1, length: 182, width: 24, volume: 29750)
4. 88 26 -24 (type: 1, length: 328, width: 17, volume: 28216)
Locations of largest ravines by volume:
1. 424 27 -312 (type: 3, length: 222, width: 17, depth: 47, volume: 89847)
2. 136 21 -184 (type: 2, length: 190, width: 11, depth: 37, volume: 32476)
3. 232 24 -280 (type: 2, length: 180, width: 10, depth: 34, volume: 25931)
Locations of largest circular rooms by volume:
1. 313 13 -403 (width: 44, volume: 20859)
Locations of abandoned mineshafts by corridor length (center of central room):
1. 232 21 -168 (span: 9, size: 202, length: 2050)
2. 328 26 -88 (span: 9, size: 147, length: 1505)
3. 104 21 -280 (span: 8, size: 125, length: 1240)
4. 200 40 -408 (span: 8, size: 113, length: 1150)
5. 440 37 -392 (span: 5, size: 54, length: 560)
Generating map...
Generating caves... 6% 12% 18% 25% 31% 37% 43% 50% 56% 62% 68% 75% 81% 87% 93% 100%
Rendering map... 6% 12% 18% 25% 31% 37% 43% 50% 56% 62% 68% 75% 81% 87% 93% 100%
Total air volume is 1339850 blocks (8.662919%)
For comparison, this is the largest region file in TMCWv5, which compresses to about 2.25 times the size of the normal Superflat world; there are a total of 221 block variants and 512 entities and tile entities; otherwise, the biggest difference is that I lit up all the caves, with nearly 15,000 torches, while on the order of 40,000 ores were mined; the underground included the two largest types of caves with nearly 20% of all blocks on layers 4-62 being air:
My bad, I wrote the comment at around 4:30AM so I was really tired, I thought I should tell you that the world has grown since then, originally it was 115GB now it is 118GB. For context I own an Anarchy Server, because of this people often try to go out really far hence the large amount of chunk generation.
i had a server for a year and lot of ppl played there. It was like 3gb, so i guess this is pretty heavy.
I am aware that file sizes can reach over 100 gigabytes but it doesn't appear to be very common, it would only be possible if say the world was long term and/or if people did a lot of exploring in these worlds. The more of the world that generates the more of it gets saved to disk.
Just building alone isn't enough to make file sizes this bloated and staying within the confines of your render distance means you're limited to this area plus the 386 on the Y coordinate in the Overworld, and even then you cannot remove bedrock in legit survival without exploits.
But it is good to know that some people did reach over 100gb, such as thxtnt, this is enough information to say anyone that hosts a Minecraft server for good measure should consider at minimum a 250gb Solid State drive, factoring in space needed for the OS and all the necessary files. Higher capacity would be better, but unfortunately more space costs more money. My personal recommendation if anyone can afford it is 500gb.
What is the largest save file you've ever seen somebody have or state they had? what is the largest file you've all ever had in the game? this question applies to all game mode worlds, but vanilla Minecraft only, no mods.
On the spigot forum I've seen somebody say he had a world folder size of 74gb, which to be honest is the largest I've seen somebody claim they had. I know the theoretical maximum is somewhere in the neighborhood of petabytes in size, but nobody really has this because nobody has explored this much of the world or found the time to preload it this much, and the storage for such a thing would be too expensive for most people.
But I'm asking this question because it'll help me determine whether or not I'll have to upgrade my Minecraft server storage at some point in the future. The RAM is fine, the CPU is fine, but the storage concerns me and unless Mojang intend on adding in world border settings in bedrock edition for both legit survival and creative/cheat worlds I'm afraid the unbound world sizes will become a problem in the future.
https://www.spigotmc.org/threads/is-this-normal-minecraft-world-size.321374/?__cf_chl_jschl_tk__=634b7f97b61060d12c10282b43823b1d058125d8-1585846854-0-AdVwy55JylLSKWFs7Vh4FhAvJOyhAQYCiv5c0NVKdPQVYVhD5wTkUuOvxWyFPbgSMogj53vD7Lsq2yR1RJMshqg0I0qlVp9_M0ewW4295iZDNlV5qhuJjbIwm2QuK7983uJa7QVOSDM-opJv-eKJeiJcxTVXIKxKHVEr8p_Q3V0wfGMKTquzckl-cG8_zUx3AXp_ib55Lhv0C_gzyvLPpZ6earZAGrDidN7dT9QII9zYIazxGcM8SoWTdahQ0PH7kKrtBB-cnGu5PX_lQFygnfh7-sCnRpvvh1L3zVrfjj2GWi8wzjL77lxrVQJbtxRvc39cP8zIM7eWAUfp8JNaZhw
Not playing on a server presently but on my home system, I have several in the 10-20 gB size. I know the server I mostly played on trimmed his world after I went hunting as many strongholds as I could find, and was out over 10k in all directions. No idea what size he wanted to limit it to. What with 1-2 tB drives being so cheap I can't imagine you would ever fill one up.
Learn something new each day
My first world is 525 MB for the Overworld only, nearly all within region files (I deleted the Nether and End since I never use them after the "end game"), which has 109595 chunks for an average of about 4.9 KB per chunk (this is a 1.6.4 world so there are less blocks, especially underground, where the new stone types decrease the compression ratio in 1.8+, on the other hand, I've lit up all the caves which increases the complexity of block light data and freshly generated regions are around 10-15% smaller).
Also, one of the posts in the thread you linked to gives a formula for calculating the size of a world:
If I put in 8192 for n (the distance to the world border), which gives an area of 1048576 chunks I get 4356 MB, or about 4.25 KB per chunk, though to be safe I'd go with 5 KB per chunk (you also need to consider the Nether and End, and the fact that a chunk can never be smaller than 4 KB on disk due to the way the game saves them, so even a "void" world will have 4 MB region files, with the End being close to this limit).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
It's not the cost of the storage that is worrisome per se, I know it's unlikely I'd be needing something crazy like a 8 terabyte hard drive, but I'm using a 500gb SSD, of course I don't plan on just using 1 world file in the long run, when the alpha/beta is over and if it will support multiple instances I will use the server software to host about 4 world files tops, but capping the maximum active player count to 7, I could've had more players had I not gone for such a high render distance, being 22 chunks, was 32 chunks, but due to somebody's habit of breeding villagers I had to cut it back a bit to lower the demand.
still 22 chunks is pretty far and it's enough for me and anyone else on the world we're playing on.
2 of the worlds will be survival mode,
and the 2 other ones will be creative.
I could see myself needing about 2 terabytes though, worst case scenario.
I will have to keep an eye on the world folder size and see what happens.
Hello Agtrigormortis, I know this is an old post but I thought I should leave a comment because I have a world bigger than your friend does. For context own a Minecraft server and it's world is around 115GB. If you have any follow-up questions feel free to ask!
That person wasn't a friend, I don't know that person on the other forum, I was just mentioning their post for example. Your file size is a lot, 115gb now the largest Minecraft save file I've been made aware of even though the theoretical limit is much larger than 115gb. I suppose you and anyone else you might have on your server have explored a lot.
You could use compression on your storage drive, but it's probably not advised as decompressing eats up the CPU resources.
Thanks for letting me know though, you've alerted me to how big save files can get in real terms. Definitely shouldn't skimp on storage.
I wish bedrock edition had the option to set world border sizes, this way
we can stop file sizes getting out of control.
One thing I'm curious about is the size per chunk or region file (fully generated), assuming a modern version, as this enables calculating how large a world with a given size/world border can get (the only figures I have are for vanilla/modded 1.6.4, where my first world is about 5 KB per chunk and modded worlds range up to 8 KB per chunk*, with the biggest factor being the amount of unique blocks; a world with 3 times the ground depth (191 layers) is only slightly larger per chunk than a world with closer to the original depth (more and higher peaks above sea level) but far more block variants; in the same vein the doubling in depth in 1.18 may be less important than new added blocks (in fact, an overall decrease in ores may offset the depth; simply adding the 1.8 stone types to TMCW caused a noticeable increase in save size, likewise, as I light up caves the more complex lightmap decreases compression).
*Up-to date data for my first world and two modded worlds; note that I used MCEdit to get the exact number of chunks (region files may be incomplete, which is why I mentioned fully generated regions unless you have a tool that can report the chunk count):
World1 (vanilla 1.6.4); the average size per chunk is 5115 bytes, or about 80 MB per level 4 map (2048x2048 blocks / 16384 chunks). None of these include other dimensions (only TMCWv5 still has the Nether/End) or files, which are all quite small (level.dat, player data, map data, and structure data, which is separate from regions in 1.6.4; conversely, newer versions save a lot more data in separate files):
TMCWv5 (modded with extensive new world generation and blocks); the average size per chunk is 7879 bytes, or about 123 MB per level 4 map and 50% larger than vanilla:
TripleHeightTerrain (modded with 3 times the ground depth, otherwise vanilla block composition); the average size per chunk is 8573 bytes, or about 134 MB per level 4 map and 67% larger than vanilla (this is still a lot less than a simple multiplication by 3 would give. Note that the overall height limit doesn't matter as only non-empty sections are created and saved, down to a minimum of 4 KB per chunk due to the region file format):
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
So basically, if I am understanding this correct here, air blocks have negligible affects if any on the overall save file size, but also it comes down to the number of unique blocks as well as any blocks not in the original file for a particular world seed?
Common sense would dictate how much of the world has generated determines the overall size of the file,
and it does because the more chunks are generated the more information that gets added to the region files.
I'm sure player data has affects on this too, including ender chest items per player,
but the majority of the changes to the file size appears to be coming from the region files.
Only air blocks in completely empty, and unallocated, sections do not count; "air" is simply represented by 0, similar to how "stone" is 1, "grass" is 2, and so on, all of which convey the exact same amount of information, and every block has its own associated light level and metadata (they all take up 2.5 bytes per block in memory). What really matters is how easily the data can be compressed; the reason why lighting up caves increases save size, despite mostly only modifying "air" blocks (by setting their block light data to something other than 0), and the number of torches I place being several times less than the amount of ores I remove (replacing them with air) is because it is harder to compress than a light map which is all 0s (which could be compressed to almost nothing in the best case. e.g. "repeat 0 4096 times per section"). Likewise, the 1.8 stone types only change the "metadata" array, making it less compressible than an array of mostly 0s.
This can be best seen by comparing a Superflat world using the "Overworld" preset, with all normal features (including caves and passive mobs spawning during world generation, unique features of TMCW) and one with 256 layers of solid stone) - the latter has far more non-air blocks and is over 3 times deeper (16 sections vs 4-5) but is far less complex so it compresses down to almost nothing; the difference in the sizes of the compressed region files is actually due to the empty space between chunks, which are already compressed so the additional compression has little effect (the Region format is most efficient when chunks are exactly a multiple of 4 KB in size; this is not unlike a file system, which commonly use a sector size of 4 KB, hence the "size on disk" being a multiple of 4 KB, so as far as the disk is concerned it is not wasting any space over individual chunk files (which is what very old versions used but this was highly inefficient due to having to open so many files):
An analysis of the normal region (the other is nothing but stone) and renderings of both and the underground of the normal region (this has more impact than any surface features in this case); despite being 77% air the normal region is 18 times larger when compressed because of all the different blocks it contains (185 variants), and to a lesser extent, entities (entities, including tile entities, do take up more space than a block but are far less common, only 698 compared to 15.24 million non-air blocks, so they probably have no impact at all):
(1:0),Stone,10041575
(1:1),Stone,950617
(1:3),Stone,701724
(1:5),Stone,832918
(2:0),Grass,252992
(3:0),Dirt,1316730
(4:0),Cobblestone,5230
(4:1),Cobblestone,312
(5:0),Wood Planks,10454
(7:0),Bedrock,262144
(9:0),Water,33755
(10:1),Lava (active),60278
(12:0),Sand,2805
(13:0),Gravel,202055
(13:1),Gravel,180899
(14:0),Gold Ore,9071
(15:0),Iron Ore,89965
(16:0),Coal Ore,157399
(17:0),Wood,812
(17:12),Wood,388
(18:0),Leaves,6799
(21:0),Lapis Lazuli Ore,4314
(24:0),Sandstone,7
(30:0),Web,1426
(31:0),(Unused Shrub),60445
(35:15),Black Wool,2
(37:0),Flower,447
(37:1),Flower,53
(37:2),Flower,73
(37:3),Flower,59
(37:4),Flower,43
(37:6),Flower,57
(37:7),Flower,39
(37:8),Flower,42
(37:9),Flower,39
(37:10),Flower,75
(37:11),Flower,45
(37:12),Flower,58
(37:13),Flower,43
(37:14),Flower,56
(37:15),Flower,33
(38:0),Rose,427
(39:0),Brown Mushroom,141
(39:1),Brown Mushroom,24
(39:2),Brown Mushroom,61
(39:3),Brown Mushroom,59
(39:4),Brown Mushroom,11
(43:0),Double Stone Slab,22
(44:0),Stone Slab,60
(47:0),Bookshelf,14
(48:0),Moss Stone,1782
(49:0),Obsidian,2381
(51:1),Fire,2
(51:3),Fire,3
(51:4),Fire,1
(51:5),Fire,8
(51:6),Fire,7
(51:7),Fire,13
(51:8),Fire,17
(51:9),Fire,12
(51:10),Fire,8
(51:11),Fire,3
(51:12),Fire,2
(51:14),Fire,1
(52:0),Monster Spawner,52
(53:0),Wooden Stairs,236
(53:1),Wooden Stairs,226
(53:2),Wooden Stairs,156
(53:3),Wooden Stairs,168
(54:2),Chest,15
(54:3),Chest,14
(54:4),Chest,20
(54:5),Chest,14
(56:0),Diamond Ore,2229
(58:0),Crafting Table,2
(59:2),Crops,27
(59:3),Crops,30
(59:4),Crops,28
(59:5),Crops,14
(59:6),Crops,15
(59:7),Crops,26
(60:7),Farmland,224
(62:2),Lit Furnace,2
(62:3),Lit Furnace,2
(64:0),Wooden Door,7
(64:1),Wooden Door,13
(64:2),Wooden Door,5
(64:8),Wooden Door,23
(64:9),Wooden Door,2
(65:2),Ladder,13
(65:4),Ladder,4
(66:0),Rail,865
(66:1),Rail,765
(66:3),Rail,1
(66:4),Rail,2
(66:5),Rail,2
(66:7),Rail,1
(66:8),Rail,1
(67:0),Stone Stairs,7
(67:1),Stone Stairs,7
(67:2),Stone Stairs,9
(67:3),Stone Stairs,11
(72:0),Wooden Pressure Plate,16
(73:0),Redstone Ore,18085
(75:1),Redstone Torch (off),27
(75:2),Redstone Torch (off),45
(75:3),Redstone Torch (off),35
(75:4),Redstone Torch (off),52
(75:9),Redstone Torch (off),18
(75:10),Redstone Torch (off),20
(75:11),Redstone Torch (off),11
(75:12),Redstone Torch (off),10
(75:13),Redstone Torch (off),12
(82:0),Clay,120
(83:0),Sugar Cane,26
(83:2),Sugar Cane,2
(85:0),Fence,6004
(91:4),Jack-o'-Lantern,27
(98:0),Stone Bricks,1699
(98:1),Mossy Stone Bricks,153
(98:2),Cracked Stone Bricks,80
(98:3),Circle Stone Bricks,56
(99:10),Huge Brown Mushroom (Stem),2
(99:11),Huge Brown Mushroom,5
(100:1),Huge Red Mushroom (Northwest),2
(100:2),Huge Red Mushroom (North),3
(100:3),Huge Red Mushroom (Northeast),2
(100:4),Huge Red Mushroom (West),3
(100:5),Huge Red Mushroom (Top),25
(100:6),Huge Red Mushroom (East),3
(100:7),Huge Red Mushroom (Southwest),2
(100:8),Huge Red Mushroom (South),3
(100:9),Huge Red Mushroom (Southeast),2
(100:10),Huge Red Mushroom (Stem),6
(101:0),Iron Bars,4
(102:0),Glass Pane,154
(141:2),Carrots,12
(141:3),Carrots,9
(141:4),Carrots,7
(141:5),Carrots,12
(141:6),Carrots,7
(141:7),Carrots,9
(142:2),Potatoes,5
(142:3),Potatoes,4
(142:4),Potatoes,4
(142:5),Potatoes,3
(142:6),Potatoes,7
(142:7),Potatoes,5
(145:5),Anvil,1
(145:11),Anvil,1
(162:0),Future Block!,452
(164:1),Future Block!,2
(164:2),Future Block!,1
(164:3),Future Block!,2
(164:4),Future Block!,1
(164:5),Future Block!,9
(164:6),Future Block!,1
(164:7),Future Block!,2
(164:8),Future Block!,1
(164:9),Future Block!,2
(164:10),Future Block!,4
(165:1),Future Block!,7
(165:2),Future Block!,6
(165:3),Future Block!,7
(165:4),Future Block!,6
(165:5),Future Block!,23
(165:6),Future Block!,6
(165:7),Future Block!,7
(165:8),Future Block!,6
(165:9),Future Block!,7
(165:10),Future Block!,17
(165:11),Future Block!,14
(175:0),Future Block!,100
(175:1),Future Block!,118
(175:2),Future Block!,16046
(175:4),Future Block!,162
(175:5),Future Block!,164
(185:0),Future Block!,901
(185:8),Future Block!,2078
(186:0),Future Block!,524
(186:8),Future Block!,1048
(187:0),Future Block!,46
(187:8),Future Block!,120
(200:0),Future Block!,419
,,
,<Entities>,579
Bat,Bat,16
CaveSpider,CaveSpider,1
Chicken,Chicken,93
Cow,Cow,64
Creeper,Creeper,18
Enderman,Enderman,1
Endermite,Endermite,2
Horse,Horse,56
Item,Brown Mushroom,2
Item,Rail,5
MinecartChest,MinecartChest,23
Pig,Pig,66
Rabbit,Rabbit,67
Sheep,Sheep,94
Silverfish,Silverfish,5
Skeleton,Skeleton,14
Spider,Spider,5
Villager,Villager,32
Zombie,Zombie,15
,,
,<TileEntities>,119
Chest,Chest,63
Furnace,Furnace,4
MobSpawner,MobSpawner,52
For comparison, this is the largest region file in TMCWv5, which compresses to about 2.25 times the size of the normal Superflat world; there are a total of 221 block variants and 512 entities and tile entities; otherwise, the biggest difference is that I lit up all the caves, with nearly 15,000 torches, while on the order of 40,000 ores were mined; the underground included the two largest types of caves with nearly 20% of all blocks on layers 4-62 being air:
(1:0),Stone,10242487
(1:1),Stone,754446
(1:3),Stone,961268
(1:5),Stone,1076115
(2:0),Grass,230698
(3:0),Dirt,1494260
(3:2),Dirt,4
(4:0),Cobblestone,10032
(4:1),Cobblestone,199
(5:0),Wood Planks,223
(5:1),Wood Planks,1349
(5:2),Wood Planks,280
(5:3),Wood Planks,1931
(7:1),Bedrock,257907
(7:5),Bedrock,4237
(9:0),Water,127499
(11:0),Lava,90947
(12:0),Sand,23735
(13:0),Gravel,164018
(13:1),Gravel,234942
(14:0),Gold Ore,6693
(14:5),Gold Ore,4
(14:6),Gold Ore,15
(14:7),Gold Ore,18
(15:0),Iron Ore,75216
(15:5),Iron Ore,185
(15:6),Iron Ore,622
(15:7),Iron Ore,183
(16:0),Coal Ore,137139
(16:5),Coal Ore,275
(16:6),Coal Ore,778
(16:7),Coal Ore,225
(17:0),Wood,23383
(17:1),Pine Wood,11591
(17:2),Birch Wood,7054
(17:12),Wood,44256
(17:13),Wood,1876
(17:14),Wood,10632
(17:15),Wood,116
(18:0),Leaves,497175
(18:1),Pine Leaves,99608
(18:2),Birch Leaves,147340
(18:4),Leaves (Permanent),13
(21:0),Lapis Lazuli Ore,3410
(21:5),Lapis Lazuli Ore,4
(21:6),Lapis Lazuli Ore,17
(21:7),Lapis Lazuli Ore,22
(24:0),Sandstone,1575
(30:0),Web,529
(31:0),(Unused Shrub),16642
(37:0),Flower,354
(37:1),Flower,15
(37:2),Flower,31
(37:3),Flower,36
(37:4),Flower,25
(37:6),Flower,39
(37:7),Flower,41
(37:8),Flower,22
(37:9),Flower,12
(37:10),Flower,25
(37:11),Flower,19
(37:12),Flower,36
(37:13),Flower,22
(37:14),Flower,6
(37:15),Flower,13
(38:0),Rose,233
(39:0),Brown Mushroom,825
(39:1),Brown Mushroom,374
(39:2),Brown Mushroom,504
(39:3),Brown Mushroom,440
(39:4),Brown Mushroom,378
(48:0),Moss Stone,230
(49:0),Obsidian,39232
(50:1),Torch,1090
(50:2),Torch,1117
(50:3),Torch,866
(50:4),Torch,901
(50:5),Torch,11009
(52:0),Monster Spawner,9
(54:2),Chest,12
(54:3),Chest,20
(54:4),Chest,9
(54:5),Chest,13
(56:0),Diamond Ore,1660
(56:6),Diamond Ore,6
(60:7),Farmland,8
(62:3),Lit Furnace,16
(64:1),Wooden Door,1
(64:3),Wooden Door,1
(64:8),Wooden Door,2
(65:2),Ladder,3
(65:3),Ladder,13
(65:4),Ladder,16
(65:5),Ladder,8
(66:0),Rail,95
(66:1),Rail,15
(73:0),Redstone Ore,13851
(73:5),Redstone Ore,12
(73:6),Redstone Ore,115
(73:7),Redstone Ore,15
(75:1),Redstone Torch (off),20
(75:2),Redstone Torch (off),11
(75:3),Redstone Torch (off),13
(75:4),Redstone Torch (off),14
(78:0),Snow Layer,80965
(79:0),Ice,12876
(80:0),Snow,2809
(82:0),Clay,1317
(83:0),Sugar Cane,3
(85:0),Fence,215
(85:1),Fence,886
(85:2),Fence,307
(85:3),Fence,940
(91:4),Jack-o'-Lantern,1
(97:0),Hidden Silverfish (Smooth Stone),4309
(97:6),Hidden Silverfish (Smooth Stone),320
(97:7),Hidden Silverfish (Smooth Stone),479
(97:8),Hidden Silverfish (Smooth Stone),485
(98:0),Stone Bricks,825
(98:1),Mossy Stone Bricks,188
(98:2),Cracked Stone Bricks,105
(99:1),Huge Brown Mushroom (Northwest),37
(99:2),Huge Brown Mushroom (North),32
(99:3),Huge Brown Mushroom (Northeast),37
(99:4),Huge Brown Mushroom (West),32
(99:5),Huge Brown Mushroom (Top),146
(99:6),Huge Brown Mushroom (East),32
(99:7),Huge Brown Mushroom (Southwest),37
(99:8),Huge Brown Mushroom (South),32
(99:9),Huge Brown Mushroom (Southeast),37
(99:10),Huge Brown Mushroom (Stem),55
(99:11),Huge Brown Mushroom,5
(100:1),Huge Red Mushroom (Northwest),52
(100:2),Huge Red Mushroom (North),43
(100:3),Huge Red Mushroom (Northeast),52
(100:4),Huge Red Mushroom (West),44
(100:5),Huge Red Mushroom (Top),152
(100:6),Huge Red Mushroom (East),44
(100:7),Huge Red Mushroom (Southwest),54
(100:8),Huge Red Mushroom (South),46
(100:9),Huge Red Mushroom (Southeast),54
(100:10),Huge Red Mushroom (Stem),70
(100:11),Huge Red Mushroom,20
(129:0),Emerald Ore,1106
(129:6),Emerald Ore,1
(142:4),Potatoes,1
(142:5),Potatoes,3
(142:6),Potatoes,1
(142:7),Potatoes,3
(160:0),Future Block!,36
(161:0),Future Block!,103084
(161:3),Future Block!,971
(162:0),Future Block!,966
(164:1),Future Block!,72
(164:2),Future Block!,53
(164:3),Future Block!,72
(164:4),Future Block!,53
(164:5),Future Block!,136
(164:6),Future Block!,53
(164:7),Future Block!,72
(164:8),Future Block!,53
(164:9),Future Block!,72
(164:10),Future Block!,80
(164:11),Future Block!,5
(165:1),Future Block!,51
(165:2),Future Block!,45
(165:3),Future Block!,51
(165:4),Future Block!,45
(165:5),Future Block!,207
(165:6),Future Block!,45
(165:7),Future Block!,51
(165:8),Future Block!,45
(165:9),Future Block!,51
(165:10),Future Block!,76
(165:11),Future Block!,10
(166:1),Future Block!,51
(166:2),Future Block!,45
(166:3),Future Block!,51
(166:4),Future Block!,45
(166:5),Future Block!,183
(166:6),Future Block!,45
(166:7),Future Block!,51
(166:8),Future Block!,45
(166:9),Future Block!,51
(166:10),Future Block!,73
(166:11),Future Block!,5
(168:12),Future Block!,33286
(168:13),Future Block!,77029
(168:14),Future Block!,34722
(168:15),Future Block!,43758
(174:0),Future Block!,3662
(174:1),Future Block!,2781
(174:2),Future Block!,3466
(175:0),Future Block!,54
(175:1),Future Block!,44
(175:2),Future Block!,5394
(175:4),Future Block!,110
(175:5),Future Block!,26
(185:0),Future Block!,2025
(185:1),Future Block!,1
(185:8),Future Block!,4654
(185:13),Future Block!,3
(186:0),Future Block!,938
(186:8),Future Block!,2012
(186:13),Future Block!,4
(187:0),Future Block!,156
(187:8),Future Block!,332
(188:0),Future Block!,1615
(188:1),Future Block!,10
(188:2),Future Block!,6
(188:3),Future Block!,13
(188:4),Future Block!,6
(188:5),Future Block!,13
(188:6),Future Block!,16
(188:7),Future Block!,4
(188:8),Future Block!,12
(188:9),Future Block!,12
(188:10),Future Block!,12
(191:5),Future Block!,76
(200:0),Future Block!,356
,,
,<Entities>,433
Arrow,Arrow,3
Bear,Bear,5
Chicken,Chicken,64
Cow,Cow,61
Item,Arrow,2
Item,Bone,4
Item,Egg,9
Item,Gunpowder,4
Item,Rotten Flesh,8
Item,Slimeball,2
Item,String,1
Item,Sugar,1
MinecartChest,MinecartChest,13
Pig,Pig,67
Rabbit,Rabbit,65
Sheep,Sheep,93
Wolf,Wolf,17
XPOrb,XPOrb,3
Zombie,Zombie,11
,,
,<TileEntities>,79
Chest,Chest,54
Furnace,Furnace,16
MobSpawner,MobSpawner,9
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
My bad, I wrote the comment at around 4:30AM so I was really tired, I thought I should tell you that the world has grown since then, originally it was 115GB now it is 118GB. For context I own an Anarchy Server, because of this people often try to go out really far hence the large amount of chunk generation.
The largest single player world I have is 11 gigs
i had a server for a year and lot of ppl played there. It was like 3gb, so i guess this is pretty heavy.
I am aware that file sizes can reach over 100 gigabytes but it doesn't appear to be very common, it would only be possible if say the world was long term and/or if people did a lot of exploring in these worlds. The more of the world that generates the more of it gets saved to disk.
Just building alone isn't enough to make file sizes this bloated and staying within the confines of your render distance means you're limited to this area plus the 386 on the Y coordinate in the Overworld, and even then you cannot remove bedrock in legit survival without exploits.
But it is good to know that some people did reach over 100gb, such as thxtnt, this is enough information to say anyone that hosts a Minecraft server for good measure should consider at minimum a 250gb Solid State drive, factoring in space needed for the OS and all the necessary files. Higher capacity would be better, but unfortunately more space costs more money. My personal recommendation if anyone can afford it is 500gb.
Fr its crazy that some world can weight so much! Impressive