Antony Jiang

I don't know why it sent me to BDS. This was meant for Minecraft: Bedrock Edition ^^

This may be a world generation bug. I personally found decent amounts of Ancient Debris in different worlds, so no problem for me. To test if your world has a bug: copy your world, turn cheats on, give yourself a repeating_command_block, go to the nether, and insert the command 

execute @a[name=Stephanie] ~~~ fill ~10 ~10 ~10 ~-10 ~-10 ~-10 air 0 replace netherrack

(replace 'Stephanie' with your in-game name) Fly around the nether and see whether or not there actually is Ancient Debris. Even if there's only one or two, this does not mean it's a bug. World generations vary; good luck!

Is this actually a bug? I've seen videos online where the anvil doesn't (or shouldn't) break once it touches the ground... unless there's a torch or slab underneath, it does not make sense for an anvil to break on a solid block.

Need more info ^^ Are you playing on a world before the Nether Update? If so, loaded chunks from older versions may not contain any Ancient Debris. They're also decently rare, try using beds in the nether to make the process of finding them easier!

Hello Eugeni,

This is not a bug nor is it Mojang's fault. You are interpreting the command wrong. If you use "facing 0 0 0", the sheep will look in the direction of 0 0 0 forever. If you use "facing ~~~", it is looking at the direction it wants to, but more stuttery. If you are looking for the sheep to face you indefinitely, use /tp @e[type=sheep] ~ ~_0.5 ~ facing @p[name=Eugeni]. (Replace 'Eugeni' with your in-game name) If you are looking for the sheep to look in one direction forever, use /tp @e[type=sheep] ~ ~_0.5 ~ facing x y z (with specific coordinates). Hope this helped!

Hello Connor,

This is not a bug nor Mojang's fault. You should be careful summoning withers on a repeating_command_block. Here's a hotfix based on your description:

-Set the world difficulty to peaceful from the 'Worlds' tab (not in-game).

-If lag still persists, but you are able to get into the game, use /kill @e[type=!player] to kill all mobs in the world (or use ie. /kill @e[type=!player,type=!cow] if you have a cow farm and wouldn't like to kill all the cows} and /gamerule commandblocksenabled false if you suspect a destructive command block running in the background. Find the command block, destroy it, and then type /gamerule commandblocksenabled true. Hope this helps!

The issue has been reported with repeating command blocks (with specific commands) fails to work suddenly and/or reopening the world ^^

This is a self-prescribed hotfix done to my world:

-Use /execute commands when available (didn't run into many problems with /execute compared to /tp or /testfor)

-Change the repeating command block to 'Needs Redstone'

-Power the command block with a redstone_block

So far, the world has been running much smoother. Most of the faults now are with my own coding. Hope this works!

v1.16.10 – Tried cloning a 2x2x1 space that is 2 blocks from the clone command block to a spot 3 blocks away from the same command block as a test before a much bigger clone. Got the same error message.

v1.16.10 – Having the same problem ^^ Some of the repeating command blocks (both IN and OUT of a /tickingarea) fail after I leave the general area or when I leave/rejoin the world. The bug seems to be heavily affecting my /tp and /testfor command blocks that are decently packed in a chunk (edited).

P.S. Switching from Repeat>Impulse>Repeat temporarily fixes this situation. Also, setting the repeating command block to "Needs Redstone" and manually powering it (ie. redstone_block) hasn't given me a bug yet.