-
Bug
-
Resolution: Duplicate
-
None
-
1.21.2 Hotfix
-
None
-
Unconfirmed
-
PlayStation
I'm not sure if it's intended or not but while I was making a random events map for me and some friends I was in need to use the /setblock command to place a redstone block down. But I wanted it to be placed after 1 min the command block being activated. I set the tick delay to 1200 ticks or 1min. And it didn't work. I then reset the tick delay to 0 and it worked I also tried 5 delay in tick it also worked. So then I tried 30sec delay or 600 tick delay it also didn't work. I was really hoping I'd be able to delay it by 1 min but it never ended up working. Lots of other commands work of being delayed by a min though so I thought it felt off that the /setblock command wasn't working with a 1min delay. And like I said I'm not sure if it's an intended feature or a bug.
The following statements I make is an updated version of my previous statement due to not having enough resources to find the issue or how other player could find this issue.
Steps to reproduce:
- Place down a impulse command block that is required to be activated by Redstone and type in the following command /setblock 348 98 -468 redstone_block, Then place a button on the command block.(Those coordinates I used are place holder where you'd put you're coordinates please use any coordinate that works for you)
- set the command delay to 1200 ticks=1min.
- After 1 min check the coordinates that you told the command block to place it in.
- The results on my end was no Redstone block or even a message at the top left corner of the screen showing that the command has been successful.
- change the delay in ticks from the original command block to 5 keeping every other rule the same(impulse, needs Redstone, or command).
- after a quarter of a second hence 5 ticks check for the Redstone block where the command block was set to place it in.
- The results on my end was a Redstone block at the desired location the command block was supposed to place it, I also got a message at the top left corner of the screen stating the command was successful.
- I then tried a 2 min delay with the same command and same setup but with the delay in ticks being 2400 and got the same results after activating it with a button as I did on steps 1-4
Observed Results:
The time delay that i tried that did not work are 30sec, 1min, or 2 min delay. They did not show proper message at top left corner of screen letting the player know the command was successful.(using /setblock command) I also realized that if using any other command like the /give command works fine with these types of delays.
Expected Results:
30 sec, 1min, and 2min delay while using the /setblock command in a command block should be showing that the command was successful and should be placing the desired block at the desired location. (in my case this block was a Redstone block)
- duplicates
-
MCPE-145283 Command blocks with delay don't execute unless they remain powered for the delay duration
- Resolved