-
Bug
-
Resolution: Unresolved
-
None
-
1.13.0.13 Beta, 1.18.12 Hotfix, 1.20.50, 1.20.62 Hotfix
-
None
-
Confirmed
-
Multiple
-
725640
According to the wiki, giving a player the Saturation status effect should instantly replenish (1 x level) hunger and (2 x level) saturation, then repeat this every tick for as long as the effect lasts. But in Bedrock, it never replenishes any saturation points.
Steps to Reproduce:
- Create an empty flat world with cheats enabled. For convenience, I recommend turning off mob spawning, daylight cycle, and weather cycle.
- Open the world and sprint-jump until at least 1/2 haunch disappears from your hunger bar. Notice that your hunger bar begins "twitching", indicating that your saturation value is at 0.
- Execute the command /effect @s saturation as many times as necessary to restore your hunger bar to full, then an additional 5 times. This should leave you with at least 10 points of saturation (according to the wiki).
Observed Results:
The hunger bar continues to twitch, indicating that your saturation value is 0. If you resume sprint-jumping, your hunger bar immediately loses 1/2 haunch, which should only happen if your saturation value is 0.
Expected Results:
You should have non-zero saturation value, so your hunger bar shouldn't twitch and you should be able to sprint-jump without immediately losing hunger value.
Additional Information:
- This behavior also occurs if you eat a suspicious stew made with a dandelion or blue orchid, though the stew has food value that separately adds 6 hunger and 7.2 saturation value so it's more difficult to demonstrate that the status effect it applies only affects food and not saturation.
- The /effect command allows optional parameters for effect duration in seconds and level. The defaults for these, based on the command output in the chat window, are 30 seconds and 0 level. However, neither parameter appears to affect the results as expected: The duration apparently is measured in ticks rather than seconds, and the level doesn't seem to have any effect at all as far as I can see. I don't know whether this is WAI (with the prompt in the command being wrong) or a bug, and in the latter case whether it should be separately reported, but I intend to see what results from this report before reporting it separately.
Original description:
Saturation (status effect) is supposed to grant levelx2 points of saturation for every tick it lasts. However, it does not.
- relates to
-
MCPE-151871 Dying Doesn't Reset Saturation
- Resolved