Range slider/input to limit the range of BlockESP

[HoratioGamer]

Describe the feature

Particularly with ores, and particularly in 2b2t with its greater render distance, when BlockESP is on, one sees a visual clutter extending to great distance showing all of the selected blocks -- there are outlines everywhere on the screen. One has to move around a little to get a perspective on what might be close based on which lines move more with player movement. With BlockESP turned off, one sees nothing. So finding just close stuff is not easy.

By adding a range slider/value input to filter BlockESP results to those within a certain radius of the Camera Position (not player position), one can immediately see what is close, and not get the visual clutter of farther matches. If one is searching for a rare block, like Ancient Debris, then obviously this is not as helpful. In combination with:

#3541 (comment)

Being able to see the ore around the corner in a cave complex is useful for fast accumulation of some ores.

In combination with FreeCam which changes a player's Camera Position, it allows exploring selectively in different directions to see where the most promising, easily-reached proximity is -- at a distance it is hard to see what is proximate to an existing tunnel or, the ground surface, or natural caves.

I would recommend making the slider/value input default to max range every time BlockESP is activated, so that forgetting the slider from the last use of BlockESP does not cause one to miss things on the next use of BlockESP. Essentially, when activating BlockESP changes the entire screen into detection lines, one can go to the slider/value input, and reduce the range and see less visual clutter and easily see only the closer blocks.

By making this based on Camera Position, it makes it unique and different than just reducing one's client render distance in Minecraft Video Options, which is always player-position based.

Before submitting a suggestion

• This feature doesn't already exist in the client. (I have checked every module and their settings on the latest dev build)

• This wasn't already suggested. (I have searched suggestions on GitHub and read the FAQ)