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

Dying to the warden's sonic boom doesn't count as the warden's kill

XMLWordPrintable

    • Confirmed
    • Statistics
    • Important

      The warden's sonic boom is not attributed to the warden. This means that advancements with the entity_killed_player trigger don't trigger, and the statistic for dying to wardens doesn't increment.

      How to reproduce:

      1. Create a new world. (optional: add the attached datapack that adds an advancement for dying to a warden)
      2. Spawn a warden on the ground in creative mode.
      3. Pillar up 5 blocks with blocks around you so you don't fall.
      4. Give yourself a bow and arrow or a snowball.
      5. Switch to survival mode.
      6. Hit the warden with your projectile.
      7. When the warden comes to kill you, wait until it hits you with its sonic boom.
      8. Let it hit you with its sonic boom enough times to kill you.
      9. Respawn and look at your statistics and advancements.

      What I expected to happen was:

      The statistic for dying to a warden would increment by 1 and the advancement "Adventure" would be granted to me (plus the custom advancement from the datapack).

      What actually happened was:

      The statistic didn't increment and no advancements were granted to me.

      Cause:

      The warden's sonic boom uses the damage source "sonic_boom" which is an environmental damage type, like "cactus" or "hotFloor". If it was a player/mob damage type, like "mob" or "fireball", then it would count as the warden's damage. Before 22w17a, the sonic boom used the "mob" damage type, so it did count as the warden's damage.

        1. MC-250966.mp4
          6.15 MB
        2. MC-250966.png
          MC-250966.png
          974 kB
        3. warden kill.zip
          1 kB

            grum [Mojang] Grum (Erik Broes)
            ManosSef ManosSef
            Votes:
            8 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: