Still having this issue as of Septemder 2026 in 26.3. I asked AI, and here is the answer:
The barrier itself has no block model. The implementation in Java Edition is rather special: The barrier block itself is completely transparent and invisible. Only when the player holds the barrier item, the client scans all nearby barrier blocks and spawns particles (block_marker particles) to draw the red‑cross icon. This icon is not a texture belonging to the block itself.
The scanning and particle‑spawning logic is not instantaneous and has inherent delay. After placing or breaking a barrier, particles are not spawned or cleared right away. As a result, the icon appears with a several‑second delay, and it still lingers for some time before disappearing after the barrier is broken.
Bedrock Edition has built‑in display markers for the block. Icons pop up immediately upon holding the item without this delay, so this is a well‑known parity issue.
It seems that resolving this bug is not an easy task.
fishheadDF
Still having this issue as of Septemder 2026 in 26.3. I asked AI, and here is the answer:
The barrier itself has no block model. The implementation in Java Edition is rather special: The barrier block itself is completely transparent and invisible. Only when the player holds the barrier item, the client scans all nearby barrier blocks and spawns particles (block_marker particles) to draw the red‑cross icon. This icon is not a texture belonging to the block itself.
The scanning and particle‑spawning logic is not instantaneous and has inherent delay. After placing or breaking a barrier, particles are not spawned or cleared right away. As a result, the icon appears with a several‑second delay, and it still lingers for some time before disappearing after the barrier is broken.
Bedrock Edition has built‑in display markers for the block. Icons pop up immediately upon holding the item without this delay, so this is a well‑known parity issue.
It seems that resolving this bug is not an easy task.