watl
Assigned
Reported
MC-260557
Ice is not part of the #overworld_carver_replaceables tag, causing carvers to not cut through it
Confirmed
MC-256631
Floating Hanging Signs
Duplicate
MC-252426
Some sculk family blocks does not have an animation
Invalid
MC-252259
The sculk shrieker have a bigger hitbox
Duplicate
MC-252258
Wool block / carpet items generate vibrations, unless thrown by crouching players
Fixed
MC-252125
The ores in beacons are not perfectly alined
Duplicate
MC-252094
Block animations does not stop in the pause menu
Duplicate
MC-252092
sculk does not spread under non-full blocks .
Duplicate
MC-251980
Since 22w15a the warden's melee attack range reset even after fixing the bug
Duplicate
MC-251937
The warden does not pathfind correctly
Duplicate
MC-251912
sculk blocks does not let nearby sculk sensors know about wool placement
Invalid
MC-251910
armor wearing sound plays when the armor gets damage
Duplicate
Comments
This seems to only occur in creative mode
This seems to be fixed in 1.19.4-pre 1
so pleaaase everyone vote for this issue
i wanted this to be fixed from a long time
also i wanted to make the sculk shrieker hitbox similar to the bedrock edition one
does voting for issues make them faster to be inprogress?
Thanks
please tell me where to request a change.
ok thanks
i have another question:
is assigning the ticket necessary??
is this a confirmed bug??
did'nt notice this
beacause you have to always sneak in the deep dark
this issue issue is finally fixed in 1.19 pre-release 4 (or 1.19 release candidate 1)
please fix this bug please
this is so confusing
he talks about this experimental snapshot feature from the changelog :
When wool blocks are placed on a sculk block, it will let nearby sculk sensors know, preventing that vibration from being occluded .
but no this tag was removed in 22w11a and thats the first change i noticed in that snapshot
good idea
i think you are using the missing chunk fix resourse pack (from vnilla tweaks) in the ocean of 1.18 panorama
is this a new world or an updated one
if updated then this is not a bug
i also did the same bug report but the devs said that changes from the 1.19 experimental snapshot does not count as a bug
THE DEVS WILL NOT ACCEPT YOUR BUG REPORT
can confirm in 1.19 pre-release 3
Can confirm in 1.19.3