PencilSharpener

Interestingly, using data modify will modify the storage, even if the effects are otherwise identical:

/data modify storage example:temp {} merge value {bar: 123}

(The error still happens, though.)

Also affects Fire Charges from dispensers and Ghast Fireballs (though a Ghast Fireball will at least be able to delete the End Crystal if it hits close enough to the base to where the explosive damage is able to reach it). Happens due to End Crystals now being immune to the entire #is_fire damage type tag, which, of course, includes fireball damage.

Just like (Ghast) Fireballs, Wind Charges have a noticeably larger hitbox for player melee attacks than their actual, displayed hitbox would suggest. This is most likely intentional in order to make them easier to hit back. This hitbox does not seem to be affected in any way by having several of them inside of each other.

Updated wiki link: https://minecraft.wiki/w/Raid#Joining

Wind charges only deal around half a heart, and the minimum incoming damage needed for a shield to lose durability is 3 (1½ hearts), so this seems like it would be intended.

Can also be seen by repeatedly blocking them with a shield. It makes them look like they're just sliding along the floor. (Also, the shield variant of this, at the very least, definitely existed pre-1.20.2. (@RiskEdits))

Relates to MC-260591. What seems to happen is that the cached entity reference to the owner (that used to cause MC-226344) doesn't carry over when the projectile is recreated at the other end of the portal, and then looking up the owner by UUID fails because it's in a different dimension. If you go through the portal yourself before the projectile hits then credit is applied as expected.

It isn't actually infinite, though. It starts counting down as soon as you go underwater (and resets upon resurfacing). Having the timer show infinity when not underwater seems like it would just be misleading.

(also doesn't seem logical to see a duration countdown get reset every X seconds)

Unlike beacons, the turtle shell timer stays firmly locked at 10 seconds until you either start diving or remove it (at least in my experience).

Also applies to execute on owner.

1. Tame a wolf (or cat, etc.).

2. execute as <wolf> on owner run say <message>
   → ✔ The message should appear in chat.

3. Change dimension and run the above command again.
   → ❌ No message appears.

4. (Optional: Run the above command without on owner the verify that the wolf still exists.)

This also seems to make it so that pet death messages do not show up for their owners if their owners are in a different dimension from them. (Not sure if a bug report exists for this.)

Also likely caused by this bug: Lingering Potions thrown through a portal do not properly assign kill credit (nor do they copy their Owner/origin to the created Area Effect Cloud) unless the thrower also travels through the portal before they hit the ground on the other side.

1. Place a named mob* next to a Nether Portal in the Overworld. (*Or another player; anything that'll produce a death message somewhere.) Try to keep it in place to make the next steps easier.

2. Go through the portal.

3. From the Nether, throw a Lingering Potion of Harming (or Healing, if the mob is undead) back through the portal to kill the mob in the Overworld. Throw several if you need to.

4. Check the output log (or latest.log).
   → ❌ <victim> was killed by Area Effect Cloud using magic

5. Redo the above, but after throwing the potion(s) through the portal, quickly go through the portal yourself before they hit the ground. (You'll most likely need to be in Creative Mode for this.)

6. Check the log again.
   → ✔ <victim> was killed by <your username> using magic
   (if you went through the portal fast enough)

Also affects team display names, prefixes, and suffixes. Does not affect bossbar display names.

The light level is probably too low.

This doesn't seem to be fixed for me. If I run /playsound minecraft:entity.enderdragon.death hostile @a ~ ~ ~ 1 1 1 (or /playsound minecraft:record.cat record @a 0 0 0 1 1 1 or anything with a minimum volume set), the sound's volume still decreases as I move.

You also get stuck if farmland reverts to dirt naturally while you're standing on it.

You can actually obtain path blocks by using Pick Block in Creative, though that might be a bug on its own.

JSON formatting became more specific in these snapshots for no apparent reason. Try: /title @p title {"text":"Broken"}

Empty chunks are just entirely broken in this snapshot. They seem to behave almost identically to how chunk errors worked in 1.8.

Empty chunks are just entirely broken in this snapshot. They seem to behave almost identically to how chunk errors worked in 1.8.

Empty chunks are just entirely broken in this snapshot. They seem to behave almost identically to how chunk errors worked in 1.8. (You fall slowly while inside of them, jumping while inside of them seems to make you bump your head on an invisible block, the sky gets darker while you're inside of them, you're invisible inside of them, lighting doesn't work properly in chunks adjacent to them, etc.)

Just so you know, you can use tab completion for the item/block names. For example, typing "comm" and hitting tab will auto-complete into "minecraft:command_block". Also, the "minecraft:" is unnecessary.

"hollow" removes all blocks inside the box while "outline" keeps them.