When an armorstand is summoned with all slots disabled, you cannot use /item replace to modify its chestplate, leggings, or boots slot—though the helmet slot is unaffected
How to Reproduce:
Summon an armorstand with all slots disabled,
/summon armor_stand ~ ~ ~ {DisabledSlots:4144959}Attempt to give it a diamond helmet using /item,
/item replace entity @n[type=armor_stand] armor.head with diamond_helmetAttempt to give it the rest of the set:
/item replace entity @n[type=armor_stand] armor.chest with diamond_chestplate
/item replace entity @n[type=armor_stand] armor.legs with diamond_leggings
/item replace entity @n[type=armor_stand] armor.feet with diamond_boots
It can be seen that the helmet is set appropiately, but all other commands throw the error, "No targets accepted item [Item] into slot 100/101/102"
Expected Behavior:
In previous versions, the /item command would bypass disabled slots entirely. Either way, the behavior should be consistent across the board.
Comments 3
Affects 1.21.7.
The problem seems to come from the remove values (1-32).
Example:
Modifying a armor stand’s armor.chest slot that has DisabledSlots:4144959 (all slots locked) does not work.
Modifying a armor stand’s armor.chest slot that has DisabledSlots:4144951 (all slots minus chest remove locked) does work.
It should be allowed, as /data can edit them anyways. Limiting /item but not /data would be illogical (and limiting /data by itself would be illogical too, since it's supposed to allow modifying everything).