Unusual Old Minecraft BUGS Mojang Still Hasn't Fixed...

Make sure to subscribe :) Join my discord - discord.gg/WGc9UNM

1:55 is actually really well known if you play multiplayer. The player who gets aggro keeps the aggro for the mob, even when you attack(ed) the mob. I don't know if this was changed/fixed, but a common strategy early on would be that one player charges in to do a hit and the other then kills the creepers etc.

The F4 key was used to disable "Super Secret Settings". I guess that hotkeys was never deleted in the code to allow this toggle option of the spectator view.

4:14 I wonder how many other bugs existed since 1.3 from the singleplayer-multiplayer merge, I know the damage tilt was one that was broken from this for years that they only recently fixed

Lever mining speed is such an oddity. I noticed it many times over the years, but never considered it a bug - I always reasoned that it was intentional since an active lever supplies a constant redstone signal and breaking it accidentally could trigger a redstone mechanism.

5:34 this one is not a bug. It is a necessary quirk, as the allows forest to be grown. If this were not the case, trees could never be grown near each other, as the leaves on any tree that attempts to grow must have at least a 1-block gap from between any leaves and any preexisting block on the same y-level as the leaf. In order to make the game work in an expected way and seni-realistic way, particularly for Acacia and large oak trees, this has to account for logs. As far as the leaves go, they need to be able to not get the tree growth canceled due to overlapping things like tall grass, ferns, extra-long grass, large ferns, and other leaves. In fact, them not doing this with snow layers is arguably a bug, or at least an issue, as snow layers that generate from snow on top of trees in snowy biomes can make you unable to plant trees near each other very often if there has ever been rain/snow while the area was loaded.

10:41 as far as i remember f4 was used to toggle or do something with super secret shaders, those shaders being available in the setting themselves, probably being why it toggles them

Is the lava one not just the lava causing the block to drop as an item - the same as water, but the item being destroyed by the lava on the same tick? That's the same sound effect for when an item is destroyed by lava. Also, why would water create a sound or smoke effect? It's not destroying anything, just moving it.

10:04 I've posted a related bug WAY back, arrows fired from a dispenser do not reflect ghast fireballs. The reason is, all the projectile knockback is derived from the rotation of the entity firing the entity, but since in the case of the dispenser there is no entity shooting the arrows, no knockback is applied and therefore the fireballs do not reflect. Also makes for some interesting cases where you can shoot at a ghast fireball and then turn 180 degrees to hit yourself with the fireball that you shot at.

The tick advance thing is quite useful in time travel/glitched speedrun, as you can utilize it to perform tick perfect strats.

I know why the beacon bug happens, it's because of re-applying regen every couple of seconds. Regen seemingly heals based on the remaining ticks of the effect, so reapplying it frequently can increase or decrease the regen rate. Same also applies to poison and wither dealing damage.

The bug at 4:12 with the nether and end portal text just saying 'loading terrain' could be because servers often use portals in hubs to bring people places. Intentional or not I think it is better this way.

8:34 - I think the chunk is still loaded after you die because of the death screen while you are AFK, not because of the bug. The bug is about entities still being visible (or loaded) at the client side even after they despawned at the server side.

Just so you know, In the lava sound bug (7:28) the lava burns the items and that is where the sound comes from. If it didn't destroy the block, then it would not make that sound. So because water doesn't entirely destroy they items that it hits, it therefore doesn't make that sound. This is not a bug just a feature. A good example of this is when you drop anything made of netherite it will not burn and doesn't make that sound. Also that particle that appears is the smoke particle (The campfire smoke has a different particle) is because the item is burned.

Discovering these bugs, and trying to base contraptions around them is my favourite part of redstone :) Never gets old, and you always learn new things.

In the final bug, f4 disables the effect because it is the button to disable overlays, such as the hotbar, potion effect TOAST boxes, and screen filters(including the now removed Super Secret Shaders, the Spectator shaders(remnants of the Super Secret Shaders), the spyglass border, the f3/debug screen, and the carved pumpkin mask. The fact it doesn't go away is a bug though, but that is why f4 would do that.

1:41 I've come across that bug in real life. Got so focused on what I can't do that I didn't do the easier alternative. Hope mojang and god coordinate on fixing it

7:02 actually came across this one fairly often. it also works if you stay in adventure mode, have a tool which can break a certain block, i.e. an iron pickaxe which can break diamond ore, but then have the ore be immediately replaced by another solid block, i.e. stone, immediately after it is destroyed. the breaking animation will continue to play in adventure mode, even when using a tool that does not have the explicit ability to break said block.

i have occasionally gotten that block breaking animation bug by simply moving away from the block while i was breaking it, usually by falling

6:25 this is because the torch's "correct mining tool" is an axe, if I'm not misremembering