The Meaning of Life, the Universe, and Everything.
Join Date:
10/23/2015
Posts:
52
Location:
A Place
Minecraft:
UKnighted
Member Details
When you CTRL+Middle mouse a command block (or anything that carries NBT data) it will save the information stored inside of it, wether that be always active or the command itself. But here's the thing; the "Conditional" tag is not carried. I don't know if it's like the conditional NBT tag doesn't exist so there's nothing to carry (and if it doesn't, it should) or what, but it's extremely annoying when I'm creating repeating chains of command blocks.
It seems like a bug, so I added it in the bug tracker. Please support it here:
Please support this page in the bug tracker if you're interested in this suggestion.
It's technically not a bug. Ctrl+pickBlock does not store any block data (like the block facing), so it's currently impossible for it to also hold whether the block is conditional.
It's technically not a bug. Ctrl+pickBlock does not store any block data (like the block facing), so it's currently impossible for it to also hold whether the block is conditional.
That is true to an extent. However, it does store its "auto" tag and last output message, the reason why the +NBT lore is added. Ideally, Ctrl+pickBlock should preserve all block data except the block's direction. I support.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhen you CTRL+Middle mouse a command block (or anything that carries NBT data) it will save the information stored inside of it, wether that be always active or the command itself. But here's the thing; the "Conditional" tag is not carried. I don't know if it's like the conditional NBT tag doesn't exist so there's nothing to carry (and if it doesn't, it should) or what, but it's extremely annoying when I'm creating repeating chains of command blocks.
It seems like a bug, so I added it in the bug tracker. Please support it here:
https://bugs.mojang.com/browse/MC-102138
My youtube: https://www.youtube.com/channel/UCO9DtxabZWZpv_k-rsUx7FA
My steam group: https://steamcommunity.com/groups/castlecrashersarmy
It is probably a glitch, but it could be intentional. Try posting this on the bug tracker.
Check out my PvP map Here!
Check out my website Here!Website is down until further notice.I think the reason for this is because conditional is a block state, not a data tag, and thus held by the data value of the block.
But, yeah, this should be put into consideration by the engine.
I Support.
Want to see my suggestions? Here they are!
I am also known as GameWyrm or GameWyrm97. You can also find me at snapshotmc.com
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttps://bugs.mojang.com/browse/MC-102138
Please support this page in the bug tracker if you're interested in this suggestion.
My youtube: https://www.youtube.com/channel/UCO9DtxabZWZpv_k-rsUx7FA
My steam group: https://steamcommunity.com/groups/castlecrashersarmy
It's technically not a bug. Ctrl+pickBlock does not store any block data (like the block facing), so it's currently impossible for it to also hold whether the block is conditional.
Want to see my suggestions? Here they are!
I am also known as GameWyrm or GameWyrm97. You can also find me at snapshotmc.com
That is true to an extent. However, it does store its "auto" tag and last output message, the reason why the +NBT lore is added. Ideally, Ctrl+pickBlock should preserve all block data except the block's direction. I support.
Support
Since this bug should be fixed for the sake of Mac users' enjoyment with Minecraft.