I created my own behavior pack, and in this behavior pack I created my own type of cake and for the cake to saturate you I had to use the "minecraft: on_interact" component and an event in which I added the command "effect @e [type = player] saturation 1 1 true" and everything before 1.17.30 worked fine, so after eating a cake, one hunger recovered, but now after 1.17.30, after eating one piece of cake (a cake made by me), the whole bar replenishes immediately, and it shouldn't work that way. In my opinion, the fault is on your side, not mine, because everything worked fine before version 1.17.30.
On Minecraft 1.17.10, everything worked fine.
Comments 4
@@unknown I found a problem with why this is happening and it was the fault of the program I made the addon in, because now I moved it to another program, or rather to its second version, and now everything is fine.
The program I used was bridge and now I used bridge v.2.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Is this still an issue in the latest version? If yes, can you please add it to the affected versions (or mention it if you are not the reporter)?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Still broken in 1.18 betas
The issue occurs when running the effect command with the run_command component for events, any effect that uses ticks for time (instant damage, instant health, saturation) uses seconds instead, whereas from a regular command (not part of an event, just run from the command window) use ticks for time correctly.