The previous update this worked on was 1.20.2
So this bug is back for 1.14 pre release 5. Do we Submit new bug report or reopen this one? Tested in creative and survival, normal arrows shot when relogging in will have particles emitted from them.
Up to current snapshot 19w14b
Still an issue. Was hoping the new texture update would highlight it more, I guess not.
This is still a problematic bug to going into 1.14 release. I understand that most hardened creators may not come across this issue working with functions or pasting everything into command blocks but some of us like to again select text in game larger than the visible text box.
And I thought I was doing something wrong. Good to know it's only a bug.
Question: is this the same bug that affects opening a book in the off-hand that ignores selectors?
Can confirm issue. Surprised this has not been assigned or up voted as it will break all adventure maps that require any right click action in close proximity to a block.
@Charlene You can also beat a chicken to death with the rod, or just use an xp farm of any sort but issue still remains that no mending while fishing defeats the purpose. I did enjoy killing chickens with a rod though while testing.
Still issue in 1.12 pre-7
It appears this issue also affecting command given books incorrectly displaying scoreboard and entity selector syntax if opened for first time in off-hand. Tag {resolved:#} also incorrectly triggers to 1 in offhand when clearly not resolved.
Still an issue in 17w13b.
Arrow texture still incorrectly mirrored in snapshot 16w50a
Texture still an issue in 16w44a.
Still deep child villager zombie sounds 16w44a.
Arrow texture still not correctly mirrored in snapshot 16w42a.
Ok bug closed as invalid but why is it linked to MC-55516?
This bug was in regard to head and held items not rendering, even on normal villagers custom head and held items render. This was not in reference to armor not rendering, I know normal armor slots are not on villagers.
Thank you Skylinerw for pointing out this is not a bug but a feature that Creeper NBT:fuse can not be tracked and expected to work like TNT NBT:fuse. Now the question is what NBT are we to track for Creeper fuse count down? Otherwise I guess we now have to suggest a real creeper fuse on Reddit and hope next year it gets added.
still affects 15w47a
I'm getting this too on signs and placed skulls as well as chests, but oddly only at certain viewing angles.
Sorry FVbico I don't see how it could be intended, there are many texture UV mapping issues in the game that are more visible when higher detail resource packs are used. Fixing the texture UV mapping for the arrow doesn't make anything harder for the game.
Sorry for my delayed correction to this bug report, {resolved:0b} is not in the normal generation of a written book. {resolved:1b} only generates after a book is read. However in the 1.20.2 version, when adding {resolved:0b} into custom nbt in the /give commands, the read book would replace the '0b' with the '1b' and be able to be identified in data get commands.
With custom NBT move to custom_data, {resolved:0b} can not be placed in a /give command and be detected as changed state because the normal {resolved:1b} is not custom_data and the placement of the {resolved:0b} in the original posts' command is not saved as part of the written_book components.