When the new saturation effect came out, I used command blocks to give me hunger points. It seemed like at amplifier 0 for 1 second I got 1 hunger point. When I put the same effect on a potion using NBT editors, even 1 second at amplifier 0 filled my entire hunger bar, when it should act the same as /effect. The issue is that when the command says the effect was applied for x seconds, it was actually applied for x ticks.
Linked issues
is duplicated by 19
relates to 2
Attachments
Comments 21
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Is this still a concern in the current Minecraft version 1.7.4 / Launcher version 1.3.8 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Given the changes to the /weather and /title times commands in 23w03a, perhaps this should be reflected in the title of this bug?
That would make this requesting a change, rather than reporting a bug. This issue is about the value being treated differently based on the effect type, not the lack of t, s and d suffix usage.
relates to MC-139527, which needs to be updated.
The actual issue is that the potion is using ticks instead of the reported "seconds". Observe that a potion at 10 ticks will heal the same as an /effect with 10 "seconds". 1 second is 20 hunger points, while 1 tick is only 1 hunger point.
This issue is present for Instant Health, Instant Harm, and now, Saturation: the command will state that the effect was applied for X seconds, when in reality it was applied for X ticks (1/20 of a second).
Please update your ticket and title to make it clear that the issue is in the command for these effects - custom potions have consistent behavior for all effects, but the command does not.