It's been a while since I've first watched this vid, but I'm super glad the algorithm showed it to me again! Would you ever consider doing a redux of this now that the terrain/world generation is even more different than before? Also I miss ur content lmao, the pokemon design vids were always fun. Hope life is okay for ya!
I understand generation now but what i can't is how he put those different version which like only height maps then ore stage i mean how and why this is not a popular video. But extermely good video this is what i wondered from long ago You earned a sub.
This video was amazing, great way to illustrate what's going on behind the scenes. That said, there's still one big question I have unanswered: when does this happen? I mean, the world is procedurally generated, so I've always thought the biome of each coordinate (x, z) was calculated when needed (e.g. when (16, 16) is generated, a function calculates which biome corresponds to that block column). But the way you explained it, in which the world generates layers and zooms in these layers seem to contradict my belief. If, as you said, biomes are generated very small and at the end they are "zoomed in" to make big biomes... doesn't this mean that we actually generated a lot of data covering thousands of blocks when all we wanted was the biome at (16, 16)?
Good question! Each chunk is generated separately, and the generation process begins when you are a certain number of chunks away so that there are always more chunks in the distance as you walk around. As far as the “zooming”, that’s something that happens in the underlying noise function - the intermediate tiny biomes are never actually generated (unless you modify the code like I did). Because the underlying noise function is smooth, each piece can be generated independently and still fit together smoothly. There are a few instances where the order the chunks are generated actually can matter, but they are pretty rare
This is amazing! This summary helped me a lot in understanding the source code
It's been a while since I've first watched this vid, but I'm super glad the algorithm showed it to me again! Would you ever consider doing a redux of this now that the terrain/world generation is even more different than before?
Also I miss ur content lmao, the pokemon design vids were always fun. Hope life is okay for ya!
I understand generation now but what i can't is how he put those different version which like only height maps then ore stage i mean how and why this is not a popular video.
But extermely good video this is what i wondered from long ago
You earned a sub.
i enjoyed watching this video. upload more like it bro! these videos are just my type. will be watching your others
Love this video! The world you are in is very pretty
Interesting! I like these videos.
Loving the videos!
Please could somebody tell me, where the source code of the world generator is located in the minecraft folder/ jar ?
He: Explains about Minecraft generation...
My brain: **get ready to create your own**
This video was amazing, great way to illustrate what's going on behind the scenes.
That said, there's still one big question I have unanswered: when does this happen? I mean, the world is procedurally generated, so I've always thought the biome of each coordinate (x, z) was calculated when needed (e.g. when (16, 16) is generated, a function calculates which biome corresponds to that block column). But the way you explained it, in which the world generates layers and zooms in these layers seem to contradict my belief. If, as you said, biomes are generated very small and at the end they are "zoomed in" to make big biomes... doesn't this mean that we actually generated a lot of data covering thousands of blocks when all we wanted was the biome at (16, 16)?
Good question! Each chunk is generated separately, and the generation process begins when you are a certain number of chunks away so that there are always more chunks in the distance as you walk around. As far as the “zooming”, that’s something that happens in the underlying noise function - the intermediate tiny biomes are never actually generated (unless you modify the code like I did). Because the underlying noise function is smooth, each piece can be generated independently and still fit together smoothly. There are a few instances where the order the chunks are generated actually can matter, but they are pretty rare
Nice!
link minecraft plisss
sounds like a complicated pile of code