[MCPE-22450] Cloned "Always Active" repeating command blocks don't activate until their "Redstone" value is toggled Created: 06/Jun/17  Updated: 28/Nov/18  Resolved: 19/Jun/18

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 1.1.0.55, 1.1.1.1
Fix Version/s: None

Type: Bug
Reporter: Daniel Rollins
Resolution: Cannot Reproduce Votes: 2
Labels: /clone, repeating_command_block

Issue Links:
Cloners
is cloned by MCPE-37821 Cloned "Always Active" repeating comm... Resolved
Relates
relates to MCPE-36340 Command blocks don't working after cl... Resolved
Confirmation Status: Confirmed
Platform: Windows
CHK:

 Description   

Create a repeating command block and set to always on. Put in any command. Clone the command block and the clone will not be on until you change the setting to needs redstone, close out of the command block gui, then go back in and change the setting to always on again.

Edit by SuperGeniusZeb: This behavior also occurs when placing CTRL+Pick-Block'd repeating command blocks set to "Always Active".



 Comments   
Comment by [Mojang] Mega_Spud (Jay Wells) [ 28/Nov/18 ]

Please refer to MCPE-36340.

Comment by billy [ 28/Sep/18 ]

I just made a new ticket for this bug because it still isn't fixed

Here is the link to itΒ https://bugs.mojang.com/browse/MCPE-37821

Comment by [Mojang] Mega_Spud (Jay Wells) [ 19/Jun/18 ]

Cleaning up old tickets: This ticket has not been updated recently (1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.

Quick Links:
πŸ““ Issue Guidelines – πŸ’¬ Community Support – πŸ“§ Feedback – πŸ“– Game Wiki

Comment by Zeb [ 18/Jun/17 ]

Revised title to be more descriptive.

Comment by Katie Heart [ 07/Jun/17 ]

Video over 10mb so I uploaded example to YouTube
EDIT: Also existed in a 1.1 beta build on Google Play before the 1.0.9.1 release.
Samsung Galaxy Note 4 (Android 5.1.1 - custom ROM; armv7l)

Generated at Sat Jan 11 15:34:58 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.