Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-267015

Flight speed is miscalculated at high tick rates when using Elytra

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • None
    • 1.20.3 Pre-Release 2, 1.20.3 Pre-Release 3
    • Confirmed
    • Collision, Networking

      If the game is running at a high enough tick rate, the player's speed while flying will be miscalculated causing kinetic energy damage to be applied in incorrect situations.

      Steps to Reproduce:

      1. Tick sprint the game
        /tick sprint 3d
        
      2. Stand on a 3-block pillar, equip Elytra, and switch to Survival Mode if not already in Survival Mode
      3. Fly into a wall which is close enough to not cause damage normally

      Observed Results:

      Despite not traveling far or fast enough to cause kinetic energy damage normally, the player will take lots of damage in quick succession, and often times die.

      Expected Results:

      The player would not take any damage since they are not traveling fast enough to cause kinetic energy damage like in a normal tick rate of 20.

      Screenshots/Videos:

      2023-11-25_12-03-45.mp4

      Notes:

      The expected results can be backed up by the changelog for the /tick rate command, which states that a higher tick rate preserves normal player movement:

      . . . whilesetting a higher tick rate will cause the players to be simulated at the default rate of 20 ticks per second to maintainthe expected responsiveness of the game . . .

      Considering the game is handling the player's movement/speed differently compared to a normal tick rate of 20, this is unusual behavior.

        1. 2023-11-25_11.56.01.png
          551 kB
          [Helper] Jiingy
        2. 2023-11-25_12-03-45.mp4
          667 kB
          [Helper] Jiingy

            Unassigned Unassigned
            Jingy [Helper] Jiingy
            Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: