MC-149038Command blocks on repeating with always active or need redstone stop working
Command blocks on repeating with 'always active' or 'need redstone' stop working until updated again. This might be occurring when the chunk is unloaded. It's also possible that is is related to other problems with chunks unloading. Had this happen in several worlds by few people.
Created Issue:
Command blocks on repeating with always active or need redstone stop working
Command blocks on repeating with 'always active' or 'need redstone' stop working until updated again. This might be occurring when the chunk is unloaded. It's also possible that is is related to other problems with chunks unloading. Had this happen in several worlds by few people.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
![[Mojang] Bartosz Bok](../../../data/avatars/users/10122.svg){kind=small}
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
relates to
I use repeating blocks, always on, constantly, and I never know when one will freeze up. I use them to interrupt a summoner powered by a chest that will summon until the testfor interrupts the flow.
Kind of need that testfor not to freeze up guys.
Zombies. Everywhere. 😂
You're apparently playing on a very old version, /testfor was removed long ago. Please only report things in the latest release or snapshot.
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
Thank you for your report!
We're actually already tracking this issue in MC-149038, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Basically what the title says. If you first place a redstone block down and then a command block next to it (doesn't matter which type), change it to repeating and enter a command (such as: say hi!) it doesn't give output unless updated, either before or after the command was entered.
Feels related to MC-86846 and possibly MC-149038, not sure about that one.
Also was able to reproduce in 12.2, 13.2, 14.4, but this behaviour may then also have been produced by MC-86846 in the case where the command block was powered and on 'needs redstone' mode.
Easily read reproduction steps:
- place down redstone block
- place command block next to it
- set mode to repeating and enter any command (e.g. say hi)
- no output
- update command block (placing block next to it, breaking a block, (soft) powering it with redstone (again), etc.)
- output starts
What are the steps to reproduce this?
I'm having same issue, see
MC-149007.Need more info on it. Everyone's guess is unloading but cant confirm.
please dont set bug reports to "resolved" just because we dont know how to replicate it. Thank you
When it's resolved as AR it automatically reopens with a response. It's not the end all be all
I understand but it comes across as confusing, I got messaged by a few people saying this bug was resolved already and there fore they didn't contribute to this bug report.
Its resolved as "Awaiting response", its resolved but not fixed
Does
MC-86846describe your issue?Does this still happen in recent versions? We did fix few problems related to ticking, so this issue might already be fixed.
Still an issue.
In which version?
1.14.4.
I was never really able to reproduce this reliably and now I tried lots of different things in 1.15-pre1, all kinds of combinations between dimension change, view distance change, flying around, reopening the world, loading chunks and quickly unloading them again, laggy and not laggy server and so on. To test this, I had a bunch of command blocks adding and subtracting 1 from a scoreboard. The value stayed at 0.
Does someone know a reliable way to reproduce this? Or is it maybe fixed already in 1.15-pre1?
Was able to reproduce this bug in 1.15.1
What I did:
Not sure what the important part of this setup is, just added every single thing I've down. With more testing this could probably be narrowed down.
EDIT:
Not sure anymore if same bug or different one.
More testing:
EDIT:
I believe now this is a different bug. Updating it after it was placed adjacent to a redstone block but before the command is entered also fixes it. Created
MC-168681for this new bug.Actually Fabian, I thought this was a Bedrock report, as that was what I was searching for. In Bedrock we're still using testfor.
Is this still an issue in 21w20a or later?