mojira.dev

A Full Name

More than one avatar was detected! There might be multiple accounts sharing this same name.

Assigned

No issues.

Reported

MC-198706 Droppers don't work under certain weird circumstances Duplicate MC-188090 Rails try to connect to rails that they can't connect to, breaking existing connections Community Consensus MC-187993 nether portals not connecting correctly. Invalid MC-185910 The screen is jerky Invalid MC-134940 World Corruption (disappearing blocks) Cannot Reproduce MC-111740 Exiting a minecart sometimes glitches me through the floor Awaiting Response MC-111249 Being killed by a baby husk is not recorded correctly in the stats Cannot Reproduce MC-111247 Endermen become hostile when hit by the Enderdragon Duplicate MC-110011 Mobs behind me never make sounds Awaiting Response MC-52535 Water dispensers get stuck when powered by redstone directly on top of them Duplicate MC-52525 Sticky pistons won't pull dirt Duplicate MC-52513 Boats don't reliably activate wooden pressure plates Incomplete MC-52511 Left Shift in a minecart is glitchy, dumps me down a hole Duplicate MC-26802 Boats are worthless unsteerable garbage Duplicate MC-7038 Glitchy Witches Incomplete

Comments

This is happening in 1.15.2.

Since when can fences burn? Also, aren't the wood blocks at a blacksmith supposed to be too far away for the lava to set them on fire? Did they increase the distance that lava can set things on fire from?

(I guess I'm not sure they aren't burning, since there is lava near both places, and all missing blocks were wood or wood fence.)

Well, I attached the crash report. When I pressed F3+C I was standing in a tunnel, at the place where the fences disappeared.

This is not a duplicate of MC-85100 Enderman Getting Angry At Dragon, because it makes the Endermen hostile TO ME. Endermen that I have never attacked or looked at will attack me after taking damage from the Enderdragon.

This bug still exists. In 1.10 and 1.11, shields block all damage to you from both melee and ranged attacks, but still don't block any damage to your armor.

This also happens in PC Minecraft (version 1.11) and the framerate stays at 1 FPS forever because the time between shots is shorter than the time that the lingering stuff lasts. It makes The End unplayable.

Cartographers are white like librarians. The green guys are village idiots or something like that.

OK, you're right. But it's really weird though because my computer has always had 2.1 speakers, not surround sound, and I never changed the settings, nor allowed anyone else to use my computer. It should have defaulted to the correct setting when I installed the drivers, but somehow it was on the 4 speakers setting.

I'm having a similar problem, but in a slightly different situation. If I'm inside a building with stone walls and a roof made of slabs, and no light sources inside, there is a little bit of light at the top of each wall. The slab roof covers the walls, so there is no "crack" for light to seep in through.
This only happens when the roof is made of slabs and only with Smooth Lighting turned on.
It still happens if I extend the walls upwards.
But it doesn't happen if I replace slabs near the edges with stone blocks.
Cross sectional view:
1234567 (roof)
#_____# (walls and empty space)
If blocks 2 and 6 are slabs, light leaks in. If they are stone blocks, light does not leak. The other numbered blocks don't matter; they can be either slabs or full blocks. Blocks 1 and 7 can even be air without changing the result.

This bug has been in Minecraft since about BETA 1.6 or 1.7, I think, and was reported way back then. And it's deadly with only a few seconds of riding in a boat. I'm not sure how long exactly, but it's definitely less than 10 seconds. I think this bug is a side effect of very crude, lazy fix for a bug that made you immune to fall damage while in a boat. That bug was exploitable, but was almost never exploited because it was so useless. I've never been in a situation where exploiting the fall damage immunity bug with a boat would have worked better than just going down a temporary waterfall.

This could be fixed by just bringing back the old fall damage immunity bug, but apparently Notch decided that it was more important to fix a very rarely (or maybe never) useful exploit than to fix an instant-kill bug that can only be completely avoided by NEVER using boats. You see, it happens with squid too, and those things are everywhere.

And this isn't the only bug that instantly kills you. Hardcore is unplayable with all the instant death bugs that Minecraft has.

If they merely appear to glitch through doors, then this actually duplicates MC-10, not MC-2025.

This is NOT a duplicate of MC-72. Many witch huts are duds due to being mostly or entirely on River biome. Witches can only spawn in a Swamp biome.
Here is a YouTube video that explains exactly where witches can spawn:
https://www.youtube.com/watch?v=KllWkdfOS3M
I have also seen a witch hut that NEVER spawns witches due to the entire interior being on River, so that only a small portion of a wall is on Swamp. Thus, modification of that hut would be necessary for witches to spawn there, and even then they'd be abnormally rare.
Witches are NOT normally rare. As long as you are about 24 blocks from a perfectly normal witch hut (one that is entirely on Swamp), witches will spawn more often than Endermen. (Not counting Endermen that spawn underground where you can't see them.)

If it is not a bug that witches can spawn only on Swamp, then it is a bug that a witch hut can be mostly on River.

I think that maybe the requirement to be on Swamp was intentional, but was intended only as a safeguard to prevent them from spawning like crazy everywhere in case something went wrong with the other spawn condition (that they must be in a hut). It was then assumed that the "only on swamp" condition would not matter because Swamp Huts are supposed to generate only in a Swamp. But this assumption is wrong because a hut can actually generate almost entirely on a River. I'd be interested to know whether my guess on this is correct.

OK, I attached the crash report. Though you didn't say whether I needed to be near the witch-infested cave, I went over there anyway, just in case. But I didn't go inside because the witches would probably just kill me right away.

It think it says "resolved" because they fixed it in a development snapshot version. But that really doesn't count if you ask me.

It's still there in 1.4.6.
And I wouldn't say that the fall distance accumulates very slowly. Just going far enough away from a cat to make it teleport to you is long enough to accumulate a fatal amount, so if a cat teleports underneath your boat, you will die for sure.

This is extremely easy to recreate, seeing as how it happens every single time. And it happens as soon as you run over the soul sand, not when you exit the boat. And it's not minor, seeing as how it INSTANTLY KILLS you. If it happens in Hardcore mode, that means you lose your world forever. And it's hard to avoid, because it also happens when you run over an animal. If you have a cat following you, and it falls far enough behind to teleport, it could teleport right underneath you, causing an unavoidable death.

What makes this even more aggravating is that this is a side effect of fixing the bug where boats protect you from fall damage. That exploit was extremely unlikely to ever be useful. I for one never used it because I have never been in a situation where it could be useful. Yet Notch considered it more important to fix that exploitable bug that doesn't matter than to fix this horrible bug that instantly kills you. They could fix this bug with no effort at all by simply bringing back the "no fall damage in boats" bug, and they SHOULD do that until they can figure out how to fix it without causing horrible bugs like this one.

This is horrible. I have designed several different railway stations that totally depend on double T-junctions to work correctly. I never got around to building any of them, and I guess I never will, because all of them are very tightly knit and intolerant of change. I can't fix them to work around this bug, so I'll have to discard them all and redesign from scratch.