PvPqnda
Assigned
Reported
MC-278618
Crossbows loaded with something other than an arrow still fires an arrow
Duplicate
MC-261319
Gamemode Switcher icons duplicate upon toggling fullscreen
Duplicate
MC-260454
Decorated pots are translated off-center when displayed on head
Fixed
MC-259877
Text displays with no text still render a small background
Works As Intended
MC-259830
/damage isn't compatible with /execute store result
Invalid
MC-259823
Inconsistencies with Text Display opacity
Confirmed
MC-259448
Trim item model overlays conflict with base textures
Duplicate
MC-259395
The "/stopsound" command doesn't remove subtitles
Works As Intended
MC-258402
Armor Stand arms aren't aligned correctly with some poses
Community Consensus
MC-253534
Gamerule "reducedDebugInfo" doesn't affect chat entity selector hover text
Invalid
MC-252476
TNT doesn't damage players
Invalid
MC-238932
Micro biome in 21w41a
Duplicate
MC-230433
Scoreboard objective "minecraft.used:minecraft.name_tag" doesn't function
Duplicate
MC-227502
Spectating positioning is offset with marker armor stands
Duplicate
MC-225892
The hook of a cast fishing rod does not match the item texture
Community Consensus
MC-225890
Potion effects don't affect player FOVs when the player is spectating an entity
Confirmed
MC-151165
Sprint By Pressing Sneak Twice
Duplicate
MC-140998
Advancement Not Working
Duplicate
Comments
ah, yes. didn't find that ^
can confirm
The suspicious sand generates underneath the temple in a new sand-filled room.
While inside a desert temple, run this and go into spectator mode to identify the replaced blocks underground:
/fill ~15 ~15 ~15 ~-15 ~-15 ~-15 conduit[waterlogged=false] replace suspicious_sand
this is definitely intended
Should I add this as feedback on the feedback site, or has this already been accounted for in that regard?
This is not a bug, things just aren't being ordered correctly.
I was experiencing this too, but the other way around. My custom material was being overridden by the highest index value (amethyst) but only because I didn't have things ordered correctly and I was neglecting the "blocks.json" atlas.
I recommend following Misode's guide, it allowed me to discover something I was missing.
https://misode.github.io/guides/custom-armor-trims/?version=1.19.3#adding-a-custom-trim-material
Can confirm in 1.19.3.
Just stumbled upon this bug myself. Made me very confused as to why my functions weren't working properly for a couple days before I realized this command simply just wasn't working. But I've found for the time being, an easy fix is instead of running /data remove entity @s CustomName, use /data modify entity @s CustomName set value ''
Can confirm in 1.19
My mistake, I was completely unknowledgeable to this peaceful difficulty feature.
Can confirm is a bug in 1.18.
Unfortunately, yes