Cloned "Always Active" repeating command blocks don't activate until their "Redstone" value is toggled
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 Zeb: This behavior also occurs when placing CTRL+Pick-Block'd repeating command blocks set to "Always Active".
Created Issue:
Cloned always-on repeating command blocks stop working
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.
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10
- 1.1.0.55
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 Zeb : This behavior also occurs when placing CTRL+Pick-Block'd repeating command blocks set to "Always Active".
Clonedalways-onrepeating command blocksstop workingCloned "Always Active" repeating command blocks don't activate until their "Redstone" value is toggled
relates to
is cloned by
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)
Revised title to be more descriptive.
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
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
Please refer to
MCPE-36340.