Isaac King
Assigned
Reported
View all
MC-296822
Vibrations don't render when generated more than than 32 blocks from the player
Won't Fix
MC-296706
Vibrations don't render in correct location
Awaiting Response
MC-296705
Vibrations teleport on world reload
Awaiting Response
MC-296182
Wool's vibration occlusion is direction and position dependent
Community Consensus
MC-295414
Player-created vibrations stop being retransmitted by amethyst when the player switches into spectator mode
Confirmed
MC-295398
Structure blocks create bugged sculk sensors
Confirmed
Comments
@NeunEinser Please actually read bug reports before closing them.
@NeunEinser Please actually read bug reports before closing them.
Thanks Savvvage_.
@Greymagic27 I completely agree with the importance of having clear reproduction steps. There is not, however, any good reason why they have to be written in text rather than shown in a video, and in fact videos are generally better for things like this, which is why Youtube is a more popular vehicle for Minecraft tutorials than microblogging plaforms.
The reproduction setup consists of a total of 6 blocks, and the video clearly shows the precise coordinates of all 6. If someone is incapable of figuring out how to reproduce this setup from the attached 43-second video, I’m confident that it would take them longer than 43 seconds to understand an equivalent set of text instructions.
Dude, actually read the issue before closing it. I provided all of that information already.
This was already reported in MC-207289, but was resolved without actually fixing the issue. (They only fixed the specific examples given in that ticket, they didn’t actually make it nondirectional.)
Oh, I just noticed this has been incorrectly marked as resolved, so I’ve opened a new ticket, MC-296182
And confirmed in 1.21.5. Here’s another video demonstrating the bug: https://www.youtube.com/watch?v=JUdHnEvtft4
Still exists in 1.21.4
Cannot reproduce in 1.21.4 or 1.21.5. Please confirm you don’t have a mod or datapack enabled that might be affecting the behavior.
Also applies to the player or any mob standing still on it
This is not a bug, you misclicked and placed the bucket in the water block that was already there.
Looking at the code, I’m pretty sure the current behavior is not intended by Mojang. Vibration particles are already being assigned the overrideLimiter boolean by default, the same as any particle that’s created with the /particle force command, which IMO makes it pretty clear that Mojang wants them to be visible from far away.
The overrideLimiter attribute is being ignored for vibrations due to a bad check in net.minecraft.server.level.ServerLevel.sendParticles, very easily fixed.