Beacon beam disappears after going past 64 blocks

To Reproduce

Build a beacon. Walk away until it disappears but the chunks around it do not.

Still affects in 1.2.13.5.

Can confirm for 1.5.2

A possible solution for this would be swappping the beacon beam for a non animated block similar to how it's done to kelp at a distance

Still present in 1.6.1

Won’t be fixed in 1.7 or 1.8 so I’m guessing it won’t be fixed at all.

Don't be so negative. The bug report is still open and they are aware of this issue, which means they are still considering it. They just haven't got around to fixing it yet.

They are aware of this issue? I wouldn’t be so negative if it was dealt with. And considering fixing it? You realise this bug makes the beacon a useless block. I’ll wait tho I’m sure some year it will be fixed.

It depends on the priority list.
Considering this isn't a "game-breaking" bug, it won't likely be fixed anytime soon (maybe later down the line).

Its a block-breaking bug ruining creations. And if thats the case then thats that. If it isn’t fixed anytime soon then ill just re create my builds which I’m capable of doing.

..

This issue still affects 1.11.1

Well I can see this has been updated so could it be fixed anytime soon? I'd like to use beacons again..

The Problem is: This is a beacon and the logical basic function of a Beacon is the far visibility.

in german: Leuchtfeuer; in latain: malus navis

So why was console edition different? The light would disappear at Max chunk distance, for me playing on Switch that should be 14 chunks of visibility for Bedrock, whatever function the beacon works on needs to be changed into its own unique function so when everything around the beacon disappears when further away you can still see the light, gotta do something instead of just leaving a broken beacon in the game u know🤷

The other particles have this also

Easy fix is to rename it from Beacon to Buffer and remove the beam entirely ;p

I hate this bug. Beacons are supposed to help people find their way but by the time you see the beam, you will most likely see the building. Makes them only good for effects and it annoys me.

The beacon beam is a block entity model, which yes, disappears before block models. I believe it renders as long as it is within simulation distance (which is separate from render distance. If you are worried about getting lost, turn on "Show coordinates", and record where your base is.

This bug breakes one use of the beacon: The player should be able to use it to find the location where the beacon is from far away.

Related issue MCPE-30028

Confirmed for 1.16

Well in Java Edition this issue does not exist, so it's diffferent from JE and in order to make the synchronization between BE and JE, please fix this.

I geuss you guys can give a tag to the becaon light beam which marks it to be a enity can be rendered from far away distances.😃

Affects 1.16.200.53 Beta.

affects 1.17.20.23

This bug is somehow simultaneously reported as MCPE-25228 & MCPE-17595. If 70 blocks is the entity render limit, perhaps a bug report should be opened stating that beacon beams should not be considered entities in terms of how they're rendered.

Affects 1.17.40.20

Affects 1.17.30

Affects 1.18.2. This bug is very noticeable now that beacons are commonly placed at negative Y coordinates in order for the beacon effects to reach down to bedrock. At the surface the beam doesn't render, even right on top of it

Active in 1.18.31 PS5. It can't take this long surely

Still an issue in 1.19.2…

Hoppers, Chests, Banners, Paintings, Anvills, Signs, Trapdoors and Minecarts all have similar issues

When I first began using beacons (in Creative), I thought they were there to help me find my way back somewhere. But they disappear! A "beacon" by definition is a wayfinder; it is not regularly understood as an effect generator. Mojang, please make an exception for this one item that is the very best built-in item to be a wayfinder to de-render only at a very far distance. Thank you.

still an issue

This continues to be an issue in 1.20.51.

This has been an issue for so long it seems like it is actually intended, though defeating the purpose of a beacon.