mojira.dev

MisteryGates

Assigned

No issues.

Reported

MC-276001 Observers don't detect redstone dust changes Duplicate MC-275397 Redstone dust doesn't update properly Fixed MC-273328 Stars are smaller than supposed to Fixed MC-270826 Simulation distance is improperly saved Duplicate MC-265797 Furnace doesn't store initial burn time. Duplicate MC-263969 Narrator generates lag spikes Confirmed MC-257685 Canceling server encrypting can cause the game to crash Invalid MC-255388 Monster hunter and Monsters hunted advancement does not include the Warden Duplicate MC-248866 Grass block and dirt have different rules for fog Duplicate MC-241592 Trees can be cut off at new chunk boundries when upgrading a world to caves and cliffs world generation Community Consensus MC-241222 Mineshafts generate twice when updating from 1.17 to 1.18 Duplicate MC-239969 Mojang accidentally removed chunck blending for trees. Duplicate MC-239111 Phantoms keep getting stuck on walls Duplicate MC-220196 Relogging resets mob's attack cooldown. Duplicate MC-219508 Sound still plays when source is removed Duplicate MC-216658 You can take over buff effects from exploded creeper. Duplicate MC-216538 Placing blocks on OP only area causes inventory desync. Duplicate MC-215618 Hold F3 + C to crash the game Invalid MC-211931 Cursed fullscreen when loading Incomplete MC-202884 Mob drops before death animation Duplicate

Comments

Thanks Avoma for updating the resolution. It could have been helpful if people can do it themself.

I discovered that adding a piston on top of the powered redstone dust does fix it, but then the randomness of redstone plays a role due to the timing of my door. Sometimes it works, sometimes it doesn't. It bothers me a lot.

Although that is an easy fix, it is not intended behaviour. People using this circuit or similar circuits might not have the extra space available in their contraption to update that redstone dust.

This looks to me to work as intended.

Can confirm for 1.21. The famous Vanilla Tweaks team had trouble updating their datapacks because of this bug. I hope it will be looked at in the future.

This is intentional. However, it is supposed to check if you already have a milk bucket in your inventory. So it should only give one bucket.

I hope this bug gets fixed soon. I'm running a server that I'm planning to update to 1.21 as soon as it is released. It has a tunnelbore that is very well measured on the edge of my simulation distance (12 chunks).

Fair. I think the search bar needs some improvements because I did search for a similar bug and couldn't find it. So I assumed I was the first one discovering it.

This bug is the cause of a bug in my mod: Changing the spawnpoint to the nether makes beds not skip the day in the overworld.

I want this bug to be fixed within 3.5 years so my mod is not gonna suffer for this.

This works the same for any fog in the game and the reason for this is simple. The fog is calculated from the pre-projection position of the game. If they spend time fixing this bug, it means they have to rewrite the entire fog system.

When I looked for any duplicates I searched for the word "furnace" and it only gave me bugs where the title starts with that word. That is not the case on MC-10025. I knew that this bug might have affected older versions. Even older than 1.4.7. It takes a minor code change to get rid of this bug. So why is it still not fixed.

I discovered this bug when I was working on a mod that uses this narrator to warn the player when he is in danger. It doesn't really help when you are getting a lag spike. I think the problem has something to do with multi threading.

I agree that the bug is not very clear when I describe it with just text. I had some issues with my OBS installation which is why I didn't include a video in the first place.

Can confirm on 1.20. I wrote a mod that fixes this bug.

Can confirm for 1.20. My friend asked me to make a mod that fixes this bug specificly.

It is indeed not a bug if it was caused by me doing something wrong. I would say the fact that it gets stuck on Encrypting might be a problem caused by me. But I guess the Cancel button guarantees a crash, which is in fact a bug.

Can confirm. I discovered this when I was developing a mod and wanted to check for a mistake in my custom models.

I agree that this is a duplicate, but that bug does not include the Monsters hunted advancement. Only the Monster hunter advancement.

Can confirm. This also applies to the Monsters hunted advancement.

I played with autojump for a long time. I can't believe I didn't notice this bug.

The commands that you use to reproduce this bug are unreal to be used by a player.