Can confirm in 1.21.3
If it's only working on a single player, it's likely you're using the wrong selector (@s, @p, etc) for your situation.
In the future, I'd recommend posing your issue on a command block/ datapack help forum rather than making a bug report since it's likely an issue with your command logic rather than a bug.
Does not affect 1.19.3
No longer an issue in MC 1.19.3
Affects 1.18.2
This absolutely should be fixed, I was scratching my head for ages trying to figure out why it wasn't showing up, came here to report, but found this thread.
Not criticizing the devs, I get why they made it this way, but from getting iron/ gold would make a whole lot more sense
Affects 1.17.1
It's still best to reproduce it in a vanilla setting, if possible
Are you on a server? Because server lag can cause the eating animation and sounds to end before the food has been consumed
I assume your ticket was taken down as it's an experimental snapshot, bugs are to be expected as it is still in development. The bug tracker is only intended to track completed versions or snapshots.
Although if I'm wrong and this is a valid ticket than try and leave some extra information such as the world seed, screenshots and/or video and also a screenshot with the F3 screen up
I believe feature requests are not allowed in the bug tracker, only things that are not working as intended.
I've added a video that was created in a vanilla world, with a vanilla client and on a single player world
The server is completely vanilla, the client is modified with optifine
But I assume that statistics are calculated serverside so my modified client should not affect results
https://minecraft.fandom.com/wiki/Statistics
From the official minecraft wiki:
"Statistic related to the number of blocks a player mined. Players' statistic increases when the player mines a block of the specified type. It never increases for a player in Creative Mode."
Turns out that this is how it is intended to work. I would delete this report if I knew how to
I agree that this is a bug and should be fixed. For those encountering the same issue in this report, I suggest that every storage you create has all data points under a single tag e.g:
that way the storage can be deleted using /data remove ~ root_tag