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

Respawn anchor doesn’t store its charges when mined with silk touch

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Works As Intended
    • 1.16.3, 1.16.4 Pre-release 1, 1.16.4 Pre-release 2, 1.16.4 Release Candidate 1, 1.16.4, 20w45a, 20w46a, 20w48a, 20w49a, 20w51a, 21w03a, 21w05a, 21w05b, 21w06a, 21w07a, 21w08a, 21w08b, 21w10a, 21w11a, 21w13a, 21w14a, 21w15a, 21w16a, 21w17a, 21w18a, 1.17, 1.17.1 Release Candidate 1, 1.17.1, 21w37a, 21w38a, 21w39a, 21w40a, 21w41a
    • None
    • Confirmed
    • Block states, Parity
    • Normal

    Description

      The bug

      On bedrock edition when you mine a respawn anchor with silk touch, it will store its charges. This is also visible on the texture of the item, when you then place it again, it will still have the charges. However this is not the case in java. On java it will lose the charges when mined with silk touch. According to https://feedback.minecraft.net/hc/en-us/articles/360043896251-Minecraft-Beta-1-16-0-63-Xbox-One-Windows-10-Android-, the bedrock behavior is intentional.

      How to reproduce:

      1. Place a respawn anchor
      2. Charge it with glowstone
      3. Get a silk touch pickaxe
      4. Mine it in survival mode
      5. Place it again
        All of the charges are gone.

      Attachments

        1. MC-200268.mp4
          8.86 MB
        2. MC-200268.png
          MC-200268.png
          388 kB
        3. save_43.mp4
          8.62 MB
        4. Silk Touch enchant works on respawn anchor.png
          Silk Touch enchant works on respawn anchor.png
          43 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              bugsbugsbugs bugsbugsbugs
              Votes:
              15 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                CHK: