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

Elytra Glide State Not Cancelled During Creative Flight

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.20.12 Hotfix
    • None
    • Unconfirmed
    • Nintendo Switch

      Bug Description: In the latest version of Minecraft, a bug has been observed where the Elytra glide state is not cancelled when flying in Creative mode. Normally, when flying in Creative mode, the Elytra glide should be cancelled, but this issue prevents the glide state from being cancelled while in Creative flight.

      Steps to Reproduce:

      1. Update Minecraft to the latest version.
      2. Start the game in Creative mode and obtain an Elytra.
      3. Equip the Elytra and initiate gliding.
      4. Perform Creative flight while maintaining the Elytra glide state.

      Expected Behavior: When performing Creative flight, the Elytra glide state should be cancelled. The glide should be discontinued as usual during flight.

      Current Behavior: Even during Creative flight, the Elytra glide state remains active and is not cancelled, allowing the glide to persist.

      Impact: This bug limits the means of cancelling the Elytra glide state for players, potentially affecting the flight experience. Particularly during architectural or exploratory activities in Creative mode, the unintentional persistence of the Elytra glide state can be inconvenient.

      Proposal: I kindly request the development team to address this issue and ensure that the Elytra glide state is correctly cancelled when performing Creative flight. Swift resolution of this matter would enhance players' flight experience and contribute to a smoother gameplay. Your prompt attention to this bug report is greatly appreciated.

            Sabakan809 Sabakan809
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: