Yes. Please fix lol
Can confirm it is also broken in 1.21.2 (I haven't updated on my phone yet because I just got back from a trip). Behaves the same way on my phone in 1.21.2 as it does in 1.21.21 on my laptop.
So basically realms is likely the full problem, I don't know how relevant the prior version before everything broke is but I guess this could be helpful.
This has always been how it has worked, I've been playing for about five years and experienced it almost every time I loaded a bonus chest...
They probably have gamerscore in another game. 0/2930 is for just Minecraft on that particular platform. You can earn Minecraft achievements and gamerscore for every platform the game is on
Slight workaround that is also a bug... but if you drown a zombie or husk you can get it to drop its items, including whatever it spawned with (which includes trial chamber armor lol)
Hope this helps someone
Can confirm there is an issue in which you can break structure void blocks in survival mode in the latest version
Would I support this being reopened, or make my own report?
I'd also say that they should add a toggle to go back to the old version of the controls anyways. I like to play with my controls invisible (meaning muscle memory has been a big factor in gameplay) and I think we can all agree that learning a new, more buggy control system is not going to fly with some people. I could barely play at the time of the update and I feel lucky that they didn't just put the new buttons as retextured versions of the old ones.
Plus, I now have to redo the resource packs. (That's a me problem, we don't worry about that) :/
Works when you go into the settings while a world is loaded.
Never remember them mentioning in the changelog adding a self destruct button being into the settings...
I'm having lag issues in both normal survival worlds and superflat. On my survival world, the area I've experienced lag in has an iron farm with 20 villagers as well as a pumpkin and melon farm that includes a total of 16 hopper minecarts. These are all located in the same chunk as well.
My phone runs Android 10 with a snapdragon 675 processor and 4 gigabytes of ram, and I've had it for 3 years now. I want to also mention that I've been using a render distance that is double what the game would allow me to do normally through methods I will not go into because I don't want it to get fixed. I would say that it is completely unrelated because I've been using that since 1.18.
Affects 1.20.30
Affects latest version - This is going to be much more annoying because I see a lot of people rushing to build trading halls after the changes made in 1.20.30.20...
Using this comment to continue to add affected versions until Mojang can answer my question. (Do y'all have an actual reason to resolve this? - And no, a developer resolving the Java equivalent without context doesn't count because in my opinion for a bug like this that's just lazy.)
I'm probably going to start updating this again soon, seeing that you guys can't seem to give me a good reason why we can't fix this...
1.20.0.24 Preview, 1.19.83 Hotfix, 1.20.0.25 Preview, 1.20.10.20 Preview, 1.20.10.21 Preview, 1.20.0, 1.20.10.23 Preview, 1.20.1, 1.20.10, 1.20.12, 1.12.13, 1.20.14, 1.20.15, 1.20.30, 1.20.31, 1.20.32
Affects 1.20.0.24. May dedicate a comment to affected versions for documentation purposes.
Also, could a developer answer the question in the previous comment when you get a chance.
I've asked this question a few times (On the other bug report and r/mojira) and still haven't gotten an answer: Is there a good reason to resolve this as "Works as Intended?"
All I've heard is that it's been resolved by developers (On Java Edition) and the pixels are still in the same color palette. That's it. Nothing actually reasonable. Plus, it probably wouldn't take 5 minutes just to fix this.
Once AGAIN:
It affects tiling with all other planks.
They have fixed similar issues before (MC-176832/MCPE-158025).
This is to do with colors of 4 pixels. That's not asking for much to be changed.
Affects 1.19.80 and 1.20.0.22.
The issues with the codes in the armor trim descriptions are in the base game as well. From now on, I won't mention it unless something changes.
Still an issue in the latest versions. [English US, but probably a bunch more]
Affects 1.19.80.23 - The color formatting issues that were discussed yesterday still persist.
Affects 1.19.80.22. The two codes have recently been implemented to be used with the descriptions of the new armor trims (§m for redstone and §n for copper). They work as these colors across the game in the latest preview. Could be a HUGE issue for parity if it makes it to 1.19.80.
As said it is still around as of the latest version. It produces a different issue with stone with the recent changes, making terrain look even more like a wasteland than before
[media]