I was messing with Jump Boost II in a map I'm creating on my iPad Air, but when I was some blocks away the effect started vanishing. I remember Xisumavoid's video on the range of beacons and I discovered that here on the iOS version it isn't, but weirdly enough I found some inconsistencies so I decided to mark with red glass the borders of the beacon range.
It created a strange shape so I opened another world at different coordinates and I recreated the original red border, but I discovered that the effect was vanishing in some areas where it shouldn’t have. I marked the new perimeter in green glass and comparing the borders I couldn't find a logic. I think it is a bug regarding chunk loading the effect, but you are the experts so here you have my issue.
Linked issues
is duplicated by
Attachments
Comments


The shape is caused by the simulation distance when it is at 4 chunks. On a 6 chunk simulation distance there is also a chance of a small area (chunk) not having the beacon effect. Anything >6 chunks and this should disappear. The chunk containing the beacon in these occasions is not loaded (active) due to the shape of the simulated (working) area.

Great! So we know the issue, but is it a bug? I think so

Affects 1.12. I'm wondering if there would even be a solution to this besides turning up the simulation distance (I can't because I mostly play on Realms).
Thank you for your report!
However, this issue has been closed as Won't Fix.
If you'd like to post a suggestion or give further feedback, please visit the Minecraft Feedback Site or choose a link below.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I just want to say that I know why the beacon beam cannot be seen if you go 64 blocks away from the block, but this doesn't relate at all with my issue. Even if the beam is missing, the effect is still there in the y axis, but in the z and the x axes there are some holes around the corners of the range limit. I still suggest chunk loading issues with older devices, but still my iPad isn't the new Nokia 3310, so I still don't know. I hope it is a bug that can be identified on other devices and so I hope for its correction as soon as possible. Thank you for reading.