For commands, this behaviour is the only known way to flatten from JSON text components to plaintext, which also makes it the only known way to parse strings (by constructing flattened text and doing a binary search).
Hate to advocate for a bug, but a lot of stuff indirectly relies on this. It would be nice if this could be kept until some alternative (e.g: `/data ... append` working for strings) was available.
Here's a utilities library that makes extensive use of the trick, for reference: https://github.com/McTsts/Minecraft-String-Utilities
Didn't occur in 19w38b so I assumed it was caused by recent render changes and only searched recent bugs, but appears to have existed previously. Duplicate of: https://bugs.mojang.com/browse/MC-7882
@Thomaz Calazans Linhares Junior
The delay is significantly shorter for most things now I feel, but it definitely isn't just on block-picking (was chosen as an easy example since it changes in one frame, whereas movement has a bit of momentum and I couldn't find a QIPress equivalent for mouse movements), and I would have agreed with "near unplayable" when the delay was at its worst.
The end goal should be to have controls be as or more responsive than they are in Java, since Bedrock has overall a better performing engine.
@Auldrick
Checking the latest beta, it appears that this has already been fixed (or consistent with Java 1.12 at least) and the slash is now optional in the inner command.
Seems intentional. It's blue because it's highlighted (can get same effect highlighting text manually), and it's highlighted so that whatever you type next will replace that text.
Affects 18w11a.
I think this occurs not when there are blocks "listening for block changes", but instead when there is a reasonable amount of geometry in the chunk. I've attached
[media], which has examples set up to reproduce the lag. World may take a few moments to load up.
@maggstrom - that doesn't appear to be the same issue. This problem is that sponge blocks delete waterlogged blocks (sponge should not break the blocks), that issue is that waterlogged blocks don't leave behind water when broken.
Still occurs in 17w13b. The bug that this one is marked as a duplicate of has been fixed (it was caused in a different scenario by a different line of code), so requesting this one to be reopened, as it is not fixed.
This is even worse than it first seems, because using
clear
with amaxCount
of 0 is how maps/datapacks check how many of an item a player has.With this bug causing
maxCount
to be ignored, checking how many items a player has will instantly delete the items they're crafting with.