When I use command blocks and set them to "always active," I expect them to be just that.
"always active." Yet somehow this can fail at complete random. If they are outside of spawn chunks they can randomly stop working for no reason or explanation.
obviously they will not work if you are not in their range, I get that.
however THESE FAIL EVEN WHEN YOU ARE IN THE SAME CHUNK. It's like they don't realize you're in range again and don't update.
The only way to fix them is to set them to "Needs Redstone," which sometimes not even this works.
sometimes the command block it's self is cursed, and you have to give yourself a new one.
please, make your stuff do it's job. This glitch is as old as time. It can't be that hard to make command blocks do their job. I shouldn't have to rip out my hair trying to figure out what's wrong with my stuff only to realize your stuff is a broken mess.
WORSE YET! What if someone releases a map, only to find out later the map is broken due to one of these cursed command blocks? What then?
I believe the current system works, it really does.
anything within spawn range should always be active.
however, what I am advocating for is better wake up for these command blocks.
I think the problem is that they go out of range but then fail to re active when they should.
::::IMPORTANT DISTINCTION FOR PEOPLE WHO DIDN'T PAY ATTENTION! ::::::::
I KNOW COMMAND BLOCKS ARE NATURALLY UNLOADED! DUH! I METION THIS WITHIN THE FIRST PARAGRAPH!
THE ACTUAL PROBLEM;;;;;
THIS IS REALLY IMPORTANT IF YOU INTEND TO BE OF ANY HELP AT ALL SO PAY ATTENTION THIS TIME!
THESE COMMAND BLOCKS ARE NOT WORKING WITHIN THE SAME CHUNK! GET IT YET?
THEY ARE L O A D E D! YET THE GAME DOESNT THINK SO!
IN OTHER TERMS; You could stand right next to the command block and nothing will change. It’s just busted.
LITERALLY THE ENTIRE PROBLEM IS THAT THEY UNLOAD, AND THEN FAIL TO RE-LOAD
Comments 10
of course, I don't really understand command blocks, but I know that it would be better to use "need a signal" (so you can check its performance)
and don't forget to put a slash at the beginning of the command
For example, write: /time set night
is mandatory during the day
If it works, then try to turn on "always active"
The main problem here is that there’s almost no way to test this glitch.
these command blocks fail at complete random.
Like, one will fail and all the others around it will be fine.
I have been doing command blocks for many years and have never come across this problem. Have you tried relogging, checking the "Previous Output" section or even just testing with a few "say hi" command blocks?
Always being active/powered doesn't mean they're always in loaded chunks.
The game is not going to load every single chunk that was generated for you...
Cannot confirm the rest.