Decomposed transformation sometimes requires all properties to be set
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}}/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}
Whereas the following do work as expected:
- Specifying all four properties:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}}/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}
- Using matrix form:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}
- Modifying a specific property:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2f,2f,2f]
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}
Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}
The entity has the default appearance, and all of its transformation data is set to their default values.
Linked Issues
is duplicated by4
MC-259803cant change scale in text_displayDuplicateMC-260457block_display entities do not inherit transformation nbt data properly from /summonDuplicateMC-260543Can't modify scale of item display at summoningDuplicateMC-267548Summoned Block displays ignore Transformation Nbt values on creation.Duplicate
Created Issue:
Decomposed transformation cannot always be used
When using the summon or data modify commands to summon a display entity, the transformation tag can only be set in the matrix (TAG_List) form, and not in the decomposed (TAG_Compound) form. Using the decomposed form causes an error to be logged, and the transformation values to be set to their defaults.
As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2.0f,2.0f,2.0f]}Whereas the following four do work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2.0f,2.0f,2.0f] /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2.0f,2.0f,2.0f]}}Expected behaviour
The decomposed form can be used in all cases where NBT is used, so all the above commands should work.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When using the summon or data modify commands to s
ummona display entity, the transformation tag can only be set in the matrix (TAG_List) form, and not in the decomposed (TAG_Compound) form. Using the decomposed form causes an error to be logged, and the transformation values to be set to their defaults.As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2.0f,2.0f,2.0f]}Whereas the following four do work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2.0f,2.0f,2.0f] /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2.0f,2.0f,2.0f]}}Expected behaviour
The decomposed form can be used in all cases where NBT is used, so all the above commands should work.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When using the summon or data modify commands to set the NBT of a display entity, the transformation tag can only be set in the matrix (TAG_List) form, and not in the decomposed (TAG_Compound) form. Using the decomposed form causes an error to be logged, and the transformation values to be set to their defaults.
As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2.0f,2.0f,2.0f]}Whereas the following four do work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2.0f,2.0f,2.0f] /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2.0f,2.0f,2.0f]}}Expected behaviour
The decomposed form can be used in all cases where NBT is used, so all the above commands should work.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
Decomposed transformationcannot alwaysbeusedDecomposed transformation sometimes requires all properties to be set
When
using thesummonordata modify commands to set the NBT of a display entity,the transformation tag can only be set in the matrix (TAG_List) form, and not in the decomposed (TAG_Compound) form. Using the decomposed form causes an error to be logged, and the transformation values to be set to their defaults.As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2.0f,2.0f,2.0f]}Whereas the following
fourdo work as expected:/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2.0f,2.0f,2.0f] /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2.0f,2.0f,2.0f]}}Expected behaviour
The
decomposed form can be used in all cases where NBT isused,so all the above commands should work.Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
# Specifying all four properties /summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]} # Using matrix form /summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} # Modifying a specific property /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2f,2f,2f] # Using data merge /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{scale:[2f,2f,2f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
# Specifying all four properties /summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]} # Using matrix form /summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]} # Modifying a specific property /data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation.scale set value [2f,2f,2f] # Using data merge /data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
- Specifying all four properties:
**
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}- Using matrix form:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}- Modifying a specific property:
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
- Specifying all four properties:
**
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}- Using matrix form:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}- Modifying a specific property:
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
- Specifying all four properties:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}- Using matrix form:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}- Modifying a specific property:
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
- Specifying all four properties:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}- Using matrix form:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}- Modifying a specific property:
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
When setting the transformation property in the summon or data modify command in the decomposed (TAG_Compound) form, all four properties are required; otherwise, the entire object is set to default and an error is logged. This requirement does not exist for the data merge command. Setting the transformation property in the matrix (TAG_List) form works as expected.
As an example, the following two commands do not work as expected:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,2f,2f]}Whereas the following do work as expected:
- Specifying all four properties:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[2f,2f,2f],right_rotation:[0f,0f,0f,1f]}- Using matrix form:
/data modify entity @e[type=minecraft:block_display,limit=1,sort=nearest] transformation set value {scale:[2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,2f,0f,0f,0f,0f,1f]}- Modifying a specific property:
- Using data merge:
/data merge entity @e[type=minecraft:block_display,limit=1,sort=nearest] {transformation:{scale:[2f,2f,2f]}}Expected behaviour
The command summons an entity with the specified transformation values set, and the unspecified values set to default.
Actual behaviour
Upon running the command, the following error message is logged by the server thread:
Display entityNot a list: {scale:[2.0f,2.0f,2.0f]}The entity has the default appearance, and all of its transformation data is set to their default values.
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mojang] Moesh](../../../data/avatars/users/10122.svg){kind=small}
is duplicated by
is duplicated by
![[Helper] Misode](../../../data/avatars/users/93314.png){kind=small}
As mentioned in MC-259838
When setting the transformation using the decomposed forms, you need to put all 4 parts, they are not optional. For example this command would work:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:stone"},transformation:{translation:[0f,0f,0f],left_rotation:[0f,0f,0f,1f],scale:[5f,5f,5f],right_rotation:[0f,0f,0f,1f]}}
I'll forward-resolve this as a duplicate of MC-259838, since it's the same issue but that bug report is a lot more detailed.
Duplicate of MC-259838.
Duplicate of MC-259838.
Thank you for your report!
We're tracking this issue in MC-259838, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as working as intended, which means this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
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
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Duplicate of MC-259838, on creation, the whole transformation must be provided in order to be applied.
Thank you for your report!
We're tracking this issue in MC-259838, 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.
When setting the transformation using the decomposed forms, you need to put all 4 parts, they are not optional. For example this command would work:
/summon minecraft:block_display ~ ~ ~ {block_state:{Name:"minecraft:lime_glazed_terracotta"},transformation:{translation:[0.0f,0.0f,0.0f],left_rotation:[0.0f,0.0f,0.0f,1.0f],scale:[2f,2f,2f],right_rotation:[0.0f,0.0f,0.0f,1.0f]}}That's just weird, that also means execute store wouldn't ever work.
It might be weird, but imo requesting that the other fields are made optional would be a feature request. execute store still works, for example:
It's not a feature request though, it's an inconsistency; nowhere elsd in the game do you require to provide other tags when attempting to change one of them.
Interesting. For the data merge command specifying all properties is not a requirement though, it's only summon and data modify.
Code analysis using Yarn mappings:
The codec stored in the AffineTransformation.field_42532 field does not have optional fields, so attempting to parse an incomplete transformation compound will result in an error being logged to the console instead.
This may be WAI. Quite a few players think that's why mojang added /execute summon. Also in the update log it said: (/execute summon is) meant to simplify entity setup and reduce need for raw NBT editing.
To simply summon the entity, we can use
/execute summon <id> run data merge entity @s {transformation:{scale:[4.0,4.0,4.0]}}
But that's just players' guess, and it's up to mojang to decide if it's intentional.
Why exactly is this intended? This is the only NBT to not accept non-full data, all other NBT will set the fields correctly and default the ignored values.
Quote from [Mojang] Bartosz Bok in the Minecraft Commands Discord server (link, 2022-02-12):