ALRIGHT time to correct myself Y'all are getting mad about a few things so I'll be correcting those things in this comment 1. Stacked books don't add more data This is half wrong and half right, yes you can't store "unique" info, but the point is how much info you can store not how much unique info 2. "You should use NBT data" bro... that's creative only you can't do that in survival (tbf it would take you proby over a thousand years to place that many chests) 3. 1028 bytes at 2:09 should be 1024 This is my first actual mistake, on screen it says "1028", that was wrong, it's 1024, what I said was correct however the onscreen text was wrong, I should've fixed that, mb 4. Kilobyte and kibibyte I never actually explained this in the video, the difference of 1024 bytes and 1000 bytes is that 1000 bytes is a kilobyte and 1024 bytes is a kibibyte, in the video I said 1024 bytes is a kilobyte but that's wrong, 1024 bytes is a kibibyte not kilobyte 5. End and nether are smaller than the overworld This was another mistake on me, the end and nether are the same 60Mx60M size, but it's 256 blocks tall not 384, so it's actually much smaller than the overworld 6. 20w14∞ If I made a part 2, I'd proby base it around the 20w14∞ update, the april fools update that adds (according to the minecraft wiki) 2,147,483,645 dimensions, Idk how I forgot about this update when making this video honestly it would've been such a good ending So, much apologies if this confused y'all mega nerds I did make some mistakes but not anything major
@@ZeppyTube Also argument to number 1, to count as info stored, it must be unique info stored. Otherwise you're just adding redundancy. Yeah redundancy does technically store information but the problem here is if you want any error correction, which is the point of redundancy, the stacks can't do that function, you'd have to add your own CRC bits in the book stacks, effectively storing the information of one book. However you could argue that the amount of books in each stacks stores information and I would agree, but it would only be 27 x 16 more bits per chest. It could store 16 bits, or two bytes, per inventory slot. You could probably use this as CRC but an already getting ahead of myself, no one is gonna make a real file system out of this lol
@@ZeppyTube Also as a part 2, I would be interested in how efficient storing stuff in a Minecraft world is. How much data is wasted on Minecraft shenanigans instead of my PRECIOUS data?
This is such a nerdy comment and I hate I understand all of it and completely get your point LOL I honestly don't care if it's unique or not, yes the whole point is having unique data but it's still data nonetheless, so I don't see it as too much of an issue
@@ZeppyTube If you understood that then maybe you should've started from scratch instead of nabbing the numbers from other sources since you seem way more knowledeable than them
The stacked books don’t really store any unique info, the only extra data you get is the stack count, but you can give the book a title and an author for a little extra data...
The video is full of mistakes. In 2:50 he says that a chest is 1728 bits by counting that a stack is 64 bits, but in reality a stack can't store 64 bits, only 6 bits (log2(64)) + the info that you can get from the type of block. This also translates into the book part, because he is asuming that you can have a stack of 16 books where each book has different content.
Stacking books or shulkers doesn’t give you new information so any time you stack items its not actually adding new data, and putting multiple minecart chests per block sounds cool until you consider entity cramming. If you really wanted to make the biggest data storage there are a few things to change: 1 you cant stack anything because stacking items requires them to have the same nbt data which means you cant have two different items stacked together like two books with different laters in them. 2 you should name each book to give it a few extra digits of data. 3 instead of just putting shulkers in chests, you can put actually copy a chests nbt data to put that chest in another chest and so on ten times recursively. 4 bundles could be ised to stack items with different nbt data so that could drastically increase storage in each layer. 5 now you can come back to minecarts, put the most recursively containing chest in bundles in the minecart chest 27 times to fill its inventory then copy the minecart chest 20 ish times per block to get to entity cramming. This assumes theres no hard cap in the form of an entire limit, which im not sure about, if there is then this wont work beyond adding just a few extra chests. Taking all these steps would change the calculations drastically meaning the final number is mostly very different than what you came to, id be very interested if you do a part two with these ideas.
Ok but where's the scicraft level redstone contraption to read and write these bytes and the 16bit CPU to process it, a GPU and 16MB of RAM to run DOOM in Alpine in Minecraft? Also the storage bus would be quite slow here. The higher storage capacity might not even be useable. This is actually a real computer problem, when you hear L1, L2, or L3 cache, that's essentially RAM inside the CPU that's super fast, because using the RAM you put in the motherboard is too slow. This feels stupid though so juat pull a Spu7nix and write a programming language to use a Minecraft world as a file system instead, things will definitely go well, trust me. Anyways mega nerd out, this was fun, sub
2:10 ackshwually tl;dr it doesn't matter, the difference is insignificant anyway. All it does is confuse people. You're wrong. It's 1024 (i don't get if this was a bit or not, if it was I laughed but I got confused when I tried to read it again) Also 1000 and 1024 are both correct. They're just different ways of measurement. 1000 Megabytes(MB) is 1 Gigabyte(GB) 1024 Mebibytes(MiB) is 1 Gibibyte(GiB) This is also why hard drives show up as lower than their rated spec in windows. Windows uses gibibyte but calls it gigabyte. I don't know why, go ask microshit. Hard Drive manufacturers use gigabyte.
The nether and end is actually smaller than the overworld as they dont have negative y coordinates and their hight limit is 255 blocks instead of the 319 blocks in the overworld.
16 book thing is wrong cause theres no point storing same information 16 times at best you can just get like extra bits from the amount of same book you have. so after that point all numbers need to be multiplied by16 to be more accurate
You are actually not doing "1000 bytes = 1 kilobyte" wrong, it is true, however, 1024 bytes IS 1 Kib (kibibyte) this is why when you buy hard drives that label themselves as "1 terabyte" are lower when you actually use them (931 "gigabytes") Because the computer is using binary. It goes from kibibyte to mebibyte to gebibyte to tebibyte.. etc.
@@jacpa2011 no, you're already working with strings when you show the user, how you format it doesn't really change much. They really just don't care enough and keep using the outdated terminology because not enough people care
but... cant you just place a shulker in a chest CTRL + MID CLICK and then put it in a shulker than CTRL + MID CLICK that shulker and put it in a new chest over and over?
You can compress the data even further, by having the minecraft instances stored in the books uncompress to minecraft worlds filled with chests filled with shulkers filled with books.
ALRIGHT time to correct myself
Y'all are getting mad about a few things so I'll be correcting those things in this comment
1. Stacked books don't add more data
This is half wrong and half right, yes you can't store "unique" info, but the point is how much info you can store not how much unique info
2. "You should use NBT data"
bro... that's creative only you can't do that in survival (tbf it would take you proby over a thousand years to place that many chests)
3. 1028 bytes at 2:09 should be 1024
This is my first actual mistake, on screen it says "1028", that was wrong, it's 1024, what I said was correct however the onscreen text was wrong, I should've fixed that, mb
4. Kilobyte and kibibyte
I never actually explained this in the video, the difference of 1024 bytes and 1000 bytes is that 1000 bytes is a kilobyte and 1024 bytes is a kibibyte, in the video I said 1024 bytes is a kilobyte but that's wrong, 1024 bytes is a kibibyte not kilobyte
5. End and nether are smaller than the overworld
This was another mistake on me, the end and nether are the same 60Mx60M size, but it's 256 blocks tall not 384, so it's actually much smaller than the overworld
6. 20w14∞
If I made a part 2, I'd proby base it around the 20w14∞ update, the april fools update that adds (according to the minecraft wiki) 2,147,483,645 dimensions, Idk how I forgot about this update when making this video honestly it would've been such a good ending
So, much apologies if this confused y'all mega nerds I did make some mistakes but not anything major
@@ZeppyTube NOOOOO it was funnier when you didn't respond to it
@@ZeppyTube Also argument to number 1, to count as info stored, it must be unique info stored. Otherwise you're just adding redundancy.
Yeah redundancy does technically store information but the problem here is if you want any error correction, which is the point of redundancy, the stacks can't do that function, you'd have to add your own CRC bits in the book stacks, effectively storing the information of one book.
However you could argue that the amount of books in each stacks stores information and I would agree, but it would only be 27 x 16 more bits per chest.
It could store 16 bits, or two bytes, per inventory slot.
You could probably use this as CRC but an already getting ahead of myself, no one is gonna make a real file system out of this lol
@@ZeppyTube Also as a part 2, I would be interested in how efficient storing stuff in a Minecraft world is. How much data is wasted on Minecraft shenanigans instead of my PRECIOUS data?
This is such a nerdy comment and I hate I understand all of it and completely get your point LOL
I honestly don't care if it's unique or not, yes the whole point is having unique data but it's still data nonetheless, so I don't see it as too much of an issue
@@ZeppyTube If you understood that then maybe you should've started from scratch instead of nabbing the numbers from other sources since you seem way more knowledeable than them
The stacked books don’t really store any unique info, the only extra data you get is the stack count, but you can give the book a title and an author for a little extra data...
You can also rename the chests, minecart chests, and shulker boxes.
The video is full of mistakes. In 2:50 he says that a chest is 1728 bits by counting that a stack is 64 bits, but in reality a stack can't store 64 bits, only 6 bits (log2(64)) + the info that you can get from the type of block. This also translates into the book part, because he is asuming that you can have a stack of 16 books where each book has different content.
@@cee_yarr and you can dye the shulkers ☝️
You can store utf-8 in books, so you can multiply every number by 4
They call it prefix, cause it actually prefix the unit word. "kilo-meter", "kilo-meter", "kilo-[unit]"
You forgot the infenet dimensions April fool's update
Deep lore.
"infenet" 💀
And just think about all the millions of peoples other minecraft worlds that can hold just as much data...
Stacking books or shulkers doesn’t give you new information so any time you stack items its not actually adding new data, and putting multiple minecart chests per block sounds cool until you consider entity cramming. If you really wanted to make the biggest data storage there are a few things to change: 1 you cant stack anything because stacking items requires them to have the same nbt data which means you cant have two different items stacked together like two books with different laters in them. 2 you should name each book to give it a few extra digits of data. 3 instead of just putting shulkers in chests, you can put actually copy a chests nbt data to put that chest in another chest and so on ten times recursively. 4 bundles could be ised to stack items with different nbt data so that could drastically increase storage in each layer. 5 now you can come back to minecarts, put the most recursively containing chest in bundles in the minecart chest 27 times to fill its inventory then copy the minecart chest 20 ish times per block to get to entity cramming. This assumes theres no hard cap in the form of an entire limit, which im not sure about, if there is then this wont work beyond adding just a few extra chests. Taking all these steps would change the calculations drastically meaning the final number is mostly very different than what you came to, id be very interested if you do a part two with these ideas.
so high quality for a smaller youtuber amazing job Zeppy
Don’t log out of that world, every chunk will revert. Also you would run out of unique books pretty fast
Whoops, turned the world into a chunkban
Ok but where's the scicraft level redstone contraption to read and write these bytes and the 16bit CPU to process it, a GPU and 16MB of RAM to run DOOM in Alpine in Minecraft?
Also the storage bus would be quite slow here. The higher storage capacity might not even be useable.
This is actually a real computer problem, when you hear L1, L2, or L3 cache, that's essentially RAM inside the CPU that's super fast, because using the RAM you put in the motherboard is too slow.
This feels stupid though so juat pull a Spu7nix and write a programming language to use a Minecraft world as a file system instead, things will definitely go well, trust me.
Anyways mega nerd out, this was fun, sub
1:03
WAS THAT THE BITE OF INFORMATION!!!????
For reference, if 1 bit was 1 atom, the observable universe would still not be enough to hold 1 devabyte
I FRICKING LOVE THAT SO MUCH OMW
You forgot the nether, end, and april fools exploration update
He did the nether and end didn't u watch the whole video?
imagine the ammount of data if he used the nbt data of chests so a chest filled of chests times 60 filled with shulkers filled with books
2:10 ackshwually
tl;dr it doesn't matter, the difference is insignificant anyway. All it does is confuse people.
You're wrong. It's 1024 (i don't get if this was a bit or not, if it was I laughed but I got confused when I tried to read it again)
Also 1000 and 1024 are both correct. They're just different ways of measurement.
1000 Megabytes(MB) is 1 Gigabyte(GB)
1024 Mebibytes(MiB) is 1 Gibibyte(GiB)
This is also why hard drives show up as lower than their rated spec in windows.
Windows uses gibibyte but calls it gigabyte. I don't know why, go ask microshit.
Hard Drive manufacturers use gigabyte.
Not to be rude but, Custom Dimensions.
everyone is talking about the bytes
but nobody is talking about the editing
The nether and end is actually smaller than the overworld as they dont have negative y coordinates and their hight limit is 255 blocks instead of the 319 blocks in the overworld.
the biggist chunk ban
The nether and end have a lower build limit, and the dont have negative
4:35 Stacking them only works if the stack contains the exact same data. This wouldn't increase anything.
I blame your sources tbh
minecraft has 3 worlds in vanilla, but 1 update has almost infinite so infinite data if you want
Too… much… MATH
You’re the next Mumbo Jumbo
16 book thing is wrong cause theres no point storing same information 16 times at best you can just get like extra bits from the amount of same book you have.
so after that point all numbers need to be multiplied by16 to be more accurate
Use Barrels for less lag
Imagine doing this in the portal april fools
You are actually not doing "1000 bytes = 1 kilobyte" wrong, it is true, however, 1024 bytes IS 1 Kib (kibibyte)
this is why when you buy hard drives that label themselves as "1 terabyte" are lower when you actually use them (931 "gigabytes")
Because the computer is using binary.
It goes from kibibyte to mebibyte to gebibyte to tebibyte.. etc.
-> the problem with size difference isn't "the computer is using binary" but "Windows refuses to use the standard definition of size"
@@stinkytoby ..probably because using binary is the most convenient
@@jacpa2011 no, you're already working with strings when you show the user, how you format it doesn't really change much.
They really just don't care enough and keep using the outdated terminology because not enough people care
@@stinkytoby yeah peoole dont care much xd
Bro never knew there was so much to this game😂😂
i feel like you would get book banned
Legendary channel
how much data would your pc need to store this minecraft world
but... cant you just place a shulker in a chest CTRL + MID CLICK and then put it in a shulker than CTRL + MID CLICK that shulker and put it in a new chest over and over?
Not in survival
Now download the cubic chunks mod for infinite world height💀
Only 4 bn iirc (uInt32 max)
@@mkDaniel"only"
you forgot about the 20w14infinite dimensions :D
nbt stacking.
1024 bytes ≠ 1 kilobyte
1024 bytes = 1 ki*bi*byte
kibi = KIlo + BInary = 2¹⁰
kibi mebi gibi tebi pebi etc.
Woah how did i find this vid god damnn
you didn try to use dev tag you would get more in one chest try it out dev limite should be 127 so try it out
Add the nethe the end and the mod that makes build limit higher
If you're going the mods route just add shulkers in shulkers, reinforced chests/shulkers and a stack mod.
One would like to know how much time was spent rendering in replaymod
only about 30 ish mins, it was more spent rendering the whole video
void of squares :)
WHY NOT CRTL MIDDLE CLICK TO BE SMALLER
fun fact, the first version of cave game took *6 minutes* to code
I thought it was 6 days? You probably cant write that much code in 6 minutes
It's 6 days 😡
um actually, its not 1000 bytes OR 1028 bytes, its 1024 since that's 2^10
so i can store inf data in 1 block?
basically
your keyboard looks filthy
nuh.
Here before it blew up
16:33 What about every seed?
hi zeppy
You can compress the data even further, by having the minecraft instances stored in the books uncompress to minecraft worlds filled with chests filled with shulkers filled with books.
e
You forgor the end plus nether
U did not watch full vid
@@hazardssb2 i did
@@hazardssb2 probobly just missed it
@@hazardssb2 you only did overworld from what i remember
One character can use more than 8 bits when it's uses strange characters like: ᾠ
Forgot to shoutout the current members so I'll do that now
CURRENT MEMBERS:
Big thanks to; @Twistee @ThatWannabeNerd @YourLocalAronist
Very Nice
💚⛏️🤎