Impulse Command Block Bug & Title Bounding
Since this update impulse command plocks set to "need redstone" do not function correctly when set to a delay.
Most of my worlds have broken due to this, and when trying to debug the problem, I noticed this issue.
This means a command block set like this with a button and 10 seconds of delay will never trigger since a button powers it for less than the 10 second delay. Is this an oversight? It has made many of my designs unusable.
Also, as per my usual routine after an update, it is my duty to remind you that title command text are still not bounded by the screen and instead of creating a new line like it did over a year ago, it just starts and continues off the screen. Can this please be fixed? This has been a known issue by Minecraft for over a year now.
I have tested this with repeating command blocks set to "needs redstone" and on a delay. They also will not fire if they are not powered for the duration of the delay.
This bug or new feature breaks so many technical builds used in classrooms and makes command block coding more clunky and laggy to fix.
Can I have a dev's word on whether is is intentional or a bug so I can work out whether it is worth my time to spend hours trying to find a viable workaround or whether I should just wait. I have waited for over a year on bounded to screen title command in good faith (and still waiting) so I am not overly optimistic on how long this might take the devs to fix if this is a bug.0
Hum, I wonder if the command block delay bug exists in Bedrock? Might want to ask or check the bug reporting there to see if it was a bug for them in 1.18 and if it has been fixed in 1.19 or if this bug seems to be specific to Education Edition?
Ok, I did ask the question over on the Bedrock Addons Discord server since many creators over there have their fingers on the pulse of Bedrock edition and some of them will know of bugs like that if they happened in Bedrock edition in 1.18
______________________Edit to say________________________
Apparently this bug is actually a new Feature! Apparently the fix is that you need a new impulse command block first to take the button press and then pass it on to your original command block but change that one to a chain block always active to handle your delay.0
Thanks for the info Aleece Landis. I now know not to wait, and to start the hours and hours of fixing.
Thanks also for the fix idea. Where possible, I will implement this.
Unfortunately in a very compact command block build (like trying to use all 6 sides of a redstone block to get multiple command block inputs chains going at a time), squeezing an extra command block in to set off a chain is a very unviable solution to a needless problem. Considering that most people who even know how to use the delay function on a command block is likely to use these in complex and large chained designs, this feels like a poorly thought out feature that makes command blocks even more clunky to use.
The only use I can think of for this new 'feature' is making a minimum input delay checker. But how is this useful when scoreboard commands are already a thing? This breaks more things than it creates...0
Might be time to use functions to handle everything but you initial command.0
Please sign in to leave a comment.