MC-58634Command block previous output doesn't update properly after setblock
-
- Place a command block and copy in this command (or just not a setblock command):
/setblock ~ 257 ~ command_block
- Power the command block, it should have now an error message ("... is too big, it must be at most 256") in the previous output line
- Change the command to:
/setblock ~ ~ ~ command_block
Amd power it again
- Look again at the previous output line
- Place a command block and copy in this command (or just not a setblock command):
It has still the error message like before
This is a double bug as
- The success output is missing
- There is still a last output even no command was performed at this command block (that's probably not intended like other NBT tags like the command itself was reset
Created Issue:
Command block last output doesn't update properly after setblock
- Place a command block and copy in this command (or just not a setblock command):
/setblock ~ 257 ~ command_block- Power the command block, it should have now an error message ("... is too big, it must be at most 256") in the last output line
- Change the command to:
/setblock ~ ~ ~ command_blockAmd power it again
- Look again at the last output line
It has still the error message like before
This is a double bug as
- The success output is missing
- There is still a last output even no command was performed at this command block (that's probably not intended like other NBT tags like the command itself was reset
- Unresolved
- Open
- Minecraft - Public
- Unconfirmed
- 14w25b
Added Labels: Command_Block Setblock previous_output
Removed Description:
- Place a command block and copy in this command (or just not a setblock command):
/setblock ~ 257 ~ command_block- Power the command block, it should have now an error message ("... is too big, it must be at most 256") in the last output line
- Change the command to:
/setblock ~ ~ ~ command_blockAmd power it again
- Look again at the last output line
It has still the error message like before
This is a double bug as
- The success output is missing
- There is still a last output even no command was performed at this command block (that's probably not intended like other NBT tags like the command itself was reset
Added Description:
- Place a command block and copy in this command (or just not a setblock command):
/setblock ~ 257 ~ command_block- Power the command block, it should have now an error message ("... is too big, it must be at most 256") in the last output line
- Change the command to:
/setblock ~ ~ ~ command_blockAmd power it again
- Look again at the last output line
It has still the error message like before
This is a double bug as
- The success output is missing
- There is still a last output even no command was performed at this command block (that's probably not intended like other NBT tags like the command itself was reset
Changed Description:
- Place a command block and copy in this command (or just not a setblock command):
/setblock ~ 257 ~ command_block- Power the command block, it should have now an error message ("... is too big, it must be at most 256") in the
lastoutput line- Change the command to:
/setblock ~ ~ ~ command_blockAmd power it again
- Look again at the
lastoutput lineIt has still the error message like before
This is a double bug as
- The success output is missing
- There is still a
lastoutput even no command was performed at this command block (that's probably not intended like other NBT tags like the command itself was reset
- Place a command block and copy in this command (or just not a setblock command):
/setblock ~ 257 ~ command_block- Power the command block, it should have now an error message ("... is too big, it must be at most 256") in the previous output line
- Change the command to:
/setblock ~ ~ ~ command_blockAmd power it again
- Look again at the previous output line
It has still the error message like before
This is a double bug as
- The success output is missing
- There is still a previous output even no command was performed at this command block (that's probably not intended like other NBT tags like the command itself was reset
Changed Summary:
Command blocklastoutput doesn't update properly after setblockCommand block previous output doesn't update properly after setblock
Changed Description:
- Place a command block and copy in this command (or just not a setblock command):
/setblock ~ 257 ~ command_block- Power the command block, it should have now an error message ("... is too big, it must be at most 256") in the
previousoutput line- Change the command to:
/setblock ~ ~ ~ command_blockAmd power it again
- Look again at the
previousoutput lineIt has still the error message like before
This is a double bug as
- The success output is missing
- There is still a
previousoutput even no command was performed at this command block (that's probably not intended like other NBT tags like the command itself was reset
- Place a command block and copy in this command (or just not a setblock command):
/setblock ~ 257 ~ command_block- Power the command block, it should have now an error message ("... is too big, it must be at most 256") in the last output line
- Change the command to:
/setblock ~ ~ ~ command_blockAmd power it again
- Look again at the last output line
It has still the error message like before
This is a double bug as
- The success output is missing
- There is still a last output even no command was performed at this command block (that's probably not intended like other NBT tags like the command itself was reset
Changed Summary:
Command blockpreviousoutput doesn't update properly after setblockCommand block last output doesn't update properly after setblock
Deleted Comment:
I am stupid and deleted by accident whole description on mobile
Changed Summary:
Command blocklastoutput doesn't update properly after setblockCommand block previous output doesn't update properly after setblock
Changed Description:
- Place a command block and copy in this command (or just not a setblock command):
/setblock ~ 257 ~ command_block- Power the command block, it should have now an error message ("... is too big, it must be at most 256") in the
lastoutput line- Change the command to:
/setblock ~ ~ ~ command_blockAmd power it again
- Look again at the
lastoutput lineIt has still the error message like before
This is a double bug as
- The success output is missing
- There is still a last output even no command was performed at this command block (that's probably not intended like other NBT tags like the command itself was reset
- Place a command block and copy in this command (or just not a setblock command):
/setblock ~ 257 ~ command_block- Power the command block, it should have now an error message ("... is too big, it must be at most 256") in the previous output line
- Change the command to:
/setblock ~ ~ ~ command_blockAmd power it again
- Look again at the previous output line
It has still the error message like before
This is a double bug as
- The success output is missing
- There is still a last output even no command was performed at this command block (that's probably not intended like other NBT tags like the command itself was reset
Deleted Comment:
Restored from the history.
Added Affects Versions: 14w26b
Deleted Comment:
Thank you so much
Added Affects Versions: 14w28b
Added Affects Versions: 14w29b
Added Affects Versions: 14w30c
Added Affects Versions: 14w31a
Added Affects Versions: 1.8-pre2
![[Mod] Torabi](../../../data/assets/gravatar/torabi.png){kind=small}
Added Labels: command_block setblock
Removed Labels: Command_Block Setblock
Added Affects Versions: 1.8.2-pre6
Added Labels: command-block previous-output
Removed Labels: command_block previous_output
Deleted Comment:
Fixed in a version after 1.8.2-pre6. (15w43c)
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Added Labels: command_block
Removed Labels: command-block
Without the last output text field the track output button has no context. Additionally when disabling the output "-" is shown as well.
It looks like MC-58634 might have been fixed by having the method net.minecraft.tileentity.CommandBlockBaseLogic.getLastOutput() never return null. This makes the method net.minecraft.client.gui.GuiCommandBlock.updateCmdOutput() set the output to an empty String which is not displayed.
Can't the output text field just be rendered always?
Fixed in 15w43c or in an other 1.9 snapshot (occurs in 1.8.8).
Fixed somewhere between 1.8.8 and 15w43c.