Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-56031

Hunger bar depletes too fast

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • 1.18.20.25 Beta, 1.18.30
    • 1.18.10.26 Beta, 1.18.0.21 Beta, 1.17.11 Hotfix, 1.17.10, 1.16.230.54 Beta, 1.16.230.52 Beta, 1.16.220, 1.16.220.50 Beta, 1.16.210.58 Beta, 1.16.210.55 Beta, 1.16.210.54 Beta, 1.16.210.53 Beta, 1.16.210.50 Beta, 1.16.200.57 Beta, 1.16.200.53 Beta, 1.16.200.51 Beta, 1.16.100.56 Beta, 1.16.100.54 Beta, 1.16.100.52 Beta, 1.16.100.51 Beta, 1.16.100.50 Beta, 1.16.20.53 Beta, 1.16.20.52 Beta, 1.16.0.68 Beta, 1.16.0.67 Beta, 1.16.0.66 Beta, 1.16.0.64 Beta, 1.16.0.63 Beta, 1.16.0.61 Beta, 1.16.0.60 Beta, 1.16.0.59 Beta, 1.16.0.57 Beta, 1.16.0.58 Beta, 1.16.0.55 Beta, 1.16.0.53 Beta, 1.16.0.51 Beta, 1.15.0.56 Beta, 1.13.0, 1.14.30 Hotfix, 1.14.60 Hotfix, 1.16.0, 1.16.1, 1.16.10, 1.16.21, 1.16.20, 1.16.40 Hotfix, 1.16.100.59 Beta, 1.16.100, 1.16.200, 1.16.201 Hotfix, 1.17.2 Hotfix, 1.17.30, 1.17.34, 1.17.40, 1.18.0, 1.18.2 Hotfix, 1.18.10
    • Survival
    • Confirmed
    • Multiple
    • 369851

    Description

      The hunger bar drains way too quickly.
       

      Updated description by Doubletoad74:

      The following is a list of the current exhaustion points given when performing an activity. Every time an action is performed, it's added to a counter for the player performing it. Once this counter is greater than or equal to 4, the number is completely reset to zero, and one saturation point is taken from the player. However, if the player has no saturation, one hunger point is taken instead.

      Jumping: 0.4
      Breaking Blocks: 0.025
      Sneaking: none
      Walking: none
      Sprinting: none
      Swimming: none
      Sprint Jumping: 1.6
      Attacking: 0.3

       
      As shown above, Bedrock's exhaustion system is very similar to Java's system before 1.11 (Java's Exploration Update released in November 2016; not Village and Pillage), however there are a few differences.

      First of all, it is completely impossible to gain exhaustion by sprinting or swimming at all, thereby making it impossible to lose both saturation and hunger when performing only those actions.

      Steps to Reproduce

      1. Create a flatland world with doDaylightCycle disabled and doWeatherCycle disabled in Survival Mode (cheats are required here)
      2. Sprint forward for any amount or time

      Here, the player does not lose any hunger whatsoever. The same can be said for swimming in the proper circumstances (pretty much swimming in an ocean for any amount of time).

      Second of all, jumping while sprinting is twice as painful as Java's pre-1.11 values, prompting 3 sprint-jumps per half of a hunger bar (I'd assume this is the focus of this ticket, given the name "Hunger bar depletes too fast", but I'll leave the previous information in for vanilla-parity).

      Steps to Reproduce

      1. Recreate a world with the same attributes as the flatland from the earlier list
      2. Sprint and jump at the same time until 3 hunger bars remain

      Here, when assuming the player starts with both 20 (max) hunger and 20 (max) saturation, the player is only allowed to sprint-jump 102 times from worldspawn. In Java's pre-1.11 on the other hand (taking into account that the player starts with 20 hunger and 5 saturation), it was 95 times. Today in Java's 1.15 (with the same hunger and saturation levels), it's 380 times.

      Attachments

        Issue Links

          Activity

            People

              Magicalfoot215 eythan
              Votes:
              124 Vote for this issue
              Watchers:
              52 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                CHK: