mojira.dev

LunizIsGlacey

Assigned

No issues.

Reported

MC-265802 Resource Pack Randomised Variants no longer functioning Invalid MC-254493 Tree Growth Blocked by Dirt Blocks Works As Intended MC-210759 Shipwreck found with two plank styles across chunk border. Duplicate MC-198067 Crouching does not work between cobble walls and fences Duplicate MC-192062 Previously redirected redstone dots revert into crosses Duplicate MC-179542 Basalt Delta Blocks Override Nether Bricks in Fortresses Fixed MC-179539 Nether music does not play in Nether biomes in customized worlds; instead, overworld music does Confirmed MC-178223 Baby Piglins take damage walking up staircases Duplicate MC-178113 Using a Playsound does not Override In-game Music Invalid

Comments

Can confirm still occurs in 1.21. Also affects End biomes.

Might like to add that interactions with decorated pots, despite displaying an animation, do not cause observer updates. This is in the same category as opening/closing chests as this is not a blockstate change but intuitively should cause a detectable update.

@Dhranios

Thank you, I probably should have checked that. Turns out that the formatting may have just been made stricter, rather than changed, so this bug report is probably invalid. Are you aware of how to delete a bug report?

As opposed to the cases of chorus and pointed dripstone, this one might be fine to leave in. One important use of this new decorated pot feature would be for adventure maps, which allow players to break decorated pots to obtain items. After all, this was most of the reason why this feature was suggested. Furthermore, as opposed to most other containers, such as chests, this is the only way to obtain the items in decorated pots. 

Powering the rail in that manner goes against how redstone works in all other situations. Fixing this bug would lead to the creation of a "special case" scenario which may unnecessarily complicate redstone.

On the other hand, intuitively the detector rail should power the powered rail that it is connected to, and so it is worth thinking about.

A solution to this bug may be to allow sloped activated detector rails to not only power the block they are placed on top of (as they do currently), but also the block they lean against; essentially like two levers within the same block space. This is an intuitive solution and would also make sense within the context of redstone as a whole. It would also mean that the same detector rail would also power, for example, a redstone lamp placed on top of the block it is leaning on.

Can confirm it still occurs in 1.20.2.

As for resource packs, that is intended behaviour. The sound engine is reloaded because resource packs can also affect or change the music and sounds which are played in-game. As for the other two though?

Thank you for the speedy response, Mark Derickson! That's a shame if this could be intended behaviour, I found it a useful mechanic in older versions for collecting saplings and creating canopies. Nevertheless, I understand if the developers ultimately decide this is working as intended. 

I think this is probably a hardware issue rather than an issue with Minecraft.

This is probably because frogs and tadpoles are separate mobs, unlike other baby animals... I wonder whether a similar issue occurs with other mob conversions, such as zombie villager curing? If not, then perhaps a similar solution could be taken. But if so too, then this issue could be more widespread.

@Tail, I think you've misunderstood the issue. The issue is that many common Mac systems cannot upgrade past incompatible operating system versions, not that we don't know how.

Just writing here to say that much info relevant to MCL-20783 is relevant here, and so if a bug is trying to be fixed, both should be taken into account. I used to have so much faith in Mojang, and I still do (you can fix this, I hope!) but with every passing month since PR-2 and every snapshot or release for 1.18 or 1.19 which doesn't address the issue, my faith is falling away. For me and for many others, Minecraft is our favourite game we've ever played, and yet we, passionate members of the community, are being left in the dark. If it's possible, a 1.18 using Java 16 even if it is laggy would be better, or for others who play Realms (I don't, but others do) to still be able to access such services in 1.17 would be preferable. I sure hope that even if it isn't fixed soon, we are given more information about it. Just a simple "We're working on it!" or "There's nothing we can do..." or some roundabout way as porting some generation or bug fixes to a 1.17 version, just anything to give closure or hope. Please Mojang. You can do this!

I cannot confirm or deny this occuring in any 1.18 versions due to my computer being affected by MCL-20783. Can anyone else test it in a 1.18 version?

 

Edit: I am now on a new device, and so can test current versions again.

Just checked, Minecraft and the account still works on Lunar Client, therefore the only problem is with the launcher itself, not with accounts or running Minecraft. An auto-update for the launcher was just released, so I shall check whether that fixes the issue (at least for me).

Edit: For me, the newest launcher update fixes the issue! You all should try check to see if it fixes the issue for you too. If there are still people unable to access the launcher for whatever reason, this issue should remain reopened and of a high priority, but hopefully it fixes it for all.

I'm having this problem too, also on Mac as many others are. Microsoft account did work yesterday, however today it has ceased to allow me to log in. As opposed to some other people here who made their account originally as a Microsoft account, mine was only migrated a few weeks ago. Therefore this appears to be affecting if not all but at least some users of a Microsoft account (either originally made that way or migrated) when on a Mac system. Please look into this! It renders many players unable to access their accounts.

Can you elaborate on the problem? Or send screenshots with the F3 menu open and the result of /seed shown?

There are two examples I have found too:

 

seed -5585680237520386540 at coordinates -4330 ~ -9020

seed -1699185818991075921 at coordinates -4060 ~ 4540

Seems like a problem with lag, not with Minecraft.

I don't think ghasts are undead, isn't this intentional?