MC-77600Command block pick block with NBT and sendCommandFeedback is bugged
When you use pick block with NBT (Ctrl + Mouse Wheel) on a command block with TrackOutput:1 and /gamerule sendCommandFeedback = false, and then place the command block it is some kind of bugged.
How to reproduce:
1. /gamerule sendCommandFeedback false
2. Place a command block and run a command which return any kind of feedback
3. Copy the command block with its NBT data
4. Place the command block
Now you cannot see any anything in the LastOutput line, but when you press the "X" you can see it.
I expected either that Minecraft ignores the gamerule when the command block has the tag TrackOutput:1 or that it sets it to 0 if the gamerule is false but also clears then the LastOutput
Created Issue:
Command block pick block with NBT and sendCommandFeedback is bugged
When you use pick block with NBT (Ctrl + Mouse Wheel) on a command block with TrackOutput:1 and /gamerule sendCommandFeedback = false, and then place the command block it is some kind of bugged.
How to reproduce:
1. /gamerule commandBlockFeedback false
2. Place a command block and run a command which return any kind of feedback
3. Copy the command block with its NBT data
4. Place the command blockNow you cannot see any anything in the LastOutput line, but when you press the "X" you can see it.
I expected either that Minecraft ignores the gamerule when the command block has the tag TrackOutput:1 or that it sets it to 0 if the gamerule is false but also clears then the LastOutput
When you use pick block with NBT (Ctrl + Mouse Wheel) on a command block with TrackOutput:1 and /gamerule sendCommandFeedback = false, and then place the command block it is some kind of bugged.
How to reproduce:
1. /gamerulecommandBlockFeedback false
2. Place a command block and run a command which return any kind of feedback
3. Copy the command block with its NBT data
4. Place the command blockNow you cannot see any anything in the LastOutput line, but when you press the "X" you can see it.
I expected either that Minecraft ignores the gamerule when the command block has the tag TrackOutput:1 or that it sets it to 0 if the gamerule is false but also clears then the LastOutput
When you use pick block with NBT (Ctrl + Mouse Wheel) on a command block with TrackOutput:1 and /gamerule sendCommandFeedback = false, and then place the command block it is some kind of bugged.
How to reproduce:
1. /gamerule sendCommandFeedback false
2. Place a command block and run a command which return any kind of feedback
3. Copy the command block with its NBT data
4. Place the command blockNow you cannot see any anything in the LastOutput line, but when you press the "X" you can see it.
I expected either that Minecraft ignores the gamerule when the command block has the tag TrackOutput:1 or that it sets it to 0 if the gamerule is false but also clears then the LastOutput
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
/gamerule commandBlockFeedback falseWhat?
Messed it a little bit up, I meant sendCommandFeedback
Confirmed for 1.8.7. The game does understand that the "TrackOutput" tag inside "BlockEntityTag" is set to a specific value when placing the command block, but the gamerule ends up overriding it after-the-fact.
Is this still an issue in the most recent versions (i.e. 1.10.2, or 16w42a) of Minecraft?
Seems to be fixed in 17w47b and likely easlier versions. It now uses the TrackOuput value of the command block and only if that does not exist sets it based on the gamerule.