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

At high tick rates item charge animations do not match the power or charge time of the item usage

XMLWordPrintable

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

      The animation for charging certain items (such as the trident, crossbow, and bow) do not properly reflect how long it actually takes to charge/use that item at high tick rates

      Steps to Reproduce:

      1. Tick sprint the game to run it as quick as possible
        /tick sprint 1d
        
      2. Charge a crossbow, bow, or trident for as short as possible, and fire it.

      Observed Results:

      As expected, the item will be usable very quickly due to the high tick rate, but the charge animation will not properly reflect how powerful the usage is. Instead, the item will have a full power usage with only a brief charge time.

      Expected Results:

      The animation would properly reflect how powerful the usage of the item actually is.

      Screenshots/Videos:

      2023-11-25_12-35-35.mp4

      Notes:

      1. The charge time animations for all the listed items behave as expected when using a tick rate which is lower than 20 (They are animated slower, and properly reflect the charge time and power of the usage)
      2. The crossbow is a special case with this issue, and could be considered a change request considering the animation reflects how long it takes to load an arrow rather than how long it takes to fire.
      3. The resolution of this issue could go one of two ways. Either the item charge animation would need to varry depending on how quick the game is running above 20 ticks, or the item should be used the same as at a tick rate of 20.

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

              Created:
              Updated:
              Resolved:
              CHK: