This issue I am currently running into suddenly after 6 months of using this command to create my adventure map for my friends is a bit hard to explain, so I will explain my process first:
I create a 4x4 of blocks of my choosing to use as a ground type I would like.
I place down a repeating command block with the command execute @a[m=c,tag=brush] ^ ^ ^10 clone xyz uvw ~-3 ~-2 ~-3 masked normal.
I will write down the coordinates xyz and uvw of the 4x4 I created.
I will activate the repeating command block with a redstone block and now my "paintbrush" is ready to use whenever I add the tag (brush) to myself as long as I am within the range of the 4x4 and command block.
If I go ahead and add the tag to myself it works fine, until...
When I'm working a little too far from the repeating command block it will not longer be able to execute the command. (Side note: My render distance is set to 40 so the 4x4 is still within loaded chunks.)
Normally to extend my range I would place another repeating command block with the same command and coordinates, and be on my merry way creating landscapes. However now the secondary repeating command block will fail to execute even when I have the tag activated. I even tried to go back and remove the first command block to see if they interfered. However the secondary command block still would not execute and where the first command block was, was still executing the command as if it was still their.
The only workaround I found was just creating a new 4x4 every time I needed to extend my range. However because of how short the range is on the command blocks this has put a huge delay on my project and I now have no motivation to finishing the map....
Linked issues
Attachments
Comments 7
Yea even then I've been able to use this command 6 months straight until a few days ago. It fails on the second command block even if its 50 blocks away. Did this Simulation Distance change recently? I just added a screenshot, I was able to make this with only one 4x4 and just placing new command blocks when the command was out of range. This no longer is the case however...
If it stops 50 blocks away, that means your world's simulation distance is at 4 chunks. By changing it to 12, the range will be significantly further. Or just add a ticking area, which would make it work anywhere in the world.
Ugh... I feel like I'm not getting anywhere with this. So to clear things up I have used this command 6 MONTHS with no trouble. 1. Even if it is the simulation distance how do I change this on bedrock? And 2. Why would this setting randomly change from being set to the correct distance to what it apparently is not non-sufficient? Currently my work around is just to make a new 4x4 along with a new command block anywhere I need to extend but this was not previously the case. I swear this is abnormal and a bug but don't think it will ever get fixed...
(But thank you Ice that's actually useful thanks for the ticking area idea, I will have to try that and see if that makes this better! 🙂)
It is likely there was a recent change where previously, certain actions could still apply for chunks within Render Distance but outside Simulation distance. A related report is (MCPE-154009.
Ahhh I see and yes that report is a good summary of the problem I am facing. Also Ice's comment about using a ticking area seems to be working wonders as well.
The command block needs to be within the Simulation Distance. The Render Distance has no effect.