The bug appears to corrupt the command usually when the player inputs a target selector such as @a or @p. Here is the command of one of my command blocks that recently got corrupted out of the blue.
/scoreboard players test @e[type=armor_stand,name=anvil_gametime] anvil_gametime 0 15
The command gets corrupted once I leave the 'e' in the '@e' part. Other selectors such as @a and @p work just fine, but I cannot use them for what I am trying to create. I would appreciate it if this bug was taken action upon soon, since I have to get things done urgently on my realm and they all require tons of command blocks.
Even if the particles only run when a player is near it, they render for all players in the same world, despite the fact that they are tens of thousands of blocks away. This is catastrophic when a player loads an area with a lot of translucent particles that can be extremely demanding for people on the same world with mid-low end devices. I have seen Xbox Series X's fall to their knees with fog particles rendering far out of render distance. I believe the particles should be rendered where you want them to be, but the player's set render distance should be a hard limit.
I just reproduced this on 1.17.10.04 with vanilla and custom particles and they are still showing up far out of render distance. Attached is the custom particle I am testing this issue with and its texture.
Text on signs work just fine on most realms, but not on mine. It's frustrating that we can't use one of the most commonly used blocks for communication in our minigames. Fix this.
Matyas Gulyas
MCPE-128826
The bug appears to corrupt the command usually when the player inputs a target selector such as @a or @p. Here is the command of one of my command blocks that recently got corrupted out of the blue.
The command gets corrupted once I leave the 'e' in the '@e' part. Other selectors such as @a and @p work just fine, but I cannot use them for what I am trying to create. I would appreciate it if this bug was taken action upon soon, since I have to get things done urgently on my realm and they all require tons of command blocks.
Even if the particles only run when a player is near it, they render for all players in the same world, despite the fact that they are tens of thousands of blocks away. This is catastrophic when a player loads an area with a lot of translucent particles that can be extremely demanding for people on the same world with mid-low end devices. I have seen Xbox Series X's fall to their knees with fog particles rendering far out of render distance. I believe the particles should be rendered where you want them to be, but the player's set render distance should be a hard limit.
I just reproduced this on 1.17.10.04 with vanilla and custom particles and they are still showing up far out of render distance. Attached is the custom particle I am testing this issue with and its texture.
stripesbigblue.particle.json
I also attached a link to the shader resource pack that removes fog and makes it easier to see that the particles are still rendered.
https://mcpedl.com/fog-remover-pack/
Text on signs work just fine on most realms, but not on mine. It's frustrating that we can't use one of the most commonly used blocks for communication in our minigames. Fix this.