MC-133389Command blocks dont show commands sometimes
I put a command block down with either /tp Liftski ^ ^ ^3 (this one was showed in the screenshot) or /execute as Liftski run tp @s ^ ^ ^3 (pre-8)
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it. It will take 0-2 seconds to load that text. If typing /execute as (player) run tp @s ^ ^ ^3 (pre-7 and pre-8) it wont load at all, if looking in the right place
NOTE: Clicking a command block that's off will not show the command IF you click it in the right spot.
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. if it works that way, it could possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
NOTE: This kind-of happens with command blocks that are off, but they go back to normal after about 0-2 seconds.
Environment
Latest java version, 1.13-pre7, Windows 8.1
Linked Issues
Attachments1
Created Issue:
Command blocks dont show commands sometimes
Type the command /execute as (player) run tp ^ ^ ^3 on a repeat command block with always active on. Sometimes, when you click it, it doesnt show the command and acts like the command block is empty.
Environment
Latest java version, 1.13-pre7, Windows 8.1
Attachments1
Type the command /execute as (player) run tp ^ ^ ^3 on a repeat command block with always active on. Sometimes, when you click it, it doesnt show the command and acts like the command block is empty.
Type the command /execute as (player) run tp ^ ^ ^3 on a repeat command block with always active on. Sometimes, when you click it, it doesnt show the command and acts like the command block is empty.
Type the command
/execute as (player) run tp ^ ^ ^3 on a repeat command block with always active on. Sometimes, when you click it, it doesnt show the command and acts like the command block is empty.Type the command tp ~ ~ ~3 on a repeat command block with always active on. Sometimes, when you click it, it doesnt show the command and acts like the command block is empty.
Type the command tp
~ ~ ~3 on a repeat command block with always active on. Sometimes, when you click it, it doesnt show the command and acts like the command block is empty.Type the command tp ^ ^ ^3 on a repeat command block with always active on. Sometimes, when you click it, it doesnt show the command and acts like the command block is empty.
Possibly. The command block in the picture actually has the command "tp Liftski ^ ^ ^3" in it.
Type thecommandtp ^ ^ ^3 on a repeat command block with always active on. Sometimes, when you click it, it doesnt show the command and acts like the command block is empty.I put a command block down with either /tp Liftski ^ ^ ^3 (this one was on, and showed in the screenshot) and another one with the command that i thought would work the same, but worked how i thought it should, but was off.
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it.
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. While it could be useful for an adventure map with a random ending, if it works that way, it could also possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
I put a command block down with either /tp Liftski ^ ^ ^3 (this one was
on, andshowed in the screenshot)and another one with the command that i thought would work the same, but worked how i thought it should, but was off.What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it.
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. While it could be useful for an adventure map with a random ending, if it works that way, it could also possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
I put a command block down with either /tp Liftski ^ ^ ^3 (this one was showed in the screenshot)
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it.
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command.
While it could be useful for an adventure map with a random ending,if it works that way, it couldalsopossibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!I put a command block down with either /tp Liftski ^ ^ ^3 (this one was showed in the screenshot)
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it.
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. if it works that way, it could possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
NOTE: This kind-of happens with command blocks that are off, but they go back to normal after about 2 seconds.
I put a command block down with either /tp Liftski ^ ^ ^3 (this one was showed in the screenshot)
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it.
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. if it works that way, it could possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
NOTE: This kind-of happens with command blocks that are off, but they go back to normal after about 0-2 seconds.
I put a command block down with either /tp Liftski ^ ^ ^3 (this one was showed in the screenshot) or /execute as Liftski run tp @s ^ ^ ^3 (pre-8)
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it. It will take 0-2 seconds to load that text. If typing /execute as (player) run tp @s ^ ^ ^3 (pre-7 and pre-8) it wont load at all
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. if it works that way, it could possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
NOTE: This kind-of happens with command blocks that are off, but they go back to normal after about 0-2 seconds.
I put a command block down with either /tp Liftski ^ ^ ^3 (this one was showed in the screenshot) or /execute as Liftski run tp @s ^ ^ ^3 (pre-8)
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it. It will take 0-2 seconds to load that text. If typing /execute as (player) run tp @s ^ ^ ^3 (pre-7 and pre-8) it wont load at all, if looking in the right place
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. if it works that way, it could possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
NOTE: This kind-of happens with command blocks that are off, but they go back to normal after about 0-2 seconds.
I put a command block down with either /tp Liftski ^ ^ ^3 (this one was showed in the screenshot) or /execute as Liftski run tp @s ^ ^ ^3 (pre-8)
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it. It will take 0-2 seconds to load that text. If typing /execute as (player) run tp @s ^ ^ ^3 (pre-7 and pre-8) it wont load at all, if looking in the right place
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. if it works that way, it could possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
NOTE: This kind-of happens with command blocks that are off, but they go back to normal after about 0-2 seconds.
I put a command block down with either /tp Liftski ^ ^ ^3 (this one was showed in the screenshot) or /execute as Liftski run tp @s ^ ^ ^3 (pre-8)
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it. It will take 0-2 seconds to load that text. If typing /execute as (player) run tp @s ^ ^ ^3 (pre-7 and pre-8) it wont load at all, if looking in the right place
NOTE: Clicking a command block that's off will
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. if it works that way, it could possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
NOTE: This kind-of happens with command blocks that are off, but they go back to normal after about 0-2 seconds.
I put a command block down with either /tp Liftski ^ ^ ^3 (this one was showed in the screenshot) or /execute as Liftski run tp @s ^ ^ ^3 (pre-8)
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it. It will take 0-2 seconds to load that text. If typing /execute as (player) run tp @s ^ ^ ^3 (pre-7 and pre-8) it wont load at all, if looking in the right place
NOTE: Clicking a command block that's off will
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. if it works that way, it could possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
NOTE: This kind-of happens with command blocks that are off, but they go back to normal after about 0-2 seconds.
I put a command block down with either /tp Liftski ^ ^ ^3 (this one was showed in the screenshot) or /execute as Liftski run tp @s ^ ^ ^3 (pre-8)
What i thought would happen:
I opened the command block, and 100% of the time it said the command inside.
What happened:
The command block worked like it had the command in it, and only about 30% of the time it displayed the command that the block held. The other 70% of the time it acted like i just placed the block down.
How to reproduce:
Place down a command block, and put any text in it. Close out with done to save what you put in the command block ex. "Say TEST!" and run it to make sure you entered a valid command. Click the command block a few times. Sometimes, you won't see the text you entered, ex: "Say TEST!" doesnt display but it acts like it has "Say TEST!" in it when you run it. It will take 0-2 seconds to load that text. If typing /execute as (player) run tp @s ^ ^ ^3 (pre-7 and pre-8) it wont load at all, if looking in the right place
NOTE: Clicking a command block that's off will not show the command IF you click it in the right spot.
I feel like this bug could let you break command blocks if you write text in its bugged state, in a way that it could run a certain command. if it works that way, it could possibly be very annoying, if you had a command in there that you wanted to expand. Please fix this bug!
NOTE: This kind-of happens with command blocks that are off, but they go back to normal after about 0-2 seconds.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
duplicates
When trying to see if MC-133389 happens in 1.13-pre8,i found that /tp Liftski ^ ^ ^3 was invalid. I dont know if this just affects command blocks, but it definitely doesn't seem like its supposed to work.
How to Reproduce:
Grab a repeating command block, place it anywhere, and type the command "tp (player) ^ ^ ^3" and click always active. It will say that /tp (player) ^ ^ ^3 is invalid syntax, while i discovered MC-133389 by discovering MC-133388, which had the command /tp Liftski ^ ^ ^3. This could be VERY bad for adventure maps. NOTE: It does not glitch out with /execute as (player) run tp @s ^ ^ ^3, so the game is certainly bugging out.
Note: As said in a comment, i accidentally hit the spacebar.
Maybe related to "
MC-86771- Command block sometimes not showing previous output".