A nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and n (+nbt) display for tooltip of (a copy of)×n a block have an "Items" block data
How to reproduce
- Copy a command block/crafter's nbt.
- Place the block in your main hand.
- Change last placed command block's text.
- Copy its nbt.
- Place the block in your main hand.
Observed result
The placed block's text will be the text of the block copied in 1.
There are two (+nbt) in a crafter in the main hand's tooltip.
Linked Issues
is duplicated by6
relates to3
Created Issue:
Sometimes the command block's nbt becomes the content of that which was in that location in the first place.
Sometimes the command block's nbt becomes the content of that which was in that location in the first place.
Sometimes the command block's nbt becomes the content of that whichwas in that location in the first placeSometimes the command block's nbt becomes the content of that which placed first
Sometimes the command block's nbt becomes the content of that whichplaced firstSometimes the command block's nbt becomes the content of that which copied first
Sometimes the command block's nbt becomes the content of that which copied firstThe command block's nbt becomes the content of that which copied first
The command block's nbt becomes the content of that which copied firstSometimes the command block's nbt becomes the content of that which copied first
Sometimes the command block's nbt becomes the content of that which copied firstThe command block's nbt becomes the content of that which copied first
relates to
The command block's nbt becomes thecontent of that which copiedfirstThe command block's nbt becomes the same as the first copy
The command block's nbt becomes the sameas thefirst copyThe command block's nbt becomes the same when it was first copied
The command block's nbt becomes the same as when it was first copied
The placed command block's nbt becomes the same as when it was first copied
The placed command block's nbt becomes the same as when it was first copiedA copy of a copy of a command block is absolutely a copy of the original
A copy of a copy of a command block isabsolutelya copy of the originalA copy of a copy of a command block is ABSOLUTELY a copy of the original
A copy of a copy of a command block is ABSOLUTELYacopy of the originalA copy of a copy of a command block is ABSOLUTELY the same as the first copy of the original
A copy of a copy of acommandblock is ABSOLUTELY the same as the first copy of the original
A nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original
A nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and two (+nbt) display for blocks have a item slot
A nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and two (+nbt) display for blocks have a item slotA nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and two (+nbt) display for tooltip of blocks have an item slot
How to reproduce
- Copy a command block/crafter's nbt.
- Place the block in your main hand.
- Change last placed command block's text.
- Copy its nbt.
- Place the block in your main hand.
Observed result
The placed block's text will be the text of the block copied in 1.
There are two (+nbt) in a crafter in the main hand's tooltip.
A nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and two (+nbt) display for tooltip of blocks have anitemslotA nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and two (+nbt) display for tooltip of blocks have an "Items" block data
A nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original andtwo(+nbt) display for tooltip of blocks have an "Items" block dataA nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and x (+nbt) display for tooltip of xth copy blocks have an "Items" block data
A nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original andx(+nbt) display for tooltip ofxth copyblocks have an "Items" block dataA nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and n (+nbt) display for tooltip of (copy of)×n blocks have an "Items" block data
A nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and n (+nbt) display for tooltip of (copy of)×n blockshave an "Items" block dataA nbt copy of a nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and n (+nbt) display for tooltip of (copy of)×n a block have an "Items" block data
A nbt copy of anbt copy of ablock is ABSOLUTELY the same as the first nbt copy of the original and n (+nbt) display for tooltip of (copy of)×n a block have an "Items" block dataA nbt copy of a block is ABSOLUTELY the same as the first nbt copy of the original and n (+nbt) display for tooltip of (a copy of)×n a block have an "Items" block data
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Isn't this your other report, MC-270413?
Both describe that when copying NBT from a command block, it's the NBT of the original not the one you copied
After closer examination, I found the cause of MC-270413 and the causative phenomenon did not occur in 1.20.4. I think that is separate from what BugTracker added that it occurs in 1.20.4. This was reported as a different bug from that one, which is what that person added to the report.
From what I'm understanding though both of these reports show exactly the same issue, which is why I'm having a hard time understanding any difference between the two.
If MC-270413 doesn't happen in 1.20.4 then why was this bug report made indictating it does happen. If it is the same issue then 1.20.4 can just be added to the affect/s versions list, a new report is not needed.
Greymagic27, MC-270413 is a bug that results in a copy of the first original but this is a bug that results in a copy of what was there in the first place. I was mistaken about MC-270413 at first and thought it was because of what was there first then, and later found out after further investigation that the phenomenon that happened to my game was different from what BugTracker was talking about.
Does MC-270413 describe your issue?
Thank you for your report, I'm resolving this as a duplicate of MC-270413 then.
Thank you for your report!
We're tracking this issue in MC-270413, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MC-270413, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Does MC-270474 or MC-270413 descrbe your issue?
Please also be aware of https://bugs.mojang.com/browse/MC-270187?focusedId=1315195&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1315195 which means that any command blocks you currently have placed may still be affected by the issue
Thank you for your report!
We're tracking this issue in MC-270413, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MC-270413, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Can confirm, this happens sometimes, also affects 1.20.4.
Thank you, BugTracker. Also added 1.20.4 to Affect version/s.
AppleSW No worries
Does
MC-270187describe your issue?Graymasic27, no. But I think this bug is due to
MC-270187being fixed.Sorry, BugTracker. Upon closer examination, I found the cause of this bug and the causative phenomenon did not occur in 1.20.4. I think this is not what you were referring to. I reported it as another bug-
MC-270474.This doesnt seem fixed, I still have this problem
Note that existing Command Blocks created in 24w14a through 1.20.5-pre1 will still have this issue - newly created ones will function correctly.