Explaining how this Minecraft world forgot its seed

On July 20th, 2024, speedrunner Couriway was working on his quest to complete Minecraft 100,000 times when his 3,606th world forgot its seed, resetting back to seed 0. Today we dive into the code to investigate how this happened and why it will never happen again. Couri reacted to this video! Check it out and an extended cut of his original live reactions:    • Couriway reacts to Seed 0   Footage from    • 100,000 No Reset Minecraft Speedrun Challe...   Corrections/Comments: pancakes104 on the Discord pointed out another reason this was able to happen: Minecraft tries to use a BufferedOutputStream to reduce how many times it writes to a file, but it mistakenly applies it after the GZIP compressor and not *before*. If this order was swapped, the entire file would be written in one big chunk, which would likely further reduce the chance of corruption like this happening! If the later 512-byte blocks went missing they could technically work for the "seed 0" part of the exploit, the player just wouldn't be (fully) reset like what happened to Couriway. 00:00 What Happened 01:38 Reaction 02:51 How it Happened 11:10 The Timeline 12:17 This Will Never Happen Again 13:18 Wrap-Up OST: https://i.qixils.dev/couriway_seed_0_... Feel free to react :) I stream Minecraft challenges on   / lexikiq   Get updates on progress and post meows on   / discord   I post thumbnails early on   / lexikiq