mojira.dev
MCPE-145283

Command blocks with delay don't execute unless they remain powered for the delay duration

Steps to reproduce

  • Create a world with cheats enabled

  • Place a command block and set a command. Set redstone to "Needs Redstone" and put a delay in ticks other than 0.

  • Give the command block a signal

Expected Results

  • Command block executes command after the delay in ticks

Observed Results

  • Command block does not execute command

Notes

Issue started to occur after the 1.17.40 update

Linked issues

BDS-16103 the command blocks are limited to only 20 ticks,but more than that could stop the command. Resolved BDS-16792 The impulse command block tick set won't work unless it is power 24/7 Resolved MCPE-145327 Command Block Set With Delay On Tick Does Not Work Properly With Redstone Resolved MCPE-145477 Command Blocks with Tick Delay no longer work unless continuously powered Resolved MCPE-145478 Command Block Tick Delay Resolved

Comments 16

This is not a bug declared by the changelog, and I do think this change isn't necessarily significant either since it ruins some command executions.

If you want to help create a change for this, I recommend voting for this particular valuable feature for command block users.

Link: https://feedback.minecraft.net/hc/en-us/community/posts/4411762335885--Tick-In-Delay-Should-Have-Different-Toggle-Features

This is not a bug declared by the changelog, and I do think this change isn't necessarily significant either since it ruins some command executions.

If you want to help create a change for this, I recommend voting for this particular valuable feature for command block users.

Link: https://feedback.minecraft.net/hc/en-us/community/posts/4411762335885--Tick-In-Delay-Should-Have-Different-Toggle-Features

Is the bug getting resolved? It's not working as intended this patch? Has the solution been found for next update?

Is the bug getting resolved? It's not working as intended this patch? Has the solution been found for next update?

Hey Joshua, so regarding the command block "bug" it actually isn't a bug. It was a feature in 1.17.40. An easy work around to fix it is to add another command block before it (don't change the settings) and than change the command block with a tick delay to a chain block and always active.

6 more comments

goodbye hours of hard work. this broke everything in my world... i might as well consider this a bug.

Jake, could you elaborate? im trying to fix my own world.

Jake, could you elaborate? im trying to fix my own world.

Could someone please elaborate on if there’s any way to change the game files to make command blocks not do this using an add-on. Or if there is any other wise sweeping solution. With people who have huge worlds with command blocks going though command blocks hand by hand would take weeks- and it’s very frustrating when the only response we get is that it’s “supposed to be this way now.” 

Could someone please elaborate on if there’s any way to change the game files to make command blocks not do this using an add-on. Or if there is any other wise sweeping solution. With people who have huge worlds with command blocks going though command blocks hand by hand would take weeks- and it’s very frustrating when the only response we get is that it’s “supposed to be this way now.” 

Jake Chiarenza

(Unassigned)

Unconfirmed

Xbox

1.17.40

Retrieved