mojira.dev

AjaxGb

Assigned

No issues.

Reported

MC-176038 Lodestone compasses in containers do not become unlinked when lodestone is broken Duplicate MC-176029 Right clicking a lodestone with a stack of compasses converts the whole stack Fixed MC-175514 Villager Gossips still use old UUID NBT format (TargetMost and TargetLeast) Fixed MC-173476 Piercing arrows pass through level+1 entities, vanish without damage when hitting level+2 Confirmed MC-152737 Summoned falling_block entities will incorrectly delete client-side blocks Duplicate MC-146881 Sleeping villagers have a much smaller render radius than normal Confirmed MC-138426 Not all CustomModelData values can be checked by predicate, due to floating point imprecision Won't Fix MC-138299 /loot mine and /loot kill ignore container contents, armor items, and other non-loot-table drops Confirmed MC-137427 Advancements treat the player as the "direct_entity" source of primed TNT damage Confirmed MC-126809 minecraft:exploration_map loot table function only works on block containers Fixed MC-121977 Data packs other than vanilla start with "file/" Works As Intended MC-121975 Datapack order does not persist after a world is closed Fixed MC-121897 Gaps in an animation's used frames throws ArrayIndexOutOfBoundsException Fixed MC-121692 Many commands break on unquoted special characters, quoting support inconsistent Won't Fix MC-116388 Chain command blocks can clone themselves to create an infinite loop which freezes the server Fixed MC-107846 Evocation Fangs hurt illagers after reload Fixed MC-94670 Bat subtitle is misspelled ("squeeks") Fixed MC-94576 (Player) Head in inventory causes buggy rendering of certain inventory slots, potion effect display and attack cooldown Fixed MC-94566 Breaking non-container comparator-enabled blocks doesn't send a comparator update through blocks Confirmed MC-93276 Mobs steered by passenger Slimes walk to 0,0 Fixed

Comments

Can confirm in 24w06a.

@@unknown Eight-year-old comment, but it seems to me that the "correct" solution would be to do attribute application in two passes. First, go over all the slots as you described, but only process item removals. Then go over all the slots a second time and process all the item additions.

Can confirm in 1.17

Did some digging on this. Turns out Striders set their NoGravity flag to true when they're in lava and to false when they aren't; that's how they float. Certain things can make the flag get stuck on true. A consistent and easy one is just saving and quitting while the Strider is standing in lava. After you reopen the world, the Strider is stuck floating at their current height forever. The flag being stuck like this also prevents them from walking up blocks, which they can normally do.

This also relates to MC-176203, as the NoGravity flag prevents levitation. Striders probably shouldn't be using that flag; it's mostly intended for command use only.

@violine1101 I actually don't think that's a duplicate. That bug is about how, when the lodestone is broken, the compass is still a Lodestone Compass, just a Lodestone Compass that points to nothing. This bug is about how, when the lodestone is broken, compasses in containers won't notice at all, and will continue to point to the lodestone's old location until they are placed back into the player's inventory.

Confirmed for both 1.15.2 and 20w07a.

 I was unable to reproduce in 1.15.2. Seems to be resolved.

Confirmed for 1.14.4 and 19w41a.

I suspect that this is happening because villagers have a much smaller hitbox while sleeping.

Confirmed for 19w04b.

Confirmed for 18w32a, with the upper limit of distance= in place of r=. Setting only the lower limit has no effect, so

distance=1000000..

will not trigger the bug, but any of

distance=1000000
distance=..1000000

will.

And for 18w32a.

Confirmed for 1.13.

@Cody
It's a block tag. It can be set with datapacks.

Confirmed for 1.12.2 and 1.13-pre5.

Confirmed for 18w16a.

Confirmed for 18w10d.

"any block with block states will always fail to match in a command argument"

Not true; that wool example will detect white wool just fine. The problem is that, instead of missing blockstates using the default value when setting and accepting any value when testing, they just always use the default value.

Confirmed for 1.12-pre5.

So does that mean that there's now a maximum chain length? If so, what is it?

@unknown Thanks for the correction.