sher1bot
Assigned
Reported
Comments
Confirmed for 1.21.3 - screenshot included. has this really been a problem for Five Years now???
[media]rooting through the files and i can confirm the file analysis in the original post - for example, waxed chiseled copper. from honeycomb is grouped in group "waxed_chiseled_copper", but crafted with slabs is in group "waxed_cut_copper_chiseled". this seems like a pretty easy fix???
still a problem in 1.21! waxed copper bulbs and waxed chiseled copper don't stack their recipes properly!
(also, probably not related, but wouldn't it make more sense to have the "waxed [x weathering] [copper block]" recipes stack? like, all the waxed cut coppers of different weatherings. like how wood recipes stack for all of the different kinds of wood. i think that would be better organized but shrug)
hi, just wanted to add that this bug is still happening in 1.21.1? and it feels like it shouldn't work like that, especially since several villages come with carpets in them now. i just found a villager in an ice biome who couldn't get to their jobsite because there was carpet in the way. they can walk on them if there's 3 blocks, but not 2? i would like it if this was fixed. it feels a little bit silly
just ran into this bug in 1.21.1!
Okay i will do that. here are my rough steps
Steps to reproduce:
1. go into the ocean ? any ocean biome
2. find some blocks underwater. like a hill or a structure or an island or something
3. break blocks so that a block that was previously solid is now filled with water on all sides
4. enter that block that's surrounded by water source blocks
5. open the F3 menu and observe the "targeted fluid" blockstate
observed results: it is flowing water while surrounded by source water on all sides
expected results: the source water around the sides should make it a source water block . and stop flowing
no datapacks or commands or anything this was in regular old vanilla. i hope this helps
i did some additional testing in creative mode - for some reason, it's trying to pathfind to ... Above the block?
[media]when i break the block it's pathing to, it's able to claim the job block, too. how odd!
[media]as the bug report says, when you break the block above the job block, the villager has no trouble at all. but it seems like when there Is a block above it, the villager attempts to pathfind to the top of the block on top of the job block??
exhibit C: villager pathfinding to above the job block
[media]i have NO idea what could cause this kind of bug. but i've experimented with it! i hope this data helps 🙂