Inconsistent Horizontal Beacon Range
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 by13
Created Issue:
Inconsistent Horizontal Beacon Range
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.
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Thank you for your report!
We're actually already tracking this issue at MCPE-31092 which has been closed as Won't Fix.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-31092, so this ticket is being resolved and linked as a duplicate. This issue is a limitation of the simulation distance range, which is 4 chunks on Realms.
Please do not leave a comment as this issue will not be fixed. However, if you want to suggest a feature you can do so on the feedback site linked below.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue at MCPE-31092, which has been closed as Won't Fix
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue at MCPE-31092, so I will resolve and link this ticket as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. The description of that ticket or the comments might explain the rationale. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
The issue is actually MCPE-31092 and nothing to do with redstone
Thank you for your report!
We're tracking this issue as MCPE-31092, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. The description of that ticket or the comments might explain the rationale. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue as MCPE-31092, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. The description of that ticket or the comments might explain the rationale. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue as MCPE-31092, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. The description of that ticket or the comments might explain the rationale. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue as MCPE-31092, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. The description of that ticket or the comments might explain the rationale. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue as MCPE-31092, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. The description of that ticket or the comments might explain the rationale. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-31092, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue as MCPE-31092, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
I am pretty sure that this is NOT the same bug as MCPE-31092. This bug only happens when Add-ons are loaded! If you run the same steps to reproduce, but skip the step where you activate an add-on, the bug DOES NOT happen!
Not to mention that this can affect a huge part of the final chunk, not just a few blocks around the edges: if you follow the steps to reproduce, you're losing an effect area that's an entire quarter of that last chunk.
Edited to add: Also, this issue did not occur when I first built my beacons, which was in a previous version (1.20 something I think). It happened at some point between when the minecart stoppage bug started and the recent new releases.


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.
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