Can confirm in 1.20.4
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!
Hello Jess Edward,
The fix you have suggested is for a different error code, namely -805306369. This is error code 0. I am also affected by this Error Code 0 bug, MCL-20783, and have tried these solutions which do not work for this bug. I do not have any of the named software which could interfere, and do not use 'Discord overlay'. Unfortunately I do not know if there is a fix discovered for this Error Code 0 bug, but thanks for trying to help anyway.
Ed Alaya, your problem seems to be different than the rest of ours; you can at least open Minecraft but cannot open any worlds, while we cannot open Minecraft full stop, the launcher preventing so. While your problem is also very severe, for all we know it may have a different cause. Still good to bring it here, but just wanted to point out to everyone that it may actually be an unrelated issue which also has to be fixed too. It's a shame your bug was marked as resolved, best of luck to you too that your issue will be fixed.
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.
I believe this issue is being tracked elsewhere too, and I think your input would be valued. I'll get back to you on the bug's number thing and link it here.
MCL-20783. If possible can you add your images there and perhaps vote for the issue? It appears to affect both Windows and Mac versions, but much more precise info is known for Mac. As you're on windows, your input would be appreciated!
I sure do hope this issue is high on Mojang's priority list, regardless of whether they can do anything about it yet. Alienating a probably large-ish portion of their audience and community is something I know they would never choose to intentionally do. I hope this is fixed soon.
Eugenio Scalfi, yes I can confirm this bug began in Pre-Release 2 for 1.18. I have done testing with different versions, and I agree it does appear to be a problem with the switch to Java 17, additionally and especially since a way Error Code 0 can be produced is with an outdated Java version. I believe some people have had this problem on Windows too maybe, but I cannot confirm. I too am on Mac OS X El Capitan 10.11.6.
Jess Edward, this does not duplicate that. This is exit code 0, not 11. May be a related issue, but not the same issue. Thanks for connecting the issues though as they are possibly related to one another with perhaps a common source of the problem.
Can confirm still occurs in 1.21. Also affects End biomes.