Uploaded January 2023 | Updated September 2026, 2 weeks ago
I've been having A Time, and after some consideration I think I want to start uploading smaller videos here. I keep too much locked behind unlisted videos, private chats, and my brain(the least trustworthy!!), and that just feels unfair. But I suppose that should include publishing all my unlisted videos too, even if old stuff might be kinda wrong or cringe. So here you go ❤️ Smthn smthn growing as a person new year new me.
Original Title: I Put a Village in the Ground
Original Upload Date: Jun 21, 2019
Original Description: N/A
Notes:
This was just a video demonstrating an application of a glitch I had found back in probably 2016, way before I got involved with Minecraft Speedrunning. I don't remember the specifics(I guess that's why I'm making this channel), but all I really called it was the "Hardcore Mode Glitch."
From what I remember, back in the day the hardcore death screen had an option to "delete world." Contrary to what the name implies, it does not delete the world. In fact, it doesn't even properly close the world. So it boots you to the title screen, but keeps the world open. Normally the title screen would pause the world anyway, but you can stop this by opening the world to LAN before dying. You can then browse the title screen and world menus while the hardcore world is still ticking along. It should completely close if you try opening a new world, but this can be avoided as well. If you induce enough lag that you can load a new world in-between ticks(?), then it'll keep ticking even after you enter the new world. As you might be able to guess the implications of that are quite whimsical.
In this video, I used a side effect of this glitch to induce world corruption in the new world. And subsequently put a village in the ground. I don't fully understand this effect of the glitch either, but this is how you perform it/how I assume it works:
This actually doesn't require the immense lag, just opening to LAN and pressing the delete world button. After being booted to the title screen you can navigate to the world list and actually find that the hardcore world is still there. You can even select it and try deleting it again. Of course, it'll fail since the world is still open, but this does have the interesting effect of removing it from the world list. The world files are still there, they're just not listed in-game anymore. From there you just have to create a new world with the same name as the "deleted" world. Normally Minecraft would detect that there's already a world under that name and append a "-" to the file to prevent overwriting it. But, since it thinks the hardcore world is deleted, it doesn't bother. This means you're essentially overwriting the old world with a new world, causing some funky stuff. You don't need to use the same seed like I did, or even a seed at all, just the same name. Using the same seed makes it much more consistent though, since you can die and spawn in at the same coords. Very fun n easy way to do chunk corruption. Funnily enough I'm pretty sure this specific part of the hardcore glitch was fixed - not because they fixed the hardcore button - but seemingly because they switched to the (1)...(2) naming system instead of just adding "-"'s till the game crashed.
Anyway I thought this application of the glitch was interesting because of how villages generated with it. I'm not sure if this is specific to the glitch, or just chunk corruption in general, but either way. The village in the new world seems to generate over-top of the chunks from the hardcore world. In this case though the hardcore world had the exact same seed as the first world, just with a big hole at the village. This causes the new village to generate into the hole, thus "putting a village in the ground." Interestingly, this also appears to offset the spawnpoint of the world. Normally you would spawn in the village, but the new world spawns you way off at a different valid location since the normal one is well, a hole now. Also note that this would work without the hole as well. Instead of generating in a hole, the village would just generate overtop of the first village. You can kind of see that in this video around the hole, but I thought I would mention it because "village duping" is such a goofy concept. That's right baby you're looking at the world's first proud village duper.
I guess I'll also note that since I make the new world in hardcore as well, this can be repeated seemingly infinitely. Anyway I'm going to stop yapping I think this glitch is very funny and so did 13/14 year old me.
I've been having A Time, and after some consideration I think I want to start uploading smaller videos here. I keep too much locked behind unlisted videos, private chats, and my brain(the least trustworthy!!), and that just feels unfair. But I suppose that should include publishing all my unlisted videos too, even if old stuff might be kinda wrong or cringe. So here you go ❤️ Smthn smthn growing as a person new year new me.
Original Title: I Put a Village in the Ground
Original Upload Date: Jun 21, 2019
Original Description: N/A
Notes:
This was just a video demonstrating an application of a glitch I had found back in probably 2016, way before I got involved with Minecraft Speedrunning. I don't remember the specifics(I guess that's why I'm making this channel), but all I really called it was the "Hardcore Mode Glitch."
From what I remember, back in the day the hardcore death screen had an option to "delete world." Contrary to what the name implies, it does not delete the world. In fact, it doesn't even properly close the world. So it boots you to the title screen, but keeps the world open. Normally the title screen would pause the world anyway, but you can stop this by opening the world to LAN before dying. You can then browse the title screen and world menus while the hardcore world is still ticking along. It should completely close if you try opening a new world, but this can be avoided as well. If you induce enough lag that you can load a new world in-between ticks(?), then it'll keep ticking even after you enter the new world. As you might be able to guess the implications of that are quite whimsical.
In this video, I used a side effect of this glitch to induce world corruption in the new world. And subsequently put a village in the ground. I don't fully understand this effect of the glitch either, but this is how you perform it/how I assume it works:
This actually doesn't require the immense lag, just opening to LAN and pressing the delete world button. After being booted to the title screen you can navigate to the world list and actually find that the hardcore world is still there. You can even select it and try deleting it again. Of course, it'll fail since the world is still open, but this does have the interesting effect of removing it from the world list. The world files are still there, they're just not listed in-game anymore. From there you just have to create a new world with the same name as the "deleted" world. Normally Minecraft would detect that there's already a world under that name and append a "-" to the file to prevent overwriting it. But, since it thinks the hardcore world is deleted, it doesn't bother. This means you're essentially overwriting the old world with a new world, causing some funky stuff. You don't need to use the same seed like I did, or even a seed at all, just the same name. Using the same seed makes it much more consistent though, since you can die and spawn in at the same coords. Very fun n easy way to do chunk corruption. Funnily enough I'm pretty sure this specific part of the hardcore glitch was fixed - not because they fixed the hardcore button - but seemingly because they switched to the (1)...(2) naming system instead of just adding "-"'s till the game crashed.
Anyway I thought this application of the glitch was interesting because of how villages generated with it. I'm not sure if this is specific to the glitch, or just chunk corruption in general, but either way. The village in the new world seems to generate over-top of the chunks from the hardcore world. In this case though the hardcore world had the exact same seed as the first world, just with a big hole at the village. This causes the new village to generate into the hole, thus "putting a village in the ground." Interestingly, this also appears to offset the spawnpoint of the world. Normally you would spawn in the village, but the new world spawns you way off at a different valid location since the normal one is well, a hole now. Also note that this would work without the hole as well. Instead of generating in a hole, the village would just generate overtop of the first village. You can kind of see that in this video around the hole, but I thought I would mention it because "village duping" is such a goofy concept. That's right baby you're looking at the world's first proud village duper.
I guess I'll also note that since I make the new world in hardcore as well, this can be repeated seemingly infinitely. Anyway I'm going to stop yapping I think this glitch is very funny and so did 13/14 year old me.
