Vibrations don't render when generated more than than 32 blocks from the player

Particles are usually just minor aesthetic effects with no impact on gameplay, so they stop rendering when more than 32 blocks away. This makes sense, as it’s not important to see them from far away. Smoke signals from campfire (when placed on a haybale) also already set a precedence for partilces rendered from further away

Vibrations however actually represent an importing thing in the game, with a specific position and effect on the world. It is often important that the player can see they exist.

Additionally, vibrations can move by up to 16 blocks during their lifetime, and their rendering is calculated based only on where they generated, not where they are currently. Combined with player movement, this means it’s possible for a vibration to get arbitrarily close to the player and still not render.

This is confusing and makes it difficult to understand what’s going on with a sculk sensor mechanism.

Steps to reproduce:

1. Build an observer clock with a piston to constantly trigger the sculk sensor

   [media]

2. (Optional) set your FOV to minimum

3. Move away

Observed result

The particle stops rendering

Expected result

The particle always renders