Minecraft as a game is nearly 12 and a half
years old. If it were a person, it would almost be a
teenager now... I feel attacked. Given how long Minecraft has been around,
it should come as no surprise that the game hasn't always been the most stable. I'm looking at you Minecraft 1.14. Java Edition has seen the release of nearly
900 updates, including snapshots, and in almost every instance, dozens of issues get addressed. Of the nearly 41,000 reported issues for Minecraft
Java Edition via Mojang's current bug reporting service, only about 1 to 3 percent of them
are valid, non-duplicate crash reports. And most of those crashes either can't be
reproduced, just aren't interesting enough, like Llamas with a strength value of 0 crashing
the game, or are just plain dumb. One example being that Minecraft crashes if
you throw a custom fireball with an absurdly high explosion power. Like, if you intentionally overwhelm the game
far past the point of sanity, yeah, it's gonna crash. However, of the roughly 700 unique and valid
crash reports that I investigated, I believe I've found a list of 50 that are absolutely
worth their own video. My only requirement is that the game must
crash for a specific reason, and in one form or another, the items have to be funny, or
at the very least, interesting. On the top of the screen will be an ID for
that crashes bug report. If you want to know more information about
any one of these items, like which versions these crashes used to occur in, just give
that ID a Google search. Don't try any of these glitches on worlds
that you care about, as many, if not most of them render the worlds they occur in inoperable. If you enjoy the video, please consider subscribing
for more. With all of that out of the way, let's check
out 50 ways that Minecraft used to crash in past versions of Minecraft. Today's video is brought to you by MCProHosting. Check out any one of MCProHosting's "One"
plans, which allow for you to pay for one server, but swap between any compatible game
of your choosing, on the fly, without having to pay for multiple servers. They have all kinds of plans to suit your
needs, they also allow for you to host a Minecraft server that both Java Edition and Bedrock
Edition players can play on at the same time, and you can get 25% off your first order with
the link in the description down below. Okay, here we go. Number 1. The biggest Nether Portal you can craft in
Survival Minecraft puts the obsidian frame at 23 blocks wide, 23 blocks tall. However, using the fill command, you can make
portals even bigger than that. For a little while before 1.16 was released,
Making a portal bigger than 32 by 48 could crash the game, with the likelihood of a crash
increasing as the portal got bigger. Number 2. Casting a fishing rod into a nether portal
and reeling it in. Number 3. Some of the crashes on this list relate to
a change in 1.13 called "The Flattening", where among other things, numeric item ID's
were properly removed from the game. And in one of those versions, having a Skeleton
kill a creeper, which is required for most music discs in the game, instead of potentially
getting the best music disc in the game, Minecraft would instead crash. Number 4. Feeding a dolphin in Minecraft causes it to
lead you to treasure. But for quite a while, feeding a dolphin on
a world where structures are disabled, the internal server would crash, as the dolphin
would have no where to take you to, and a check had not yet been implemented to handle
this situation... Number 5. Having a bee sting you while your 3d model
is loaded, either by opening your inventory or playing in third person view, the game
would crash. This is gonna take a while, so let's speed
things up. Number 6. Creating a spawner Minecart that spawns spiders
would crash the game as soon as a spider jockey, aka, a skeleton riding a spider, would spawn. Number 7. While you can right click on spawner cages
with any spawn egg to change what mob appears, at one point in time, right clicking on the
cage with a slime or a magma cube egg would cause the game to immediately crash when attempting
to render the mob inside the cage. Number 8. At a much earlier point in time, putting a
default spawn egg into a spawner, obtainable by just giving yourself a spawner egg without
any NBT information, would also crash the game. Number 9. While glitches like this are a little bit
silly, this is my video. My rules. Using commands, you can spawn any mob stacked
on top of any other mob. But during a few snapshots, spawning in mobs
with a slime or magma cube riding them would cause a crash. Number 10. During about the same period of time, summoning
a skeleton riding a parrot or a turtle would result in the game crashing after a short
period of time. Number 11. When WolfieMario reported this bug, they provided
a schematic file for it, allowing me to use MCEdit to import it into a world, so thanks. For just under 3 years, creating a spawner
cage that spawned paintings would cause the game to immediately crash upon loading the
world. Number 12. This one was referred to me by HalfofAKebab,
one of the founders of Omniarchive. In the first iteration of Minecraft Beta 1.7,
right clicking on a sheep... was enough to crash the game, probably because this was
the first version to implement shears. Number 13. Binding the sneak key to any mouse button
and then mounting the entity would crash the game, probably because the message telling
you what button to press to get off the mob wasn't set up to handle mouse buttons yet. Number 14. Dropping an anvil onto powered redstone. Number 15. Putting any item with NBT information into
an anvil, which could easily be done by control picking a chest, and then attempting to rename
it, would result in a crash. Number 16. When the piercing enchantment was first introduced,
shooting a player with a piercing crossbow while PVP was disabled would crash the server,
resulting in everyone on the server timing out after a short period of time. Number 17. Committing die with a bow an arrow, any form
of harming potion, or TNT would result in a crash. Number 18. Putting any record disc, not just the best
one, into a jukebox would result in absolutely everyone within range of the jukebox crashing. Number 19. Breaking a villagers point of interest on
the wrong tick, which could be done pretty easily by trapping a villager, followed by
placing and breaking a profession block cause the game to crash. Number 20. Minimizing the game when the server disconnect
window was displayed. Moving right along. Number 21. Using a colon within a command after a slash
or another colon. Number 22. Holding shift and pressing down without selecting
a server. 23. Having a scrollable server list, selecting
a server, holding shift, and moving it all around the list. It's inconsistent, but sometimes, when that
item reaches the bottom of the list, the game will just crash. 24. Entering just a colon into the multiplayer
direct connection menu, without any other characters present. 25. This is the only item on the list that I couldn't
personally replicate, and here's why. Having someone stay on a server for more than
24 hours would crash everyone on that server, since skins would only remain authenticated
for 24 hours. I can't replicate this one because Mojang
don't authenticate skins in Minecraft 1.7.7 anymore. They do in 1.7.6 and 1.7.8, but not 1.7.7. Interesting. Number 26, which lasted for over 4 years. Pressing an inventory manipulation key, like
Q or 1 through 9, and also pressing an item manipulation key at the same time within large
chests. If pressed at the exact same time, the game
would crash. Number 27. This one I just found online by searching
around, but in Beta 1.7, pressing a sticky piston into the same powered redstone line
that just powered it would result in the world crashing, followed by the game itself. Number 28. This one's tricky since this block disappears
after a few moments, but having a 2011 April Fools locked chest pushed into your head by
a piston resulted in a crash. 29. Speaking of block ID 95, giving yourself block
ID 55, 64, 71, or 95, which were the ID's for the block form of redstone wire, wooden
doors, iron doors, and the 2011 april fools locked chest specifically, you'd get a crash. And number 30, which is a tricky one. Having blocks drop invalid items, which was
doable in these versions by using a silk-touch pickaxe to break a lit redstone lamp would
not only result in a crash... but if you were unlucky, or if you paused the game on the
same tick that the block broke, the game would be unable to load that chunk upon re-entering
the world, which would result in the chunk getting deleted and re-generated. So. 30 down, 20 to go. While number 31 isn't strictly speaking a
crash, it might as well be considered one. If you have photosensitivity issues, turn
your head away for this item. In Minecraft Alpha 1.1.1, which only a handful
of people ever acquired when it was new, remained lost for nearly 10 years, and was only found
again recently, a video for which can be found here; depending on the GPU that you had, your
entire screen, not just Minecraft, would turn gray. On AMD GPU's, your Minecraft window would
begin flashing red. I wasn't able to replicate this bug personally,
because it just doesn't happen on my NVIDIA GPU. Number 32. Generating a super-flat world without any
information within the preset window would cause the game to crash once the world generation
window showed 100%. Number 33. Placing a snow layer on top of a fence gate. Number 34. Shift-right clicking on a shulker box while
holding bone meal. Number 35. Creating a super-flat world over 250 blocks
tall with structures enabled. 36. Creating a superflat world that includes the
"oceanmonument" tag within the preset. 37. Having a scaffolding block fall on top of
a shulker box. The moment that it lands on the shulker box,
the game would crash. 38. Having a hopper minecart fall into the void. The moment it's coordinates went negative,
the game would crash. 39. Placing a shulker box at coordinates 0x, 0y,
and 0z. Interesting. Number 40. This one was took a while to actually crash
the game, but spectating someone as they're either eating or blocking with a shield could
result in a crash. 10 more to go. 41. Spectating an entity that is submerged underwater. 42. Loading a map within an item-frame, while
no other player has that map within their inventory. Pretty interesting crash scenario, since it
can happen easily by placing a map within an item frame in survival mode. Though, it only existed for one snapshot. Number 43. Item-frames existing on walls... at all. Number 44. Flying straight up or straight down while
using a rip-tide trident, or by using an elytra with fireworks. The bug report said that this would crash
the game within the nether or the end, but I didn't observe that behavior. Either way, it boots you out of the world,
and will do so repeatedly upon re-entering the world for a while, so as far as I'm concerned,
that's a crash. Number 45. Teleporting to invalid coordinates, possible
in 19w13b by summoning an ender-dragon, which results in it's coordinates being "NaN", which
means "Not a number". Teleporting to NaN USED to be possible in
older versions of Minecraft, and resulted in some pretty interesting things, a video
for which you can find here. Number 46. This one is similar to before, but in a few
snapshots in 2013, you could actually just straight up teleport to NaN coordinates, which
would result in the game crashing. 47. Using relative coordinates with the spawnpoint
command to set your spawnpoint beyond 30,000,000 blocks. When you would respawn, the game wouldn't
outright crash... but your character would become stuck forever. Number 48. Again with the respawn command, but this time,
setting your spawnpoint anywhere, but with an angle so high that the game would interpret
that angle as NaN, which Minecraft allowed for you to do for a few versions. Upon respawning, the game would boot you off
the world, and render the world unplayable until fixed with external tools. 49. Summoning a falling sign block that has it's
text value set as null. And finally, number 50, which is the only
item that still works in modern versions of Minecraft, and probably always will, given
that it's an intentional debug feature. Holding F3+C will first copy your coordinates
to your computers clipboard, and then begin a timer that, at it's conclusion, will crash
the game...
