This issue still occurs on 1.20.15
This issue is still happening in 1.20.15
This issue is affecting a lot of packs in 1.20.15
Hello,
This issue mostly only happens on Realms. Occasionally on local worlds, when you exit out of the world and then rejoin, some of the flowers/crops will have turned their respective blocks into dirt, but not all of them do that nor does it happen over time like it does in a Realm.
Hey, this isn't anything to add on to this, as this is kind of a bug, but I just wanted to say there is a way to get Realms to register the changes. Usually, if you increment the version in the Manifest up, it'll register the changes. If that doesn't work, you can always change the UUID of the pack, which will then get Realms to see it as a different pack with the changes you made.
This still hasn't been fixed in 1.20.10. Is there anyone actually working to fix this issue? It's a pretty big and annoying issue. I should not have to redo my settings every other time I hop onto my Realm. It's very disappointing to see how long this bug has persisted. (Over a year now...)
Upon further questioning, it seems as if most of the time, the issue is caused by some form of addons or experimental toggles being on the world or Realm. It can still happen otherwise, but the most common way for it to happen is with addons.
A kind person has created a fix for this issue with this resource pack, so while we are waiting for this issue to be fixed, feel free to use these.
Multiple people I know are having the same issue. It seems to occur anywhere. People have had it occur in Realms and in personal worlds, with or without addons. Clicking the Let's Go button gets rid of the HUD, or does nothing. Turning on Hide HUD in the settings gets rid of the popup, but it also hides the rest of the HUD as intended. Here are some pictures of people having the problem.
Platforms it has been occurring on: Windows 11, iOS, PS4, PS5, probably more? Those are the only ones I have been specifically given.
Of course! Apologies for the delay on getting back to you. I will record the issue occurring in a few hours, assuming it is still occurring on 1.20.30.