Some block state changes aren't communicated to clients

Server has some internals that 'leak' through blockstates, they are not send to reduce traffic.

It's been 7 years. Is it possible to reconsider the 'works as intended' stance on this issue? I'm a texture pack creator and it bugs me to no end that I can't change textures for certain blocks based on their states. I'd love to show when hoppers are locked or when droppers/dispenser are triggered among other things.

I understand there may be legitimate performance reasons to leave it as is, but could we at least have a game/server setting to enable these updates so people could opt into having the extra functionality?

@Joshua Olufs, I would like to see this as well. Quite Irksome.
something as simple as a client setting/toggle: "Send/Receive Extended Blockstate changes (ToolTip: Warning: Server must have setting enabled and may use additional network/cpu resources)"

please fix this bug please

this is so confusing

Resolution: Works As Intended

They don't want to change this.

You can post suggestions on the Feedback site: https://feedback.minecraft.net/

We still have this problem in 1.19.1

And it's not changing. No need to confirm for versions anymore, this is by design to reduce traffic for client server communication.

This issue is still present in 1.19.4 Minecraft with Sugar Cane not showing it’s true age in F3 screen. I would like to recommend that this gets looked at again by Mojang since Grum’s comment is about 7 years old and standards might had changed since then. Ideally, blockstate changes on server should be synced to the client to help promote easier F3 debugging of issues and/or allow resource packs to properly work. Example of a sugar cane resourcepack that tries to change the look of sugar cane to match their age is in this other issue report that was closed as a duplicate of this current one: MC-135830