As far as I can tell, ``/data remove`` does not work.
There are a slew of bug reports about it not working for specific things, such as
In fact, I have yet to find anything on which the command actually does work, though I'm sure there are some somewhere – you must have unit tests that work at some level.
What I suspect is that the pattern of these bugs not been noticed as a general problem, just as a bunch of individual, low priority issues.
What I expect is that either remove works, or it is removed from the doc as not really part of the command if you're not going to fix it.
Comments 4
Thank you for your report!
However, this issue is Invalid.
Please put only one bug report in each ticket. It is very difficult to keep track of bugs when they are not in their own tickets.
However, please review the Bug Tracker Guidelines before creating new reports. Be sure to search for an existing issue as it is likely to have already been reported.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
You have no way of reporting a common problem that spans multiple bugs? Large scale problems that have been reported only at smaller scales may not be noticed? Reported?
Since /data remove does not work, there are hundreds of individual bugs that could be logged by someone with the patience to do so. Or you could be made aware that there is a systemic problem lurking among the others.
But you won't accept that?
Again, /data remove works just fine, with the exception of some tags; each one of the tags that it does not work for needs their own fix, and is their own issue.
Only if there's a single problem that causes symptoms, then it is supposed to be 1 report. If it is instead different problems wich result in the same or similar effects, each needs its own report and the reports are marked as related instead.
Do note, that while the tag is removed in all "normal" cases, some tags are always saved (eg the Items list of a chest always exists), removing it will delete it, and default it to the normal value (in the Items of a chest's case, an empty list).
Either you are using the command incorrectly, are seeing the defaulting behaviour and not understanding it, or are only testing the few fields which are bugged.
/data remove entity @e[type=item,limit=1] Item.tag.display.NameRemoves the item name of the first-found item entity just fine./data remove block ~ ~ ~ Itemsremoves the block's "Items" list (eg a chest's contents) just fine.removes that storage data's "indexes" field/object/list/array just fine.
Please do not create "collection" reports for other individual issues.
Please do verify you are using the commands correctly when reporting issues with commands.
Please do thuroughly test what you are reporting.