Megabobster

Thank you, I was unable to find that by searching for some reason.

Affects 1.18.1, and I think it's worth noting that if the photo viewer that Minecraft opens crashes it will take Minecraft with it.

Still present in 1.18.1; I think I was mistaken or confused in my testing methodology when I thought it had been fixed before. Should either this or MC-151793 be closed as duplicate, since it seems like it's the same core issue?

To summarize: any banner with a pattern (not just ominous banners) that has not yet been placed seem to erroneously have an additional NBT tag that is lost when it's placed in the world, which prevents them from stacking. I think this is most easily seen by reproducing the bug and running /data get entity @p

To reproduce: craft two blank banners of any color. Use a loom and some dye to add a pattern to one, then use a crafting interface and the blank banner to copy it. They will stack. Place and break one of them, and they will no longer stack. If the banner does not have a pattern, they will still stack, and if the banner is placed and broken before copying it, they will still stack.

I think this may have been fixed. Now it seems like they correctly push away from panes (both flat and corner) instead of clipping through them. I haven't been able to substantially test clipping on solid blocks, but I haven't noticed anything incorrect. The only situation when they can clip through a pane is when there's a block behind it that makes the space available smaller than their inflated hitbox, so I think clipping through in this scenario would be expected behavior.

Behavior is unchanged in 1.18.1

Behavior is unchanged in 1.18.1

1.14.3pre4?

Affects 1.14.3pre3

To clarify on reproducing this bug:

• The player's inventory must be full.

• Shift-clicking a recipe must make some amount of empty space in the inventory.

• The player must then pick up items which fill that empty space.

• Those items that are picked up into the empty space will be deleted if the player shift-clicks the recipe again, but the recipe book will spread out the items on the crafting interface as if they all still existed.

I cannot find a way to reproduce this without creating an empty space in the inventory. If shift-clicking the recipe does not create an empty space, the items on the ground will simply top up any stacks you have, which then seems to correctly(?) prevent shift-clicking the recipe more. Also, the type of item used doesn't seem to matter.

Duplicates MC-152182?

Relates to MC-63010, MC-152035, and MC-151793.

Possibly relates to MCCE-4796, but of course that's a different codebase etc.

I made a test case; I was able to reproduce this bug in 1.14, but not in 1.14.2. I think this is now fixed. The fix doesn't affect banners previously obtained, but all new banners stack properly. Placing and breaking misbehaving banners seems to fix them.

To test:

• Put at least one pattern on a banner

• Rename it in an anvil

• Copy it in the crafting interface

• Place and break the banner

In 1.14, after breaking, it wouldn't stack with the other banner. In 1.14.2, it will stack as expected. I updated the 1.14 test world to 1.14.2, placed the banner that wouldn't stack, broke it, then it stacked as expected.

This is, of course, assuming that it's the same issue that affected Ominous Banners. But considering those can also be fixed by placing and breaking them, I think it is.

Duplicates MC-140565

This issue also affects 1.14.3pre2. I've attached the images from my duplicate issue (MC-154078) as I think it's the simplest way to reproduce this bug.

Oops, that's what I get for forgetting to search!

This bug might relate to MC-1555, MC-122000, MC-152996, and their other related bugs.

This bug doesn't seem to be exclusive to ominous banners. I made a banner, duplicated it twice (3 total) and one of them wouldn't stack with the other two. I might have placed and broken the banner before trying to stack it, I don't remember the exact sequence of things. I'm running 1.14.2pre4.

Might relate to MC-1555, MC-122000, and their related bugs.

I think the only thing that would change is that you'd have to do one durability of damage. And maybe I'm thinking about it wrong, but would that not end up being a waste of materials? I'm thinking that at the point this would be useful, you're already making a new item to remove the enchantments from the other.

Confirmed for 1.13; a pufferfish clipped through a stone brick slab above it when it puffed up.

I've confirmed this for 1.13 by putting execute as @e[type=minecraft:lightning_bolt] run say foo in a repeating, always on command block, then running summon minecraft:lightning_bolt. Any other entity would result in that entity saying "foo" in chat, but the lightning bolt doesn't.

However, I'm pretty sure this is WAI.