The Minecraft Code (2024) [video]

[picafrost]

Internet denizens love opening a locked box. This phenomenon has been weaponized by the gaming industry in the form of loot boxes.

[astrobe_]

It is strange to me that people obsess on programming in-game with "red stone" etc. That said I am dayjob programmer so the last thing I want to do on my free time and is to program stuff.

I made a game that uses the Luanti "voxel" engine (MC-likes games of course, but also transposition of other genres), and even programming that is bit of a chore but that's the price to pay to play the game you want to play (there's much more to that than just programming/modding; game design is a rabbit hole).

But I think that it would be more rewarding for those who are curious about programming to start modding, especially in Luanti because it is relatively well documented and it's Lua. In a way, making it rain with the programmable particle spawner the engine provides is a loot box locked by an API, with hints on how to open it in the docs ;-)

[boredpudding]

It's solved, full write-up here: https://www.reddit.com/r/MinecraftUnlimited/comments/1cvo5py...

Tl:dr; It was a release file for their Minecon event. It was never meant to be public. Obsessing over a password protected in a company's S3 bucket is weird and crosses many limits.

[djmips]

Telling people they should not try and crack something is kind of like the Streisand effect.

[cedws]

I disagree with this and what Dinnerbone says about locks. It doesn’t matter who file was intended for, it’s on the internet, if people want to use their silicon to do some mathematics to turn some numbers into some other numbers that’s their choice. It’s not equivalent to breaking into a house.

[snowram]

It is rather common in gaming to communities to find people completely obessed over ultra specific details of their favorite game. It isn't even the first time for Minecraft, see the "pack.png" case.

[esnard]

Weird. The file was cracked in May 2024, while the password had appeared in a database leak which was added in HIBP (and thus pretty much public) back in October 2017.

Unsure why it took the community so long to crack the file.

[de6u99er]

>He mentioned that he does not want people to nag him about it and that “It's brought up every single year, I'm hoping this is the last ”. Finally putting an end to a 13 year old mystery.

Ouch

[MortyWaves]

I see you haven’t stumbled across the Minecraft community much, because this weirdness is just every day for them.

Take for example, the infamous 2B2T Minecraft server.

Exploits and game breaking mechanics by virtually impossible to discover bugs, and the no rule against hacking and cheating, have led to things people didn’t think were even possible in Minecraft over the servers ~15 year history.

[charcircuit]

>is weird and crosses many limits.

It's similar in format to communities that obssess over "lost media." The inability to pirate or get access to something becomes an obsession. Even if the piece of media exists in an archive somewhere, that doesn't matter to them because it's about the fact that they themselves don't have access to it that has become the obsession.

[neuroelectron]

so weird. many limits.

09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

[aswip]

I guess only boxpig41 knows what else was protected that caused them to replace the file just to avoid the chance that the real password might get out and those might be unlocked, though at this point I’m assuming those encrypted files are gone or are no longer important.

[nurettin]

Minecraft (java edition) has been decompiled, modded with different launchers and recompiled since ages. The reason you need a "launcher" is because for some reason Minecraft's jar file doesn't have a way of downloading all the assets Minecraft needs in order to run.

[teekert]

Maybe add to title: “but is solved now”. Would have saved me some time thinking they might go somewhere.

[dang]

Hmm that was a tricky one. I, er, solved it by truncation - a surprisingly effective trick for titles.

Thanks for the heads-up!

[0x6c6f6c]

It was solved? They never decrypted the original file, only the decoy.