Confirmed in 1.19.2 single player world
Confirmed for 1.18. I was wondering why only one part of my map was always so laggy when I looked at it or moved around it.
Confirmed for 1.16.3 and 1.16.4, aaand all the snapshots up to 20w51a.
Confirmed for all 20w snapshots, including up to 20w09a.
Confirmed for 20w06a
I wonder if saying "bump" will bump this bug. Still affects the newest version, 20w06a and all prior versions.
Double or triple escape the backslashes with more backslashes.
For future reference, don't put commands questions as a report on the bug tracker.
Can confirm. Also applies to beds, conduits, and banners. and possibly other placeable objects with complex block models. However, the type of shading change is different for all the listed blocks, meaning sometimes it flips, or sometimes the shadow side gets halfway lighter, or even brighter than the lighter side.
Try this:
Place a jukebox down.
Run the following command at the jukebox:
data merge block ~ ~ ~ {RecordItem:{id:"minecraft:stone",Count:1b,tag:{test:[""]}}}
Now get the jukebox's data using /data get block
Confirmed for all versions from 18w47b to the latest snapshot.
Didn't get a chance to test before 18w47b.
Confirmed for 18w50a. I wish they'd get someone on this, and quickly.
Any time my player dies, all armor stands, item frames, and falling blocks in my custom map become invisible and impossible to interact with. It's a huge issue and makes testing impractical.
Confirmed for 18w48b.
But why? Why won't they fix this?
Confirmed for 18w44a
Confirmed for 18w03b
It's interesting how using numbers still works with the old format. Funny that.
I tried toying with the syntax, but I couldn't get it to work. Do you know where I could find one example of this?
I really hope they address this issue in the next snapshot. I've been deadlocked on mapmaking ever since.
Confirmed for snapshot 23w13a.