mojira.dev

Sachari

Assigned

No issues.

Reported

View all
MC-252886 Recovery compass spins around randomly when in an item frame Works As Intended MC-242557 Dripstone caves below y=0 do not generate copper ore Invalid MC-242073 Magma blocks can generate inside of icebergs Confirmed MC-240553 Birch forests generate in areas with high humidity Invalid MC-239274 Aquifers generate harsh edges along chunk borders Cannot Reproduce MC-238878 Floating giant mushroom on lava lake Duplicate MC-238853 Shallow aquifer lakes do not generate fish or seagrass Duplicate MC-238797 Oceans and rivers place an overabundance of grass along coasts Works As Intended MC-237449 Beaches generate within land biomes Duplicate MC-226683 Sugar cane and grass generate in Mushroom Fields biome Community Consensus

Comments

It would make more sense for it to not move at all, wouldn't it? Either way a confirmation from Mojang would be appreciated, hence why I created this ticket.

Rechecked, turns out this bug was fixed in 1.18 pre-6.

Please reopen, this happens in 1.18 pre-1

These are all brand new worlds

I updated the description (thanks Avoma) and added quite a few new photos

The existing code that gives the block an age needs to be fixed, which is what CalXee is reporting, Star. We acknowledge that the code works, but it does not work in an efficient way.

I don't think this is intentional because I can't see my player icon if the X overlaps it.

Unable to reproduce in 1.17.1, looks like this might have been patched?

I can confirm this, the arms do not go down even if you are an obscene distance away.

That must've been a mistake on my end, sorry about that, it is still fixed in the final release.

This was fixed in 1.17 pre-release 3

They did not generate there prior to 1.17, before they changed what could be placed, so it is likely that the natural generation of these on mycelium is unintentional.

Looks like they patched it

They're both cobble related blocks and the original one does not rotate while the new one does. If it is WAI, so be it, and I would like to see what the devs think of it.

This is fixed in 20w48a

Load more comments