mojira.dev

Eiim

Assigned

No issues.

Reported

MC-272615 Beehives and Bee Nests destroyed by end platform don't release bees Community Consensus MC-127430 Waterlogged blocks let more light through than water Duplicate MC-127229 Nether lava oceans generate over ravines Awaiting Response MC-127141 Waterlogged blocks do not allow for bubbles Invalid MC-127120 Items move incredibly fast in water flows Confirmed MC-127102 Rising in waterlogged blocks is faster than climbing ladders Confirmed MC-109084 Redstone dust not powered/unpowered until updated Duplicate

Comments

The reason for this is that all non-air blocks are valid supporting blocks from below for carpet/moss carpet/pale moss carpet. You can place a pale moss carpet above water, for example. Therefore, when the water replaces the lower block, the upper block still sees a non-air block beneath it and it isn't in an invalid state. Possibly, pale moss carpet with bottom=false should use the isOf(this) condition, like doors.

Ore distribution changed massively in 1.18. Emerald Ore can now generate from y=-16 with no height limit. As such, this ticket is invalid.

The video appears to be modded. Please verify if you can reproduce without mods.

@jacelleo I do know that this ticket specifies Bedrock, but the issue also affects Java and I know of no separate ticket for it, in this project or in the MC one. I asked on the Mojira Discord on May 12 for JE to be added to this ticket. Violine said that it should be in the MC project because it is client-side, I provided evidence that it was at least an issue with the JE Realms API (I directly queried that API through an external script and found the same results), and no mod has responded since, despite a couple others chiming in to say they have the same issue on JE.

This is not fixed for me in Java Edition.

The emoji provided is an interesting one, as it consists of somewhere between 1 and 4 codepoints. The possible codepoints included are: 

I would guess that you are copying two of these, it is being interpreted as two codepoints but one character due to Unicode combining, and somewhere in the code it sees two codepoints and looks for the second character. Just my analysis purely from the crash report, hard to tell w/o code analysis or trying out some things in-game.

Wait a while and it will reappear. It takes a ridiculously long time, however.

1.13-style command format is: /summon minecraft:item ~ ~1 ~-0.6249 {Item:{id:"stone",Count:1b}}

This is the bug tracker, please suggest features on the [Minecraft Suggestions subreddit|reddit.com/r/minecraftsuggestions]. Additionally, I don't know if this would help your problem, but the keys can be changed in the Controls menu.

Bug was fixed, reverting it would be a suggestion. Please put suggestions on the Minecraft Suggestions subreddit.

I've had this issue on Win10, and it's always been a system screen setup issue.

No crash, just extreme resource usage and lag that can crash less-than-powerful computers. Kinda like summoning 1000 items would.

I think this is a duplicate of the "relates to" link, but with more information.

For me, the screen just turns completely black :/